/ Directory / Playground / Fibery MCP
● Official fibery-inc ⚡ Instant

Fibery MCP

by fibery-inc · fibery-inc/fibery-mcp-server

Query and update Fibery work-management entities through MCP.

Fibery is a flexible work-management tool (think Notion + Linear + Jira). This MCP exposes any of your Fibery types — Feature, Bug, Customer, Insight — as entities Claude can read, link, and update.

Why use it

Key features

Live Demo

What it looks like in practice

fibery-mcp.replay ▶ ready
0/0

Install

Pick your client

~/Library/Application Support/Claude/claude_desktop_config.json  · Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "fibery-mcp": {
      "command": "uvx",
      "args": [
        "fibery-mcp-server"
      ]
    }
  }
}

Open Claude Desktop → Settings → Developer → Edit Config. Restart after saving.

~/.cursor/mcp.json · .cursor/mcp.json
{
  "mcpServers": {
    "fibery-mcp": {
      "command": "uvx",
      "args": [
        "fibery-mcp-server"
      ]
    }
  }
}

Cursor uses the same mcpServers schema as Claude Desktop. Project config wins over global.

VS Code → Cline → MCP Servers → Edit
{
  "mcpServers": {
    "fibery-mcp": {
      "command": "uvx",
      "args": [
        "fibery-mcp-server"
      ]
    }
  }
}

Click the MCP Servers icon in the Cline sidebar, then "Edit Configuration".

~/.codeium/windsurf/mcp_config.json
{
  "mcpServers": {
    "fibery-mcp": {
      "command": "uvx",
      "args": [
        "fibery-mcp-server"
      ]
    }
  }
}

Same shape as Claude Desktop. Restart Windsurf to pick up changes.

~/.continue/config.json
{
  "mcpServers": [
    {
      "name": "fibery-mcp",
      "command": "uvx",
      "args": [
        "fibery-mcp-server"
      ]
    }
  ]
}

Continue uses an array of server objects rather than a map.

~/.config/zed/settings.json
{
  "context_servers": {
    "fibery-mcp": {
      "command": {
        "path": "uvx",
        "args": [
          "fibery-mcp-server"
        ]
      }
    }
  }
}

Add to context_servers. Zed hot-reloads on save.

claude mcp add fibery-mcp -- uvx fibery-mcp-server

One-liner. Verify with claude mcp list. Remove with claude mcp remove.

Use Cases

Real-world ways to use Fibery MCP

Convert customer insights into prioritized feature requests

👤 Product managers using Fibery ⏱ ~15 min intermediate

When to use: You have a stack of Insight entities and need to roll them up into Features.

Prerequisites
  • Server/skill installed and authenticated — See repo README
Flow
  1. Pull recent insights
    Find Insight entities created this month grouped by theme.✓ Copied
    → Themed clusters of insights
  2. Create features
    For the top 3 themes, create a Feature entity linked to all contributing Insights with a 'why now' summary.✓ Copied
    → Three new Features with backlinks

Outcome: Backlog grounded in real user feedback with traceability.

Pitfalls
  • Fibery types are workspace-specific — Fibery types are workspace-specific — always start with describe_schema before assuming a field name.
Combine with: filesystem

Combinations

Pair with other MCPs for X10 leverage

fibery-mcp + filesystem

Pair with filesystem for complementary capabilities

Use this server together with filesystem to complete a multi-step task.✓ Copied

Tools

What this MCP exposes

ToolInputsWhen to callCost
describe_schema (none) First — to discover types and fields 1 API call
query_entities type, filter, limit Find entities matching criteria 1 API call
update_entity id, fields Change a field value 1 API call

Cost & Limits

What this costs to run

API quota
See provider docs for rate limits
Tokens per call
Varies by tool
Monetary
See repo README for pricing details
Tip
Cache tool results and avoid repeated identical calls.

Security

Permissions, secrets, blast radius

Credential storage: Use environment variables; never commit secrets
Data egress: Tool calls go to the provider's API as documented

Troubleshooting

Common errors and fixes

401 Unauthorized

Generate an API token at Fibery workspace settings → API keys. Set FIBERY_HOST and FIBERY_TOKEN.

Verify: describe_schema returns types
field not found

Field names in Fibery's API use the type-qualified form (e.g. Workflow/State). Use describe_schema to find the exact name.

Verify: Inspect the type's fields

Alternatives

Fibery MCP vs others

AlternativeWhen to use it insteadTradeoff
Linear MCPEng-onlyFixed schema; less flexible

More

Resources

📖 Read the official README on GitHub

🐙 Browse open issues

🔍 Browse all 400+ MCP servers and Skills