How do I find my Fibery Workspace name?

Your workspace name is the subdomain in your Fibery URL. For example, if you access Fibery at `https://my-team.fibery.io`, your workspace name is `my-team`.

How do I generate a Fibery API Token?

In your Fibery workspace, go to **Settings > API**, click on **Create New Token**, give it a name, and copy the generated token immediately.

Can I query custom fields created in my spaces?

Yes! Use the `get_schema` tool to see the fully qualified names of your custom fields, and then include them in the `select_json` parameter of the `query_entities` tool.

Fibery MCP Server for Claude Desktop 11 tools — connect in under 2 minutes

Name: Fibery
Availability: InStock
Author: Vinkius

modelcontextprotocol.io/quickstart/user

Built by Vinkius GDPR 11 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Fibery and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "fibery": {
      // Your Vinkius token — get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Fibery MCP Server

Fibery is a work management platform that adapts to your unique processes. This MCP server allows your AI agent to interact with your Fibery workspace seamlessly.

Claude Desktop is the definitive way to connect Fibery to your AI workflow. Add the Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 11 tools in the chat interface — ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

Key Features

Space & Schema Discovery — List all your spaces (apps) and retrieve the full schema to understand your custom databases and fields.
Entity Management — Query, create, update, and delete entities across any of your custom databases flawlessly.
Comment Integration — Read and add comments to entities to keep your team in sync natively.
Advanced Querying — Use granular filters and field selections to retrieve exactly the data you need synchronously.
Cross-Database Search — Search for information across your entire workspace flawlessly through the agent.

The Fibery MCP Server exposes 11 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Fibery to Claude Desktop via MCP

Follow these steps to integrate the Fibery MCP Server with Claude Desktop.

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json

Add the MCP Server

Paste the configuration above into the mcpServers section

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server

Start using Fibery

Look for the 🔌 icon in the chat — your 11 tools are now available

Why Use Claude Desktop with the Fibery MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Fibery through the Model Context Protocol.

Claude Desktop is the reference MCP client — it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

Enterprise-grade security with local config storage — your tokens never leave your machine, and connections go directly to the Vinkius Edge network

Fibery + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Fibery MCP Server delivers measurable value.

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies — all through natural language

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Fibery MCP Tools for Claude Desktop (11)

These 11 tools become available when you connect Fibery to Claude Desktop via MCP:

add_comment

Add a comment to an entity

create_entity

Create a new entity in a specific database

delete_entity

Delete an entity

get_comments

Retrieve comments for a specific entity

get_entity

Get a specific entity by its UUID

get_schema

Retrieve the full schema of the workspace, including all databases (types) and fields

list_apps

List all Fibery apps (spaces)

list_users

List all users in the Fibery workspace

query_entities

Query entities from a specific database (type)

search_entities

Search for entities by keyword across all databases

update_entity

Update an existing entity

Example Prompts for Fibery in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Fibery immediately.

"List all active spaces in my Fibery account."

"Show me the tasks assigned to me in the 'Software Development' space."

"Add a comment to task UUID-123 saying 'The client approved the design'."

Troubleshooting Fibery MCP Server with Claude Desktop

Common issues when connecting Fibery to Claude Desktop through the Vinkius, and how to resolve them.

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting — wait a few seconds.

Fibery + Claude Desktop FAQ

Common questions about integrating Fibery MCP Server with Claude Desktop.

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully — if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL — Claude auto-negotiates the transport protocol.