MCPModel Context Protocol

LinkedIn MCP server for profiles, companies, and jobs

Research public LinkedIn profiles, companies, and jobs from the assistant you already use. EnvoAPI’s LinkedIn MCP server connects Claude, ChatGPT, and other compatible assistants to tools that retrieve professional data from your request.

https://api.envoapi.com/mcp

Get your free API key View setup guide

Hosted by EnvoAPI, with no server for you to manage.
No LinkedIn login, session cookie, or browser session required.

Connection

LinkedIn MCP server URL and connection details

EnvoAPI’s LinkedIn MCP server URL is:

https://api.envoapi.com/mcp

Add this endpoint as a remote server in your assistant’s connection settings. The address is the same for supported clients, but adding it alone does not authorize lookups. Complete authentication with your EnvoAPI account or API key before requesting data.

Connection settings
Transport	Streamable HTTP
Authentication	EnvoAPI OAuth or bearer API key
Hosting	Managed by EnvoAPI

Research

What can your assistant research?

The EnvoAPI LinkedIn MCP connector exposes 35 read-only tools. Start with a known public URL to retrieve details, or use search to identify the right person, company, or listing first.

Example session

Northstar sales lead

Who runs sales at northstar.com? Pull their LinkedIn background.

EnvoAPIRunning…Used 3 tools

search_companies_by_domainnorthstar.com

get_company_peopleNorthstar Analytics · “sales”

get_profile_details/in/maya-chen

Northstar’s sales team is led by Maya Chen, VP of Sales, based in Austin. She joined in 2021 after six years leading enterprise sales at Ridgeline.

nameMaya Chen

headlineVP of Sales · Northstar Analytics

locationAustin, Texas

previousHead of Enterprise Sales · Ridgeline

ChatGPT

Who runs sales at northstar.com? Pull their LinkedIn background.

Calling EnvoAPI · search_companies_by_domain…

Called tool search_companies_by_domain

Calling EnvoAPI · get_company_people…

Called tool get_company_people

Calling EnvoAPI · get_profile_details…

Called tool get_profile_details

Northstar’s sales team is led by Maya Chen, VP of Sales, based in Austin. She joined in 2021 after six years leading enterprise sales at Ridgeline.

FieldDetail

NameMaya Chen

TitleVP of Sales · Northstar Analytics

LocationAustin, Texas

PreviousHead of Enterprise Sales · Ridgeline

Illustrative session · tool names are real, results are synthetic

Public data you can research
Research task	Starting input	Available information
Profiles	A public LinkedIn profile URL	Professional background, experience, and other available profile details.
Companies	A company page or website domain	Company details and related people, job, and post research.
Jobs	Role keywords, a location, or a company	Matching listings and available job details.
Public posts	A post URL or search terms	Post content and available comments or reactions.

Discovery and detail lookups can take separate calls. For example, a company domain may need to be matched to the correct company before retrieving its details. Returned fields depend on the selected tool and the public information available.

Supported clients include Claude, ChatGPT, Claude Code, Codex, Cursor, VS Code, and OpenCode. Connection options depend on the client and your account or workspace settings.

Setup guide

Connect LinkedIn MCP to Claude

Have your EnvoAPI account ready, then choose the connection method for your client. OAuth lets you approve access through your browser.

1Choose how to connect

Claude · OAuth

Add the EnvoAPI connector

In Claude, open Customize → Connectors and choose Add custom connector.
Enter EnvoAPI as the name and https://api.envoapi.com/mcp as the server URL.
Continue through the detected authentication settings and select the sign-in option.
Follow the remaining steps to authorize your EnvoAPI account and finish adding the connector.
Enable EnvoAPI in your conversation before making a request.

Workspace policies and account settings can affect connector availability. The authorization is for EnvoAPI; it does not connect a LinkedIn session.

Connect with Claude Code

Add the hosted server from your terminal:

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

Open Claude Code, run /mcp, select envoapi, and complete authorization. Run claude mcp list in your terminal to inspect the connection.

Use an API key when your client requires one

If your client supports custom headers instead of OAuth, add this header in its secure connection settings:

Authorization: Bearer <ENVO_API_KEY>

Replace the placeholder with your key. Keep real keys out of chat prompts and shared files.

2Run a lookup

Run your first profile lookup

Replace the placeholder with a public profile URL and try:

Use EnvoAPI to look up [PUBLIC_LINKEDIN_PROFILE_URL]. Make one profile-details call and summarize the returned professional background. Mark missing information as “not returned” and separate facts from interpretation. Ask before another lookup or retry.

Your assistant passes the URL to the relevant tool, receives structured data, and summarizes the returned fields. Successful responses include data and meta; available metadata varies by tool. Review the result before expanding your research.

For more client-specific instructions, read the MCP connection guide.

Job search

LinkedIn MCP job search for roles and hiring research

Bring public job listings into your assistant to explore roles or research a company’s hiring activity. Start with a focused question and a small result set.

Find roles that match your criteria

Describe the role and location you want to explore. Your assistant uses the available search tools and supported filters to build a shortlist.

Search for [ROLE] jobs in [LOCATION] using EnvoAPI. Use at most three data calls, including any location-resolution step. Show up to five returned listings with title, company, location, and URL where available. Ask before fetching more pages or details.

Research a company’s public job listings

Explore advertised roles to prepare for an interview, research an account, or identify questions for a hiring team.

Find up to five job listings for [COMPANY_URL]. Group the returned roles by function and explain what they may suggest about hiring priorities. Separate observed listings from your interpretation. Use at most three data calls and ask before doing more.

Listings may have changed since publication, so check the original vacancy before applying. Hiring patterns can suggest questions to investigate; they do not prove growth or purchase intent. EnvoAPI’s tools do not submit applications or retrieve private applicant data.

Building a job-data feature? Explore job data for your application.

Credits

How MCP lookups use your credits

Connecting and discovering tools are free. Data lookups use your EnvoAPI account’s existing credit balance and rate limits, with no additional MCP access fee.

One prompt can trigger several chargeable requests. Finding a company, identifying a person, and retrieving their background may require separate calls. More pages, additional details, and repeated requests can use more credits.

Ask your assistant to use at most three data calls and stop before additional lookups or retries. This instruction limits the requested work; it is not a guaranteed credit budget. Costs vary by operation, and successful contact lookups can consume credits even when no contact information is returned.

Eligible verified accounts receive 100 one-time credits, with no credit card required. These starter credits are not a recurring monthly allowance. Check your account usage to see what each research session consumed.

View pricing

Security and access

Read-only access you control

Read-only tools
Authorizing EnvoAPI lets your assistant retrieve supported data through your account. The tools do not edit profiles, publish posts, send messages or invitations, or submit job applications. Read-only requests still retrieve data and can spend credits.
No LinkedIn session
You do not supply a LinkedIn password, cookie, proxy, or browser session. OAuth authorizes your EnvoAPI account, and an API key provides an alternative for clients that support bearer authentication.
Disconnect anytime
To remove OAuth access, open the MCP area of your EnvoAPI dashboard, find the connected client, and choose Disconnect. For an API-key connection, revoke the key separately. Revoking a shared key stops access for every client using it.
Focused requests
Keep requests focused on the information you need. Ask your assistant to report failed lookups and get your approval before expanding the research or retrying.

FAQ

LinkedIn MCP FAQs

What does a LinkedIn MCP connector do?

An MCP connector lets an AI assistant discover and call supported tools through the Model Context Protocol. With EnvoAPI, those tools retrieve public professional data for profile, company, job, and post research. You describe the task in plain language; the assistant selects tools and summarizes the information they return.

Is EnvoAPI an official LinkedIn MCP server?

No. EnvoAPI is an independent service and is not affiliated with or endorsed by LinkedIn. You authorize access through your EnvoAPI account using OAuth or an API key. You do not provide a LinkedIn login or session cookie, and the connector does not act through your personal LinkedIn account.

Should I use MCP or the REST API?

Use MCP when you want an assistant to choose tools and help you research in a conversation. Choose the REST API when you are writing application code and want to manage requests, responses, pagination, and errors directly. For the application integration path, explore the LinkedIn data API.

Why are tools unavailable or fields missing?

If tools are missing, check that EnvoAPI is enabled in your conversation, then refresh the tool list or reconnect. An empty field means no value was returned; it does not prove the information does not exist. For a failed lookup, check the reported authentication, credit, or rate-limit error. Your assistant should explain gaps instead of filling them with guesses.