fibery

Fibery MCP Server provides an integration between Fibery and any MCP-compatible LLM provider (for example Claude Desktop). It exposes a set of capabilities that let you query Fibery data, inspect databases and fields, and create or update entities using natural language. Available actions include listing databases, describing a database schema, querying data, creating single entities, creating multiple entities in batch, and updating existing entities. To use it, configure your MCP client (such as Claude Desktop) to point to the fibery-mcp-server and provide your Fibery host and API token. Once connected, you can issue natural language prompts that map to the underlying MCP actions, enabling conversational data work with Fibery without manual API calls.

Prerequisites:

• Node.js installed (recommended) or access to an MCP runtime that supports npx/CLI installation
• Access to Fibery workspace with a valid API token

Installation options:

1. Install via Smithery (recommended for Claude Desktop users):

npx -y @smithery/cli install @Fibery-inc/fibery-mcp-server --client claude

2) Install via npx directly (no Smithery):

```bash
npx -y @Fibery-inc/fibery-mcp-server

3) Install via UV (Python-based runtime) (if you prefer UV):
- Prerequisites:
  - Fibery API token
  - Python 3.10+
  - uv
- Install tool:

```bash
uv tool install fibery-mcp-server

4. Manual npm approach (if the package is published):

npm install -g @Fibery-inc/fibery-mcp-server

Configuration (example for Claude Desktop):

```json
{
  "mcpServers": {
    "fibery-mcp-server": {
      "command": "uv",
      "args": [
        "tool",
        "run",
        "fibery-mcp-server",
        "--fibery-host",
        "your-domain.fibery.io",
        "--fibery-api-token",
        "your-api-token"
      ]
    }
  }
}

Note: If the runtime command differs on your system, adjust the command and arguments accordingly (e.g., using npx or a Python/uv invocation).

Tips and considerations:

• Keep your Fibery API token secure; do not expose it in shared configs.
• If using UV, ensure the --fibery-host and --fibery-api-token values are current and have the required permissions.
• For development, you can point to a local clone of the Fibery MCP server and run it with the updated directory path in your config.
• Some MCP clients may require absolute paths to the runtime executable (e.g., /usr/local/bin/uv) if the command name cannot be resolved in PATH.
• Available tools map to common Fibery operations: list_databases, describe_database, query_database, create_entity, create_entities_batch, update_entity. Build prompts that request these operations explicitly for best results.