# Fiber AI [Health: Active]

**Category:** 🔎 Search & Data Extraction  
**Repository:** https://github.com/fiber-ai/mcp  
**GitHub Stars:** 0  
**Views:** 1  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/fiber-ai

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

## Tools
Capabilities this server exposes over MCP:

- **companySearch_tool** — OperationId: companySearch.

Company search.

USE THIS WHEN:
- Company search.
- Search for companies using filters.
- Find matching entities with structured filters and pagination.

DO NOT USE FOR:
- Finding individual people (use peopleSearch)
- Getting contact info like email (use syncContactEnrichment after finding profile)

EXAMPLE:
Input: companySearch_tool(searchParams={}, pageSize=123)

INPUT SCHEMA:
Required parameters:
  - searchParams (object): Search parameters for company search API.
    Properties: ['exactCompanyV2', 'domains', 'headquartersCountryCode', 'headquartersStateName', 'employeeCountV2', 'employeeCountRanges', 'keywords', 'industriesV2', 'stage', 'totalFundingUSD', 'lastFundingUSD', 'lastFundedOn', 'foundedOn', 'nameLike', 'exactCompany', 'acceleratorsV2', 'headquartersLocation', 'linkedinSlugs', 'specialFlags', 'employees', 'naicsCodes', 'fortuneRankings', 'jobPostingsV2', 'jobPostingStats', 'officeLocationsV2', 'tlds', 'numWordsInName', 'status', 'technologies', 'crunchbaseCategories', 'crunchbaseCategoryGroups', 'crunchbaseSlugs', 'investorsV2', 'technologiesV2', 'revenueRangeUSD', 'revenueRan...
- **peopleSearch_tool** — OperationId: peopleSearch.

People search.

USE THIS WHEN:
- People search.
- Search for people using filters.
- Find matching entities with structured filters and pagination.

DO NOT USE FOR:
- Getting email/phone directly (use syncContactEnrichment after finding profile)
- Company searches (use companySearch)

EXAMPLE:
Input: peopleSearch_tool(searchParams={}, pageSize=123)

INPUT SCHEMA:
Required parameters:
Optional parameters:
  - searchParams (object): Search parameters for people search.
      - country3LetterCode (['object', 'null'])
      - numConnections (['object', 'null'])
      - numFollowers (['object', 'null'])
      - approxAge (['object', 'null'])
      - keywords (['object', 'null'])
      - keywordsV2 (['object', 'null'])
      - keywordSearchOptions (['object', 'null'])
      - jobTitleV2 (['object', 'null'])
      - jobFunction (['object', 'null'])
      - exactProfile (['object', 'null'])
      - exactProfileV2 (['object', 'null'])
      - startedInRole (any)
      - startedAtCompany (any)
      - location (['object', 'null'])
      - lang...
- **profileLiveEnrich_tool** — OperationId: profileLiveEnrich.

Live fetch LinkedIn profile.

USE THIS WHEN:
- Live fetch LinkedIn profile.
- Returns an enriched profile with details (work experience, education, skills, location, etc.) for a given LinkedIn profile identifier. **Note:** This endpoint does NOT return emails or phone numbers. To retrieve a person's contact details (emails and phone numbers), use the `POST /contact-details/single` endpoint (synchronous, recommended) or the `POST /individual-reveal/start` + `POST /individual-reveal/poll` pair (asynchronous). These can be found under the **Contact details** section.
- Fetch fresh upstream profile/company/activity data.

DO NOT USE FOR:
- Batch operations (use search or batch APIs instead)

EXAMPLE:
Input: profileLiveEnrich_tool(identifier="example_string", getDetailedEducation="example")

INPUT SCHEMA:
Required parameters:
  - identifier (string): The profile's LinkedIn slug (e.g. 'williamhgates'), full LinkedIn URL (e.g. 'https://www.linkedin.com/in/williamhgates/'), Sales Navigator URN, or LinkedIn user ID (e.g. '443105112').
Optional parameters:
  - getDetailedEducation (['boolean', 'nu...
- **companyLiveEnrich_tool** — OperationId: companyLiveEnrich.

Live fetch LinkedIn company.

USE THIS WHEN:
- Live fetch LinkedIn company.
- Returns an enriched company with details for a given LinkedIn company identifier.
- Fetch fresh upstream profile/company/activity data.

DO NOT USE FOR:
- Batch operations (use search or batch APIs instead)

EXAMPLE:
Input: companyLiveEnrich_tool(type="example_string", value="example_string")

INPUT SCHEMA:
Required parameters:
  - type (string): 
  - value (string): The company's LinkedIn slug (e.g. 'microsoft'), LinkedIn URL (e.g. 'https://www.linkedin.com/company/microsoft'), LinkedIn organization ID (e.g. '1441'), or Fiber company ID (e.g. 'comp_1441').
Optional parameters:
  - getHistoricalHeadcount (boolean): Whether to compute the company's overall employee count over time and recent growth trends. This returns total headcount through time, not a per-department breakdown — for per-department headcount, use the Depth Chart endpoints. No additional cost, but may take longer.

RETURNS:
Response object with keys: output, chargeInfo, warnings, advice
- **getQuickstartScript_tool** — OperationId: getQuickstartScript.

Get quickstart install script.

USE THIS WHEN:
- Get quickstart install script.
- Returns a bash script that signs up for a Fiber API trial and prints your API key.
- Start an asynchronous workflow, then call the related poll/status endpoint.

EXAMPLE:
Input: getQuickstartScript_tool()

INPUT SCHEMA:
Required parameters:
Optional parameters:
- **getOrgCredits_tool** — OperationId: getOrgCredits.

Get organization credits.

USE THIS WHEN:
- Get organization credits.
- Get credits for an organization.
- Inspect or manage account-level billing and usage settings.

EXAMPLE:
Input: getOrgCredits_tool()

INPUT SCHEMA:
Required parameters:
Optional parameters:

RETURNS:
Response object with keys: output, chargeInfo, warnings, advice
- **getRateLimits_tool** — OperationId: getRateLimits.

Get organization rate limits.

USE THIS WHEN:
- Get organization rate limits.
- Returns the effective rate limits for all API endpoints for your organization. If your organization has custom rate limits on any endpoint, those are reflected here.
- Inspect or manage account-level billing and usage settings.

EXAMPLE:
Input: getRateLimits_tool()

INPUT SCHEMA:
Required parameters:
Optional parameters:

RETURNS:
Response object with keys: output, chargeInfo, warnings, advice
- **getAutoTopupSettings_tool** — OperationId: getAutoTopupSettings.

Get auto top-up settings.

USE THIS WHEN:
- Get auto top-up settings.
- Get the organization's auto top-up configuration. When configured is false, no auto top-up settings exist yet.
- Inspect or manage account-level billing and usage settings.

EXAMPLE:
Input: getAutoTopupSettings_tool()

INPUT SCHEMA:
Required parameters:
Optional parameters:

RETURNS:
Response object with keys: output, chargeInfo, warnings, advice
- **cardsAttach_tool** — OperationId: cardsAttach.

Attach card to trial account.

USE THIS WHEN:
- Attach card to trial account.
- Attach a payment card to a cardless trial organization using a single-use Stripe shared payment token. The card is verified with a temporary $1 authorization that is refunded immediately (net cost $0), and the organization's free-credit ceiling is raised. The verified card is not saved for future charges — every future paid top-up requires a freshly-minted shared payment token.
- Inspect or manage account-level billing and usage settings.

EXAMPLE:
Input: cardsAttach_tool(sharedPaymentGrantedToken="example_string")

INPUT SCHEMA:
Required parameters:
  - sharedPaymentGrantedToken (string): Single-use Stripe shared payment token (`spt_...`) authorizing exactly one card handoff. Mint it on the buyer side (see https://docs.stripe.com/agentic-commerce/concepts/shared-payment-tokens); each request must submit a freshly-minted token.
Optional parameters:

RETURNS:
Response object with keys: output, chargeInfo, warnings, advice
- **getAllApiKeys_tool** — OperationId: getAllApiKeys.

List API keys.

USE THIS WHEN:
- List API keys.
- List all API keys for your organization, including each key's name, prefix, expiration, and per-key credit usage. The secret value of a key is only shown once at creation and is never returned here. First-time users: create your initial API key at https://app.fiber.ai or via POST /v1/account/send-otp + verify-otp. This endpoint manages keys once you have one.

EXAMPLE:
Input: getAllApiKeys_tool(includeRevoked=True)

INPUT SCHEMA:
Required parameters:
Optional parameters:
  - includeRevoked (boolean): Include revoked keys in the results. Defaults to false, returning only active keys.

RETURNS:
Response object with keys: output, chargeInfo, warnings, advice

## Claude Desktop Quick Installation
Remote MCP endpoint (confidence: high). Install path detected from listing signals. Add as a URL/SSE server in your client:

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

## Documentation

## What Fiber AI MCP server does

Fiber AI MCP server exposes Fiber AI data and account operations through the Model Context Protocol. It is listed in the 🔎 Search & Data Extraction category and is intended for agent-driven research inside an editor or chat client.

The available search tools cover companies and people separately. Company search accepts structured filters such as domains, location, industry, employee counts, funding, technologies, and pagination fields. People search supports filters for attributes including country, connections, followers, keywords, job title, job function, location, and role history. Search results are intended to identify matching entities; contact details require a separate enrichment flow.

Live enrichment tools fetch current LinkedIn profile or company information. Profile enrichment can return work experience, education, skills, and location, but it does not return email addresses or phone numbers.

## How it works

The Fiber AI MCP server is available as three remote endpoints. V2 uses an API key and offers direct tools for common operations. V3 uses browser-based OAuth and exposes public operations as direct tools. Core also uses an API key, but keeps the tool surface to five discovery and invocation meta-tools for runtime access to more than 100 API endpoints.

For the listed V2-style tools, an agent sends structured arguments to operations such as `companySearch_tool`, `peopleSearch_tool`, `profileLiveEnrich_tool`, and `companyLiveEnrich_tool`. Search parameters are passed as an object, while live enrichment accepts a LinkedIn slug, URL, organization identifier, or Fiber company ID as appropriate. Responses can include output, charge information, warnings, and advice for account operations.

## Setup and configuration

Create a Fiber API key at Fiber's API application for V2 or Core, then provide it through the `FIBER_API_KEY` environment variable. V3 does not require that variable; the client opens a browser for SSO during the first connection. The remote URLs are `https://mcp.fiber.ai/mcp/v2`, `https://mcp.fiber.ai/mcp/v3`, and `https://mcp.fiber.ai/mcp` for Core.

The repository documents HTTP configuration for Cursor, Claude Code, Claude Desktop, Codex, Gemini CLI, Windsurf, and Visual Studio Code. Claude Desktop and claude.ai should use V3 as a custom connector when OAuth is required.

## Tools and capabilities

- Search companies with structured filters and pagination.
- Search people using profile, role, location, and keyword filters.
- Fetch live LinkedIn profile data without contact details.
- Fetch live LinkedIn company data and optionally historical headcount.
- Retrieve quickstart installation and trial-signup scripts.
- Inspect credits, rate limits, auto-top-up settings, and API keys.
- Attach a payment card to an eligible trial account using a single-use Stripe shared payment token.

## Limitations and notes

The Fiber AI MCP server separates discovery from contact retrieval: company and people search do not directly provide email or phone data, and profile live enrichment explicitly excludes those fields. Use the documented contact-details API flow when that capability is needed.

V2 and Core require API-key handling, while V3 depends on browser-based SSO. Account and billing tools can expose usage or change payment-related settings, so agents should only call them with appropriate authorization. MCP is positioned for interactive IDE or chat use; the README recommends Fiber's REST API or SDKs for autonomous scripts and production pipelines.

_Full upstream README: https://allmcps.com/mcp/fiber-ai/readme_