Fiber AI — MCP Server

The Model Context Protocol (MCP) server provides a standardized interface that allows any compatible AI agent to access Fiber AI's data and tools — search companies, enrich contacts, reveal emails, and more — directly from your editor.

For AI agents

If you are a coding agent and need to pick between MCP and the REST API, start with the canonical agent-facing docs on the API:

• Routing index + critical rules: https://api.fiber.ai/llms.txt
• Per-operation markdown: https://api.fiber.ai/ai-docs/<operationId>.md
• Operation index: https://api.fiber.ai/ai-docs/index.md
• MCP walkthrough for LLMs: https://docs.fiber.ai/article/using-mcp-in-llms

Rule of thumb: use MCP when you're acting inside an IDE / chat and each operation is a tool call; use the REST API (via @fiberai/sdk or fiberai) when you're building an autonomous script or a production pipeline.

Servers

Fiber AI offers three remote MCP servers:

Which one should I use? V2 is the fastest path for the most common flows with an API key. V3 is the most ergonomic for broad agent coverage — it exposes every public operation as a direct tool with compact descriptions, authenticated via browser-based SSO login instead of a pasted key. Core keeps the tool count tiny (5) and lets the agent discover endpoints at runtime; it uses the same API-key auth as V2. You can register more than one; the server names (fiber-ai-v2, fiber-ai-v3, fiber-ai-core) stay distinct.

Setup

Smithery

Install via Smithery with a single command:

npx -y @smithery/cli install @fiber-ai/mcp --client cursor

Replace cursor with your client: claude, windsurf, vscode, zed, etc.

Or browse and install from the Smithery web UI at smithery.ai/server/@fiber-ai/mcp.

Cursor

Click the link below to install automatically — paste it into your browser address bar and press Enter:

Install V2:

cursor://anysphere.cursor-deeplink/mcp/install?name=FiberAI-V2&config=eyJ1cmwiOiJodHRwczovL21jcC5maWJlci5haS9tY3AvdjIifQ==

Install Core:

cursor://anysphere.cursor-deeplink/mcp/install?name=FiberAI&config=eyJ1cmwiOiJodHRwczovL21jcC5maWJlci5haS9tY3AifQ==

Or manually: open Cursor Settings → Features → MCP → "+ Add New MCP Server" → Type: HTTP → URL: https://mcp.fiber.ai/mcp/v2

Claude Code

The simplest path passes your key as a header so the agent never sees it in chat:

claude mcp add --transport http fiber-ai-v2 https://mcp.fiber.ai/mcp/v2 \
  --header "x-api-key: $FIBER_API_KEY"

To also add the Core server:

claude mcp add --transport http fiber-ai https://mcp.fiber.ai/mcp \
  --header "x-api-key: $FIBER_API_KEY"

Or, if you prefer to give the key via chat, drop the --header flag and the agent will pass apiKey in the request body when you tell it your key.

Run /mcp inside a Claude Code session to verify the connection.

Claude Desktop

From Claude settings → Connectors, add a new MCP server with the URL https://mcp.fiber.ai/mcp/v2.

Or edit your claude_desktop_config.json:

{
  "mcpServers": {
    "fiber-ai-v2": {
      "url": "https

... [View full README on GitHub](https://github.com/fiber-ai/mcp#readme)