PersonalCRM: Stay close to the people who matter

PersonalCRM ships a built-in MCP server, the standard way to give AI assistants tools. Once connected, your assistant can read and write everything the web app can: contacts, pings, meetings, follow-ups and networks.

Endpoint: https://personalcrm.me/mcp (Streamable HTTP)

Two ways to authenticate:

Sign in with your account (OAuth): the default. Point any MCP client at the endpoint, a browser window opens, you sign in and approve. No keys to copy. Works with claude.ai, ChatGPT, Claude Code, Cursor, VS Code and any spec-compliant client.
API key as Bearer token: for headless setups and scripts. Create one in Settings → Developer; same rate limit (120 req/min) and tenant isolation as the REST API.

The fastest way to connect is Settings → Developer in the app. It has one-click installers and copy-ready snippets per client. The same setups by hand:

claude.ai & Claude Desktop

Settings → Connectors → Add custom connector, paste https://personalcrm.me/mcp, sign in when the browser opens. Connectors are shared between claude.ai and the desktop app.

ChatGPT

Settings → Connectors → Create (on some plans custom connectors sit behind Settings → Apps → Advanced → Developer mode). Name it PersonalCRM, paste https://personalcrm.me/mcp, set Authentication to OAuth, sign in when the browser opens.

Claude Code

claude mcp add --transport http personalcrm https://personalcrm.me/mcp

Then run /mcp once to authenticate in the browser. For headless machines, append --header "Authorization: Bearer pcrm_YOUR_KEY" instead.

Cursor / VS Code / other clients

Add the server to the client's MCP configuration. No headers needed, the client runs the OAuth sign-in on first use:

{
  "mcpServers": {
    "personalcrm": {
      "url": "https://personalcrm.me/mcp"
    }
  }
}

What the assistant can do

All 21 tools map 1:1 to the REST API: list/create/update/delete for contacts, meetings, follow-ups and networks, plus log_ping for check-ins. Destructive tools are annotated so well-behaved clients ask before deleting.

Example prompts:

"Here's a CSV export of my Notion contacts: import everyone, guess sensible ping frequencies, and put coworkers in a Work network."
"Who am I overdue to catch up with? Pick the top three and draft a short message for each."
"I just had coffee with Jane. Log a ping with a note that she started the new job at Vercel."
"Create follow-ups for everyone I met at the conference to reconnect in two weeks."

Good practice

One key per client (one for Claude Code, one for Desktop, …) so you can revoke individually.
The MCP server and the REST API expose the same capabilities: use MCP for interactive assistants, the REST API for scripts and automations.

MCP Server