Fibery MCP Server

by fibery-inc Your server? Claim it

answering

Fibery is answering right now. Last checked 2 min ago.

Connect AI Assistant to Fibery — operating system for orgs run by nerds.

Uptime history 48 days of history · worst day 99%

48 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

242 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Fibery missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://mcp.fibery.io/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.fibery.io/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://mcp.fibery.io/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.fibery.io/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://mcp.fibery.io/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.fibery.io/mcp	streamable-http	sign-in	230 ms	2 min ago

Alternatives to Fibery

same job, measured the same way

Seller Assistant

by sellerassistant

Connect AI clients to Seller Assistant workflows for Amazon wholesale operations.

answering

IBM Maximo

by markusvankempen

Connect AI assistants to IBM Maximo for API discovery, OSLC querying, and Carbon UI generation.

183 installs/wk local only

Plexarm

by plexarm

The operating system for self-organised AI agent teams.

answering

Outline MCP Server

by vortiago

Connect AI assistants to Outline for document search, reading, and management

482 installs/wk local only

MCP Server for YNAB

by hs737

Connect your AI assistant to YNAB. Read-only by default, with reversible opt-in writes.

1 167 installs/wk local only

openLCA MCP Server

by below280

Connect AI assistants to openLCA. 31 tools for database search, model building, and LCIA.

4 503 installs/wk local only

Warpmetrics

by warpmetrics

Connect AI assistants to Warpmetrics — query runs, calls, costs, and outcomes.

40 installs/wk local only

Apex

by hunterpercival

APEX — AI operating system for founders. Join waitlist or request a demo.

25 installs/wk local only

Fibery — questions

Answers built from our own checks of this server.

Why is there no tool list for Fibery?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is Fibery working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 242 ms. The bar chart above shows every period we have measured.

How do I connect Fibery?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to Fibery?

No API key is involved. Fibery answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is Fibery?

It answers our handshake in 242 ms on average, which is faster than 59% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.