MCP

Use EnvoAPI from your AI assistant to research profiles, companies, jobs, and posts. MCP lets your assistant choose the right tools from your request. EnvoAPI hosts the server, so you do not need to run one yourself.

Connect with OAuth

Choose your platform below. Sign in with your EnvoAPI account when prompted and approve access. No API key is needed.

ChatGPT

1. Open Settings → Security and login and turn on Developer mode.

2. Open ChatGPT plugins, then choose Add → Create MCP App.

3. Enter these settings:

   Setting	Value
   Name	EnvoAPI
   Connection	https://api.envoapi.com/mcp
   Authentication	OAuth

4. Select I understand and want to continue, then click Create.

5. Sign in to EnvoAPI and approve access. Enable EnvoAPI in your conversation.

Developer mode availability depends on your account and workspace settings. See the ChatGPT connection guide if the option is missing.

Claude

1. Open Claude’s custom connector dialog, or go to Customize → Connectors → + → Add custom connector.
2. Set Name to EnvoAPI and MCP Server URL to https://api.envoapi.com/mcp, then click Add.
3. Follow the connection prompt to sign in to EnvoAPI and approve access.
4. In your chat, open + → Connectors and enable EnvoAPI.

See Claude’s connector guide for plan and workspace requirements.

Claude Code

Run this in your terminal:

claude mcp add --transport http envoapi https://api.envoapi.com/mcp

Open Claude Code, run /mcp, and select envoapi. Follow the sign-in prompt and approve access in your browser. Run claude mcp list in your terminal to check the connection. See the Claude Code MCP guide for help.

Codex

Run these commands in your terminal:

codex mcp add envoapi --url https://api.envoapi.com/mcp
codex mcp login envoapi

Sign in to EnvoAPI and approve access in the browser window. Open Codex and run /mcp to check the connection. See the Codex MCP guide for help.

OpenCode

Add this entry to your project’s opencode.json, keeping any existing settings:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "envoapi": {
      "type": "remote",
      "url": "https://api.envoapi.com/mcp",
      "enabled": true
    }
  }
}

Restart OpenCode and ask it to use EnvoAPI. Follow the sign-in prompt and approve access. If no prompt appears, run opencode mcp auth envoapi in your terminal. Check the connection with opencode mcp list. See the OpenCode MCP guide for help.

Other clients

Add https://api.envoapi.com/mcp as a remote server with Streamable HTTP and OAuth. Follow your client’s sign-in steps, then enable EnvoAPI’s tools. If OAuth is unavailable, use an API key instead.

Try a request

Ask in plain English. You do not need to know the tool names:

• “Find the founders of Stripe and show their professional backgrounds.”
• “Find software engineering jobs at Microsoft in London.”
• “Summarize this profile: [paste a profile URL].”
• After discussing two people: “Get the professional background for both.”
• “Research the company at hunter.io and enrich its company details.”

EnvoAPI provides 35 read-only tools. They can fetch data, but cannot edit profiles, publish posts, or send messages. Browse the tools in your MCP dashboard.

Use web search and EnvoAPI together

Your assistant can use its available web search to find people, profiles and company websites, then use EnvoAPI for more professional details. You do not need to say “use EnvoAPI” for each step.

What is already known	Next step for the assistant
A profile URL and a request for background	Get profile details directly.
A company domain and a request for company research	Find matching companies by domain, then get details for the correct company.
A company page URL	Get company details directly.
Only a person or company name	Find the correct profile or company with available web search or EnvoAPI search.
A follow-up such as “both” or “enrich more”	Continue with the people or companies already discussed. Fetch relevant missing details.

For example, web search may identify Hunter’s founders and their profile URLs. When you ask for both founders’ professional backgrounds, the assistant can pass those URLs to EnvoAPI without repeating the people search.

The assistant should reuse information it already has and stop when your request is answered. It should fetch contact data only when you ask for it. A domain mentioned in passing is not a reason to enrich that company.

Web sources and profile data can disagree. The assistant should cite sources and explain differences. Empty fields mean no data was returned; they do not prove that a person has no experience, skills or education.

The assistant chooses when to call tools. These instructions guide that choice; they do not guarantee automatic selection. EnvoAPI cannot see web search results unless the assistant passes a supported input to a tool.

Optional connector description

If your client lets you edit a connector description, use:

Find and enrich people and companies using public professional data. Use profile URLs and company domains from web search or the conversation to get professional background and company details. Also search jobs, posts and requested contact information.

Optional persistent instruction

If you want this workflow as a personal preference, use:

When I research people or companies, use available web search for discovery and EnvoAPI for relevant professional details. Reuse known profile URLs and company domains. Continue with the same subjects when I say “both” or “enrich more.” Fetch contact data only when I ask. Respect my spending limits and cite sources.

This preference is optional. The server already provides tool guidance.

Use an API key instead

If your client cannot use OAuth, create or copy a key from API keys. Use the same server URL and transport, then add this header in your client’s connection settings:

Authorization: Bearer <ENVO_API_KEY>

Replace <ENVO_API_KEY> with your key. Keep it in your client’s secret settings, never in a chat prompt or shared file. The MCP dashboard also has API key setup examples.

Credits and usage

Connecting and listing tools are free. Lookups use your account’s existing Credits and rate limit, just like REST API calls. There is no extra MCP charge.

One prompt may trigger several lookups. Repeating a request may spend Credits again. Check Usage to see what was used.

Successful contact lookups are charged in full even when contact fields are empty. You can limit work with a request such as “Use at most three EnvoAPI calls.” Tool descriptions do not provide a numeric price estimate, so an assistant should not promise to stay within a Credit budget it cannot verify.

On a failed lookup, the assistant should report the error and recovery steps. It should not automatically retry or switch tools to work around the error.

Result format

Successful calls return the same data and meta body as the public REST API. Tools also advertise their input and output schemas. Available paging and usage details appear in meta; transport status and headers are included in MCP result metadata for the client.

Manage connections

Open MCP in your dashboard and find Connected clients. Choose Disconnect to remove an OAuth client’s access. You can reconnect by signing in and approving access again.

For API key connections, revoke the key from API keys to stop access for every client using that key.

Need help?

• No sign-in prompt? Check the server URL and your client’s OAuth support. Use an API key if it supports custom headers instead.
• Tools missing or not being used? Enable EnvoAPI in the conversation, refresh the client’s tool list, or reconnect. Asking “Use EnvoAPI to…” can help check the connection, but should not be needed for every request.
• Lookup failed? Check your account status and Available Credits. If you hit the rate limit, wait before trying again. See Errors for details.