ConnectMachine's MCP server

ConnectMachine runs a remote MCP server, so any MCP-compatible AI tool can manage your contacts, events, networks, and digital cards through natural conversation. Nothing to install: your tool connects over HTTPS with your personal key.

✓Included with ConnectMachine accounts. A few advanced actions follow the same Premium rules as the app.

What the server exposes

The server publishes 40 focused tools. Your assistant picks the right one for each request; you never call tools by name.

Contacts (12 tools) - list, get, find, create, update, delete, smart search, industries, counts, duplicates, merge, and network assignment.
Events (3 tools) - list your events and attach or detach the event where you met a contact.
Networks (5 tools) - list, create, update, delete, and reorder your networks.
Digital cards (7 tools) - list, get, create, update, delete, read a shared card, and extract contact data from a card photo.
Import and export (6 tools) - batch import sessions, progress tracking, and CSV export.
Notifications and profile (7 tools) - notifications, unread counts, profile, and subscription status.

Important

AI query and meeting transcription tools are not exposed yet. They arrive with a later phase.

Get your MCP key

Your key is a personal bearer token tied to your ConnectMachine account. Open the MCP connect page and sign in with your account email (one-time code) or Google. The page shows your key plus ready-made config snippets for popular tools. Keys are managed by the backend and do not expire; keep yours secret, and remove the config from your tool to disconnect.

Connect page: licenses.connectmachine.ai/mcp/auth
Every request your AI tool makes is authenticated with this key against your account only.

Connect Claude

Claude supports remote MCP servers in the web app, desktop app, and Claude Code. For Claude web and desktop, open Settings, then Connectors, choose Add custom connector, and paste the server URL. For Claude Code, create .mcp.json in your project root with the snippet below (replace YOUR_MCP_KEY with your key) and restart Claude Code.

{
  "mcpServers": {
    "connectmachine": {
      "type": "http",
      "url": "https://mcp.connectmachine.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_MCP_KEY"
      }
    }
  }
}

Connect Cursor

Create or edit ~/.cursor/mcp.json (global) or .cursor/mcp.json inside a project, paste the snippet below, and replace YOUR_MCP_KEY with your key. Reload Cursor and the ConnectMachine tools appear in the MCP list.

{
  "mcpServers": {
    "connectmachine": {
      "url": "https://mcp.connectmachine.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_MCP_KEY"
      }
    }
  }
}

Connect VS Code

VS Code uses a servers object instead of mcpServers. Create .vscode/mcp.json in your workspace, paste the snippet below, and replace YOUR_MCP_KEY with your key.

{
  "servers": {
    "connectmachine": {
      "type": "http",
      "url": "https://mcp.connectmachine.ai/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_MCP_KEY"
      }
    }
  }
}

Connect Zed

Zed calls MCP servers context servers and supports remote ones natively, so there is no extension to install. Open Settings, then AI, then MCP Servers, click Add Server and choose Add Remote Server, or paste the snippet below into your Zed settings.json. With no Authorization header Zed runs the standard MCP OAuth flow and asks you to sign in on first use; add a "headers" object with your key if you prefer a static token.

{
  "context_servers": {
    "connectmachine": {
      "url": "https://mcp.connectmachine.ai/mcp"
    }
  }
}

Other MCP clients

Any client that supports remote HTTP MCP servers can connect with two values: the server URL and your key sent as a bearer token in the Authorization header. Clients that implement the MCP OAuth flow can also sign in through the browser; the server supports OAuth 2.0 with dynamic client registration and PKCE.

Server URL: https://mcp.connectmachine.ai/mcp
Auth header: Authorization: Bearer YOUR_MCP_KEY

How the tools behave

The server is designed so an assistant cannot quietly do the wrong thing with your network.

Same-name safety: when two contacts share a name, find_contact reports the ambiguity and instructs the assistant to ask you which one you mean instead of guessing.
Events, not tags: organizing follows the app. You attach the event where you met someone; free-form tagging is not exposed.
Smart search covers name, company, job title, email, phone, notes, location, meeting location, and event names.
New accounts: until you finish onboarding in the app, tools reply with guidance and app download links instead of empty results.

Plans and Premium actions

Connecting an AI tool is included with ConnectMachine. Actions that are Premium in the app stay Premium over MCP, such as CSV export and filtering by industry or location. When a free account hits one of these, the tool returns a clear message naming the feature and how to upgrade, never a silent failure.

Privacy and security

The MCP server is a thin, authenticated bridge to the ConnectMachine API. It stores no copy of your network.

Your key is validated against your account on every request; there is no cross-account access.
The assistant receives only the data needed to answer the specific request.
Disconnect anytime by deleting the config from your tool.
Terms and privacy: connectmachine.ai/en/legal/terms-of-service and connectmachine.ai/en/legal/privacy.

Troubleshooting

Most connection problems come down to the URL, the key, or account state.

Invalid key: sign in on the connect page again and use the key it shows.
Onboarding message: finish onboarding in the ConnectMachine app, then ask again.
Premium message: the action needs an upgraded plan; everything else keeps working.
Connection fails: confirm the URL is exactly https://mcp.connectmachine.ai/mcp and restart your AI tool after config changes.

Let’s create your

Digital Business Card