Connect Meshi to AI Agents (MCP)

Meshi’s MCP (Model Context Protocol) server lets an AI agent use the Meshi context you already have: your profile, goals, network, and shared event context. The connection is personal—your Meshi account authorizes your own agent, not an organization-wide data export. Mutual-fit matching is the one place your agent looks beyond your own connections, and it sees exactly what Meshi’s own discover view already shows you.

Connect your agent

ChatGPT app

These steps apply to the ChatGPT desktop app, including its Codex experience.

Open Settings, then select Plugins.
Select the MCPs tab, then choose Add server.
Name the server Meshi, choose Streamable HTTP, and enter:
```
https://api.meshi.io/mcp/public
```
Save the server. In the server list, enable Meshi if needed, then select Authenticate and complete the Meshi sign-in and consent flow in your browser.

In a new conversation, type /mcp to confirm Meshi is connected. Start with: “What’s my Meshi context right now?”

ChatGPT on the web manages remote tools through workspace plugins; it does not read your local ChatGPT app or Codex MCP configuration.

Codex CLI

Run:

codex mcp add meshi --url https://api.meshi.io/mcp/public
codex mcp login meshi

The login command opens the Meshi sign-in and consent flow in your browser. Confirm the connection with:

codex mcp list

Start a new Codex session after connecting. In the session, use /mcp to see the available Meshi tools.

Claude Cowork

In Claude, open Customize → Connectors.
Select + next to Connectors, then Add custom connector.
Enter the name Meshi and this URL:
```
https://api.meshi.io/mcp/public
```
Select Add, then sign in to Meshi and approve the requested read access.
In a conversation, open the + menu in the chat input, choose Connectors, and make sure Meshi is toggled on for that conversation.

On Claude Team and Enterprise plans, an Owner or Primary Owner must first add the connector in Organization settings → Connectors → Add → Custom → Web. Each member then connects their own Meshi account from Customize → Connectors. On the Free plan, only one custom connector can be active at a time.

Claude Cowork connects to remote MCP servers from Anthropic’s cloud, not from your computer. Meshi’s public HTTPS endpoint is designed for this; local Claude Desktop configuration files are not used by Cowork.

Claude Code

Run:

claude mcp add --transport http meshi https://api.meshi.io/mcp/public

Restart Claude Code if it is already open, then complete Meshi sign-in and consent when Claude prompts you to authenticate. Use Claude Code’s MCP management view to confirm that Meshi is connected before asking it to use Meshi context.

Endpoint

Use the production endpoint for normal use:

https://api.meshi.io/mcp/public

For testing only, use the staging endpoint with a staging Meshi account:

https://api.staging.meshi.io/mcp/public

The endpoint is a public, stateless Streamable HTTP MCP server. It uses OAuth 2.0 with PKCE, so you sign in to Meshi in your browser and approve access—do not paste a Meshi API key into an AI client.

What your agent can do

Meshi MCP exposes five tools. Four read; one writes. They use the same visibility rules as your Meshi account.

Tool	What it does
`get_my_context`	Returns your identity, active goals, how many people are in your Meshi network, and relevant Meshi event context.
`search_people`	Searches your network—or a shared event’s attendees—by meaning, by keyword, across work history, across imported profile text, or all of them fused together. Results are paged.
`get_person_brief`	Retrieves a pre-meeting brief for a person you can view in Meshi, with each claim labelled by how Meshi knows it.
`get_mutual_fit`	Ranks people by mutual fit with your goals—whether what each of you needs matches what the other offers. This is the one tool that looks beyond your own connections, and it returns the same matches Meshi’s discover view already shows you.
`confirm_goal`	Records a goal you have told your agent you are working on. This is the only tool that changes your Meshi data.

The four read tools request the meshi:read permission. confirm_goal requires meshi:write; if you connected Meshi before that tool existed, your agent will not see it until you reconnect and approve the new permission. Nothing else changes for you in the meantime.

Meshi still cannot change your profile, contacts, or event data through this connector—confirm_goal writes goals, and nothing else.

Use Meshi in a conversation

Once connected, ask a natural-language question about the people and context available to you in Meshi. For example:

What's my Meshi context right now?

Who in my network could help me understand enterprise procurement?

Find people I know who work in climate technology and have fundraising experience.

Give me a brief on Priya Shah before our meeting.

Who should I meet about hiring a founding engineer?

Find people in my network who used to work at Stripe.

Your agent chooses whether to call Meshi for a request. When Meshi is relevant, begin with your context or make the Meshi source explicit in the question.

Privacy and safety

Each client completes its own Meshi OAuth sign-in and consent flow. Connecting Meshi in one client does not automatically authorize another.
Meshi only returns data visible to the Meshi account you authorize.
Every tool reads except confirm_goal, which records a goal you stated. Your AI client should ask before running it; the read tools run without a prompt.
get_mutual_fit ranks people from across Meshi, not only your connections. It returns the same match signal Meshi’s own discover view shows you—scores, the matched goals on both sides, and name, role and company—and deliberately returns no profile prose about someone you are not connected to.
Only connect Meshi from the official endpoint above. Review the permissions displayed by your AI client before approving them.

Disconnect

Disable or remove Meshi from the same MCP or connector settings where you added it. You can reconnect later and will be asked to sign in again if your session has expired.

Troubleshooting

You see	What it means
A browser sign-in window never opens	Retry authentication from the client’s MCP or connector settings. Check that the client can open a browser and reach `api.meshi.io`.
`onboarding_required`	Finish onboarding at my.meshi.io, then retry.
`forbidden` when requesting a person brief	That person is not visible to you in Meshi.
`rate_limited` or HTTP 429	You have reached the current limit of 60 calls per minute or 2,000 per day. Wait for the retry window, then try again.
Meshi is connected but the agent does not use it	Start a new conversation and explicitly ask a Meshi-related question, such as “Search my Meshi network for …”.