Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Fiber AI

by fiber-aiversion 1.0.0i★ –iRuns in the cloud
Registry nameai.fiber/mcp

Install

Overview

Description from the maker (original English)

Search companies, enrich contacts, and reveal emails and phones from your AI agent.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs in the cloud
  • Transport: Streamable HTTP
  • Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on the maker’s server: what you ask it goes through their server.
  • The registry lists no key to fill in.

You need

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

  1. Open Settings → Connectors
  2. Press Add custom connector
  3. Paste the address below and press Add
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Add2https://…3
https://mcp.fiber.ai/mcp/v2/

Run this in your terminal

claude mcp add --transport http fiber https://mcp.fiber.ai/mcp/v2/

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "fiber": {
      "url": "https://mcp.fiber.ai/mcp/v2/"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "fiber": {
      "type": "http",
      "url": "https://mcp.fiber.ai/mcp/v2/"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

  1. Open ChatGPT on the web → Settings → Connectors (Apps)
  2. Press Create or Add (some plans need Developer mode under Advanced first)
  3. Paste the address below, give it a name and save
  4. If it asks you to sign in, sign in with the maker
SettingsConnectors1+ Create2https://…3
https://mcp.fiber.ai/mcp/v2/

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

We have not read this server’s tool list yet; we check endpoints in rotation.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified against the domain fiber.ai (the registry checks domain ownership)

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • … Not checked yet

    Endpoint responds

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    Sign-in with OAuth

    Not checked yet; we check endpoints in rotation

  • … Not checked yet

    No hidden instructions in tool descriptions

    Not checked yet; we read the tool list when we check the endpoint

Compared with others in Search & AI memoryi

  • More stars than 0% of the other 7241 servers in this category
  • Published to the registry more recently than 4% of the other 7241 servers in this category
  • Basic checks equal to or better than 100% of the other 7241 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Fiber AI safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 8 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated 3 days ago
Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago
Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated 44 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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/ .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:

ServerURLAuthBest For
V2https://mcp.fiber.ai/mcp/v2API keyAuto-generated direct tools for the top ~10 priority operations (companySearch_tool, peopleSearch_tool, etc.)
V3https://mcp.fiber.ai/mcp/v3OAuth (SSO)Direct tools for every public operation with compact descriptions; the model can call or expand any tool on demand
Corehttps://mcp.fiber.ai/mcpAPI key5 meta-tools that discover and call any of 100+ API endpoints (search_endpoints, list_tag_packs, list_all_endpoints, get_endpoint_details_full, call_operation)

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.

Want more than MCP? Use the Fiber AI plugin

The Fiber AI plugin bundles these MCP servers with 16 skills (search, enrich, audiences, recruiting and SDR playbooks) and 7 persona subagents (ai-sdr, ai-recruiter, gtm-strategist, and more) for Claude Code, Cursor, Gemini CLI, OpenCode, Codex, and VS Code. See its install guide. This repo covers the MCP servers only.


Setup

Get an API key at fiber.ai/app/api for V2 and Core. The examples read it from a FIBER_API_KEY environment variable. V3 needs no key: your client opens a browser for SSO login on first connect.

Connect directly with the config for your client below, or through Smithery.

Smithery

Fiber AI is listed on Smithery as fiberai/fiber-mcp (V2) and fiberai/fiber-core (Core). Install into your client with one command:

npx -y @smithery/cli@latest mcp add fiberai/fiber-mcp --client cursor

Replace cursor with your client: claude-code, claude, vscode, codex, gemini-cli, windsurf, opencode, cline, goose, and more (npx -y @smithery/cli@latest mcp add --help lists them all). Use fiberai/fiber-core for Core. On first connect your client opens Smithery in the browser to sign in and set your Fiber API key.

To use it as a Smithery connection instead (for agents that call tools through the Smithery CLI):

npx -y @smithery/cli@latest mcp add fiberai/fiber-mcp --id fiber-ai-v2 \

--headers "{\"x-api-key\": \"$FIBER_API_KEY\"}" npx -y @smithery/cli@latest tool list fiber-ai-v2


Cursor

Paste a link into your browser address bar and press Enter (Cursor must be installed):

V2:

cursor://anysphere.cursor-deeplink/mcp/install?name=fiber-ai-v2&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLmZpYmVyLmFpL21jcC92MiJ9

V3 (OAuth):

cursor://anysphere.cursor-deeplink/mcp/install?name=fiber-ai-v3&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLmZpYmVyLmFpL21jcC92MyJ9

Core:

cursor://anysphere.cursor-deeplink/mcp/install?name=fiber-ai-core&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLmZpYmVyLmFpL21jcCJ9

The links don't include your key; give it to the agent in chat, or add it to ~/.cursor/mcp.json (or .cursor/mcp.json in your project):

{

"mcpServers": { "fiber-ai-v2": { "type": "http", "url": "https://mcp.fiber.ai/mcp/v2", "headers": { "x-api-key": "${env:FIBER_API_KEY}" } }, "fiber-ai-v3": { "type": "http", "url": "https://mcp.fiber.ai/mcp/v3" }, "fiber-ai-core": { "type": "http", "url": "https://mcp.fiber.ai/mcp", "headers": { "x-api-key": "${env:FIBER_API_KEY}" } } } }


Claude Code
claude mcp add --transport http fiber-ai-v2 https://mcp.fiber.ai/mcp/v2 \

--header "x-api-key: $FIBER_API_KEY"

claude mcp add --transport http fiber-ai-v3 https://mcp.fiber.ai/mcp/v3

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

Run /mcp inside a Claude Code session to verify the connection and complete the V3 login.


Claude Desktop and claude.ai

Claude Desktop and claude.ai add remote servers as custom connectors, which authenticate with OAuth and can't send an API-key header. Use V3:

  1. Open Settings → Connectors → Add custom connector.
  2. Enter https://mcp.fiber.ai/mcp/v3 and sign in when prompted.

You can also add https://mcp.fiber.ai/mcp/v2 as a connector and give the agent your key in chat (see Authentication).


Codex

Add to ~/.codex/config.toml:

[mcp_servers.fiber-ai-v2]

url = "https://mcp.fiber.ai/mcp/v2" env_http_headers = { "x-api-key" = "FIBER_API_KEY" }

[mcp_servers.fiber-ai-v3] url = "https://mcp.fiber.ai/mcp/v3"

[mcp_servers.fiber-ai-core] url = "https://mcp.fiber.ai/mcp" env_http_headers = { "x-api-key" = "FIBER_API_KEY" }

env_http_headers sends the value of the FIBER_API_KEY environment variable as the x-api-key header. Then sign in to V3:

codex mcp login fiber-ai-v3

The Codex IDE extension and the Codex app read the same ~/.codex/config.toml.


Gemini CLI
gemini mcp add -t http -H "x-api-key: $FIBER_API_KEY" fiber-ai-v2 https://mcp.fiber.ai/mcp/v2

gemini mcp add -t http fiber-ai-v3 https://mcp.fiber.ai/mcp/v3 gemini mcp add -t http -H "x-api-key: $FIBER_API_KEY" fiber-ai-core https://mcp.fiber.ai/mcp

Add -s user to install for every project instead of the current one. Run gemini mcp list to verify, and /mcp auth fiber-ai-v3 inside a session to sign in to V3.


OpenCode

Add to opencode.json in your project (or ~/.config/opencode/opencode.json):

{

"$schema": "https://opencode.ai/config.json", "mcp": { "fiber-ai-v2": { "type": "remote", "url": "https://mcp.fiber.ai/mcp/v2", "headers": { "x-api-key": "{env:FIBER_API_KEY}" } }, "fiber-ai-v3": { "type": "remote", "url": "https://mcp.fiber.ai/mcp/v3" }, "fiber-ai-core": { "type": "remote", "url": "https://mcp.fiber.ai/mcp", "headers": { "x-api-key": "{env:FIBER_API_KEY}" } } } }

Run opencode mcp list to verify, and opencode mcp auth fiber-ai-v3 to sign in to V3.


Visual Studio Code

Add to .vscode/mcp.json in your workspace (VS Code reads servers from the top-level servers key):

{

"inputs": [ { "type": "promptString", "id": "fiber-api-key", "description": "Fiber AI API key", "password": true } ], "servers": { "fiber-ai-v2": { "type": "http", "url": "https://mcp.fiber.ai/mcp/v2", "headers": { "x-api-key": "${input:fiber-api-key}" } }, "fiber-ai-v3": { "type": "http", "url": "https://mcp.fiber.ai/mcp/v3" }, "fiber-ai-core": { "type": "http", "url": "https://mcp.fiber.ai/mcp", "headers": { "x-api-key": "${input:fiber-api-key}" } } } }

VS Code prompts for the key once and stores it securely. Start the servers from MCP: List Servers.


Windsurf (Devin Desktop)

Open the Cascade panel's ... menu → Open MCP config file, and add:

{

"mcpServers": { "fiber-ai-v2": { "serverUrl": "https://mcp.fiber.ai/mcp/v2", "headers": { "x-api-key": "${env:FIBER_API_KEY}" } }, "fiber-ai-v3": { "serverUrl": "https://mcp.fiber.ai/mcp/v3" }, "fiber-ai-core": { "serverUrl": "https://mcp.fiber.ai/mcp", "headers": { "x-api-key": "${env:FIBER_API_KEY}" } } } }


Zed

Open Settings → AI → MCP Servers → Add Server → Add Remote Server, or add to your settings file:

{

"context_servers": { "fiber-ai-v2": { "url": "https://mcp.fiber.ai/mcp/v2", "headers": { "Authorization": "Bearer sk_live_..." } }, "fiber-ai-v3": { "url": "https://mcp.fiber.ai/mcp/v3" }, "fiber-ai-core": { "url": "https://mcp.fiber.ai/mcp", "headers": { "Authorization": "Bearer sk_live_..." } } } }

Zed starts an OAuth login for any remote server without an Authorization header, so use the Bearer form for V2 and Core.


Others

Most MCP-compatible tools can be configured with:

  • URL: https://mcp.fiber.ai/mcp/v2 (or /mcp/v3, /mcp)
  • Transport: HTTP (Streamable HTTP)
  • Auth: header x-api-key: (or Authorization: Bearer ) for V2 and Core; OAuth for V3
  • For stdio-only clients: npx -y mcp-remote https://mcp.fiber.ai/mcp/v2 --header x-api-key:$FIBER_API_KEY

Available Tools

V2 Server (/mcp/v2)

Direct API tools — each Fiber AI endpoint is exposed as an individual tool:

ToolDescription
companySearch_toolSearch for companies by industry, location, size, funding, etc.
peopleSearch_toolSearch for people by title, seniority, department, etc.
profileLiveEnrich_toolLive-fetch a LinkedIn profile
companyLiveEnrich_toolLive-fetch a LinkedIn company
getOrgCredits_toolCheck your credit balance
getRateLimits_toolCheck your organization's rate limits
getAutoTopupSettings_toolGet auto top-up settings
getAllApiKeys_toolList your API keys
cardsAttach_toolAttach a card to a trial account
getQuickstartScript_toolGet the quickstart install script
V3 Server (/mcp/v3)

One direct tool per public operation (100+), with compact descriptions the model can expand on demand.

Core Server (/mcp)

Meta tools for dynamic endpoint discovery:

ToolDescription
search_endpointsSearch for API endpoints by keyword
list_tag_packsList curated groups of endpoints to narrow the catalog
list_all_endpointsList all available API endpoints
get_endpoint_details_fullGet full schema details for an endpoint
call_operationCall any API endpoint by its operation ID

Authentication

V2 and Core require a Fiber AI API key. V3 uses OAuth (Clerk SSO) - the client opens a browser window for login and reuses the session token, no key configuration needed. Get an API key at fiber.ai/app/api.

You can supply your key in any of these three ways - pick whichever your client makes easiest:

Option A - via chat (zero config)

The agent passes the key in the request body as apiKey. Simplest path: paste your key into the agent

Only the beginning is shown; read the rest in the repo

Ask PopNx