Get API key

Hosted MCP server

A hosted MCP server for LinkedIn profile, company, and job data.

Connect Claude, Cursor, or your own AI agent to EnvoAPI with one API key. Enrich profiles, look up companies, and search jobs through MCP tools — without building or hosting a custom integration.

Get API keyView setup guide

100 free credits · No credit card required

  • 15MCP tools
  • HTTPTransport
  • HostedNo server to run

Works with

  • Claude Desktop
  • Claude Code
  • Cursor
  • VS Code
  • Other compatible MCP clients

How it works

Connect once. Use EnvoAPI in plain language.

Add the hosted server to a compatible MCP client with your EnvoAPI API key. The client loads 15 MCP tools that your assistant can call from a normal prompt.

  1. Connect your client

    Add the hosted server URL and your EnvoAPI API key to your MCP client. Nothing needs to be installed or run locally.

  2. Load the tools

    Your client retrieves 15 MCP tool definitions with structured inputs for profile enrichment, company research, and job search.

  3. Ask in plain language

    Prompt your assistant normally. It selects the relevant tool, calls EnvoAPI, and uses the returned data in its response.

MCP tools

15 read-only MCP tools

The server exposes 15 tools across 5 data groups. Your MCP client loads their input schemas when it connects, and each tool retrieves data through a documented EnvoAPI endpoint.

  • Profiles

    Retrieve public profile data, contact availability, and recent posts.

    3MCP tools

    /profiles/{public_identifier}

    get_profile
    Retrieve a profile by its public /in/ identifier.
    get_profile_contact
    Check which public contact information is available for a profile.
    get_profile_posts
    List a profile's recent posts and reposts.

  • Companies

    Retrieve company data, employees, and recent posts.

    3MCP tools

    /companies/{universal_name}

    get_company
    Retrieve company details by company slug.
    get_company_employees
    List company employees, with optional profile details.
    get_company_posts
    List a company's recent posts.

  • Search

    Search people and companies, and retrieve the filters used to refine results.

    4MCP tools

    /search/people

    search_people
    Search people by keyword, title, company, location, and supported filters.
    search_companies
    Search companies by keyword, industry, size, and hiring signals.
    search_locations
    Resolve location IDs used in people, company, and job searches.
    get_search_filters
    List the available filters for a supported search type.

  • Jobs

    Search public job listings and retrieve individual job details.

    2MCP tools

    /jobs/search

    search_jobs
    Search jobs by keyword, company, location, and supported filters.
    get_job_detail
    Retrieve job details from a public job URL.

  • Posts

    Retrieve post details, comments, and reactions.

    3MCP tools

    /posts/detail

    get_post_detail
    Retrieve a post by URL, including author details.
    get_post_comments
    List comments on a post.
    get_post_reactions
    List the people and companies that reacted to a post.
5 groups15 MCP toolsRead-only

EnvoAPI includes 47 documented REST endpoints. The MCP server exposes 15 read-only tools across the profile, company, search, job, and post workflows shown above.

View the API reference

Connect your client

Connect your MCP client to EnvoAPI.

Choose your client and add the hosted EnvoAPI MCP endpoint using the same API key as the REST API. No EnvoAPI server needs to be installed, deployed, or maintained locally.

Connection details

Server URL
https://api.envoapi.com/mcp
Transport
Streamable HTTP
Authentication
API key via Bearer header
Access
Read-only

Keep your API key in local client configuration or your preferred secret-management workflow. Never paste it into a prompt or commit it to source control.

View full setup guide

Requires Node.js 18+ to run the mcp-remote compatibility bridge.

claude_desktop_config.jsonjson
{  "mcpServers": {    "envoapi": {      "command": "npx",      "args": [        "-y",        "mcp-remote",        "https://api.envoapi.com/mcp",        "--header",        "Authorization:${ENVOAPI_AUTH_HEADER}"      ],      "env": {        "ENVOAPI_AUTH_HEADER": "Bearer YOUR_ENVOAPI_API_KEY"      }    }  }}

Add this to your Claude Desktop configuration, replace YOUR_ENVOAPI_API_KEY, and restart the app.

This configuration file contains your API key. Do not commit or share it.

Example workflow

See one MCP workflow end to end.

A single prompt can trigger more than one EnvoAPI tool. In this example, the assistant searches for a matching person, retrieves their public profile, and uses the returned fields to produce a concise summary.

  1. You

    “Find a VP of Engineering at Acme Corp and summarize their background.”

  2. Tool 1 — Search

    search_people

    Finds a matching person and returns their public profile identifier.

    Inputsjson
    {  "keywords": "VP of Engineering",  "current_company": "Acme Corp",  "limit": 1}

    GET/api/v2/search/people

    Selected resultjson
    {  "fullName": "Jane Doe",  "headline": "VP of Engineering at Acme Corp",  "publicIdentifier": "jane-doe-synthetic"}
  3. Tool 2 — Enrich

    get_profile

    Retrieves the profile details needed to summarize the person's background.

    Inputsjson
    {  "public_identifier": "jane-doe-synthetic"}

    GET/api/v2/profiles/{public_identifier}

    Selected resultjson
    {  "fullName": "Jane Doe",  "headline": "VP of Engineering at Acme Corp",  "location": { "fullLocation": "San Francisco Bay Area, United States" },  "currentPositions": [    {      "title": "VP of Engineering",      "companyName": "Acme Corp"    }  ]}
  4. Assistant

    Jane Doe is VP of Engineering at Acme Corp and is based in the San Francisco Bay Area. Her public profile shows experience leading engineering teams, including her current role at Acme Corp.

Example data is synthetic. Responses are abbreviated for readability.

What teams build

Build research and enrichment workflows with EnvoAPI MCP.

Use 15 read-only MCP tools to retrieve profile, company, job, and post data inside assistants, agents, and internal workflows.

  • Research assistants

    Retrieve public profile and company context during sales, recruiting, account research, or market analysis.

  • Enrichment workflows

    Retrieve profile or company data and pass the structured results into your existing CRM, database, or automation workflow.

  • People and job search

    Search people and public job listings using supported criteria, then return selected results for review.

  • Internal data assistants

    Let teammates query public professional and company data through an MCP client without writing REST requests.

Read-only by design

Read-only access with your EnvoAPI API key.

EnvoAPI MCP tools can retrieve data, but they cannot create, update, or delete it. Requests use the same authentication, credits, and rate limits as the REST API.

View authentication guideView MCP documentation
  • EnvoAPI MCP tools retrieve public profile, company, job, and post data without write access.
  • Every request is authenticated with your EnvoAPI API key.
  • MCP calls consume the same credits and follow the same rate limits as REST API calls.
  • Keep your key in local client configuration or a secret-management workflow. Never place it in prompts or source control.

FAQ

Questions about EnvoAPI MCP

Compatibility, authentication, billing, endpoint coverage, and read-only access.

MCP and compatibility

3 questions

What is an MCP server?

Model Context Protocol (MCP) is an open standard for connecting AI applications to external tools and data sources through a consistent interface. EnvoAPI's hosted MCP server exposes 15 read-only tools for profile, company, search, job, and post data, allowing compatible clients to use EnvoAPI without you writing REST requests for each workflow.

Which clients can connect?

The setup guide covers Claude Desktop through the mcp-remote compatibility bridge, plus Claude Code, Cursor, and VS Code. Other clients can connect if they support remote MCP servers over Streamable HTTP and API-key authentication through an Authorization header. You can also connect from your own application with an MCP SDK.

How is MCP different from the REST API?

Both provide access to the same underlying EnvoAPI data. With REST, your application sends HTTP requests and handles responses directly. With MCP, a compatible AI client discovers named tools, supplies structured inputs, and calls them during a conversation or agent workflow. Use REST for deterministic application logic and MCP when an assistant needs to select or combine tools from natural-language instructions.

Authentication, credits, and coverage

2 questions

Do I need a separate API key or plan for MCP?

No. Use the same EnvoAPI API key and plan as the REST API. MCP tool calls consume the same credit balance and follow the same rate limits. There is no separate MCP fee or allowance.

Does MCP expose all 47 EnvoAPI endpoints?

Not currently. EnvoAPI documents 47 REST endpoints, while the MCP server exposes 15 read-only tools for the profile, company, search, job, and post workflows listed on this page. Use the REST API for endpoints that are not available through MCP.

Security and access

2 questions

How is the MCP connection authenticated?

Every MCP request must include a valid EnvoAPI API key in the Authorization header and is sent to the hosted endpoint over HTTPS. Store your key in local client configuration, an environment variable, or a secret manager. Never paste it into prompts or commit it to source control.

Can the assistant create, update, or delete data?

No. The current 15 MCP tools are read-only. They retrieve profile, company, search, job, and post data and do not expose create, update, or delete operations.

Need implementation details? View client setup, authentication, tool inputs, and response schemas in the MCP documentation.

View MCP documentation

Start building

Your assistant is one header away.

Create a key, add the server to your client, and start enriching profiles, companies, and jobs from a prompt — on the same key, credits, and rate limits you already use for REST.

Get API keySee the setup

Same API key as REST · No extra MCP charge · Read-only access