MCP Server

The Dex MCP Server lets you manage your personal CRM directly from any AI client that supports the Model Context Protocol. Search contacts, log interactions, set reminders, organize your network, and work with your connected calendar and email — all through natural conversation with your AI assistant.

Works with Claude Code, Claude Desktop, Claude.ai, Cursor, VS Code (Copilot), Gemini CLI, Zed, Codex, Goose, OpenCode, and any other MCP-capable client.

Automatic install

If you have Node.js installed, this single command auto-detects every supported AI client on your machine and configures it:

npx -y add-mcp "https://mcp.getdex.com/mcp" -y

Restart your client(s) afterwards. You'll be prompted to authenticate via browser on first use.

Manual setup

Pick your client below. The MCP server URL is https://mcp.getdex.com/mcp and the transport is Streamable HTTP (not SSE).

If your client uses a generic JSON config file, this is the snippet to drop in:

{
  "mcpServers": {
    "dex": {
      "type": "http",
      "url": "https://mcp.getdex.com/mcp"
    }
  }
}

claude mcp add --transport http dex https://mcp.getdex.com/mcp

Available Tools

Once connected, your AI assistant gains access to the following tools for managing your Dex CRM:

Contacts

Notes & Timeline

Reminders

Tags

Groups

Custom Fields

Calendar

Reads span every connected calendar. Writes target a single account: your primary one unless you name another.

Email

Results are message metadata only — sender, participants, subject, snippet, date, and a link to open the message with your provider. Full message bodies are never returned. Without a date range, the search covers roughly the last six months.

What You Can Do

Here are some examples of what you can ask your AI assistant once connected:

Authentication

The MCP server supports two authentication methods.

Browser OAuth (Default)

On first connection, your AI client will open a browser window for you to log into your Dex account. The consent screen names the client that's connecting and whether it's requesting read or write access, and you approve or deny it explicitly. Credentials are cached for subsequent sessions.

API Key (Headless / CI)

For environments without a browser, use an API key:

Authorization: Bearer dex_your_key_here

{
  "mcpServers": {
    "dex": {
      "type": "http",
      "url": "https://mcp.getdex.com/mcp",
      "headers": {
        "Authorization": "Bearer dex_your_key_here"
      }
    }
  }
}

If your client supports the OAuth device authorization flow, you can use that instead of a key. The client shows you a code, you approve it in a browser on any machine, and the client receives its credentials without a browser on the headless box.

Data Model

The MCP server gives your AI assistant access to the full Dex contact graph:

Contact
├── Basic Info        — name, email, phone, company, job title, birthday
├── Social Profiles   — LinkedIn, Twitter/X, website
├── Description       — rich text notes about the person
├── Tags              — flat labels (e.g. "Investor", "College Friend")
├── Groups            — collections with emoji (e.g. "🏢 Acme Team")
├── Custom Fields     — user-defined (text, dropdown, date)
├── Notes / Timeline  — meetings, calls, coffees, general notes
├── Reminders         — follow-ups with optional recurrence
├── Keep in Touch     — cadence for staying in contact
└── Status            — starred, archived

Calendar events and emails are not stored in Dex. Those tools read live from the Google or Microsoft accounts you've connected under Settings → Sync & Integrations, so they only work once at least one account is linked.

Response Limits

Responses are capped at 25,000 characters. Use pagination with smaller page sizes for large result sets.

Troubleshooting

claude mcp remove dex
claude mcp add --transport http dex https://mcp.getdex.com/mcp