Skip to main content
Glama
Fibery MCP Server (deprecated)

Fibery MCP Server (deprecated)

Official
README.md
# ⚠️ Deprecated

This local MCP server is deprecated and no longer receives updates. Use the Fibery remote MCP server instead:

- **Claude**: install the [Fibery connector](https://claude.ai/directory/fibery) from the Claude directory.
- **ChatGPT**: install the [Fibery app](https://chatgpt.com/plugins/plugin_asdk_app_6a2ab6b4009c8191b74cb3b2c70025e3) in ChatGPT.
- **Cursor**: add `{"mcpServers": {"fibery": {"url": "https://mcp.fibery.io/mcp"}}}` to `~/.cursor/mcp.json`.
- **Claude Code**: `claude mcp add --transport http fibery https://mcp.fibery.io/mcp`

For other clients, see [Connecting to Fibery MCP](https://developers.fibery.com/guides/mcp/connecting#connecting-to-fibery-mcp).

---

## Legacy (unsupported)

These instructions are kept for reference only. This server no longer receives fixes or updates.

### Prerequisites
- A Fibery account with an API token
- Python 3.10 or higher
- [uv](https://github.com/astral-sh/uv)

### Installation
1. Install the tool using uv:
```bash
uv tool install fibery-mcp-server
```

2. Then, add this configuration to your MCP client config file. In Claude Desktop, you can access the config in **Settings → Developer → Edit Config**:
```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 "uv" command does not work, try absolute path (i.e. /Users/username/.local/bin/uv)

**For Development:**

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

TDQS

B3.4/5.0

Scored across 7 tools

Disambiguation3/5

Most tools have distinct purposes (create, list, describe, query, update), but create_entity and create_entities_batch have significant overlap—both create entities, differing only in batch capability. The current_date tool stands out as a utility that doesn't clearly align with the Fibery domain, potentially causing confusion about its role in the set.

Naming Consistency4/5

The naming follows a consistent verb_noun pattern (e.g., create_entity, list_databases, query_database) with clear, descriptive names. The only minor deviation is current_date, which uses a noun_noun pattern instead of a verb, slightly breaking the convention but remaining readable.

Tool Count4/5

With 7 tools, the count is reasonable for a Fibery integration, covering core operations like creation, listing, querying, and updating. It's slightly lean but functional, as it includes essential CRUD-like actions and schema exploration tools, though it might benefit from a delete tool for full lifecycle coverage.

Completeness3/5

The toolset covers key operations for interacting with Fibery databases, including creation, querying, and updating, with tools for schema exploration. However, there are notable gaps: no delete_entity tool limits full CRUD coverage, and the current_date utility feels out of place without clear integration into the domain, potentially leaving agents unable to perform complete entity management workflows.

Maintenance

ActivityMaintained
ResponsivenessLimited data