Skip to main content

Setting up and using a Custom MCP Connector

This is a step-by-step guide to setting up a custom MCP (Model Context Protocol) connector in the Claude Desktop app and using it to query data. It also covers how to do the same task using Codex

A
Written by Alex Montenegro

Use cases for an MCP connector

  • Account research: Ask Codex to pull account history before a call, without switching tabs

  • Pipeline hygiene: Find stale accounts or untouched prospects and get a task list back

  • Reporting on demand: Ask for engagement stats by campaign instead of building a dashboard

Using Claude

Adding the Custom Connector

  1. Click on your profile/account icon in the bottom-left corner of the Claude Desktop app and select Settings.

  2. In the Settings panel, click Connectors on the left menu, then click the Customize link.

  3. Add the custom connector:

    1. Click +Add custom connector near the top left.

    2. Enter a Name for the connector (e.g., Breakout).

    3. Enter the Remote MCP server URL (e.g., [https://server.prod.meaku.ai/mcp](https://server.prod.meaku.ai/mcp)).

    4. Click Add.

Authenticating and Authorizing

  1. Locate your new custom connector in the list and click Connect. A web browser window will launch automatically.

  2. Enter your user credentials and click Sign in.

  3. Review the permission requirements and click Authorize Claude.

  4. Once the confirmation screen appears, click Open desktop app to return to Claude Desktop.

Querying Data in Claude Chat

  1. Navigate to a new chat window in the app.

  2. Enter a data query into the chat box (e.g., "Tell me all the accounts that visited me in the last week") and send.

  3. When Claude requests permission to use a tool from your integration, click Allow for this task.

  4. Analyze and ask follow-up questions:

    • Review the formatted table and data insights provided by Claude.

    • Ask follow-up questions to drill deeper into the data (e.g., asking about visit frequency, conversation types, or specific transcripts) and approve additional tool permissions as prompted.

Using Codex

Let Codex search and act on your Breakout data (accounts, prospects, engagement stats, and sessions) through a remote MCP server—no local install needed.

Key features

With the Breakout MCP connector, Codex can:

  • Search and filter accounts across your Breakout data

  • Pull prospect records and enrichment details

  • Query engagement stats across campaigns and sequences

  • Search session data for activity history

  • Act on Breakout records directly from a conversation

"Which accounts have gone quiet in the last 30 days?" "Pull engagement stats for the Q3 outbound sequence." "Find prospects at companies with 50+ employees who haven't been contacted yet."

Connecting the Breakout MCP server

Codex CLI

  1. Set up and connect a remote MCP server in my Codex config.

    1. Name: breakout

    2. Type: remote / streamable-HTTP MCP server (NOT stdio — no command to run)

    3. URL: https://server.prod.meaku.ai/mcp/

    4. Auth: OAuth 2.1 — Dynamic Client Registration (RFC 7591) + PKCE (S256) with an RFC 8252 loopback redirect. It self-registers, so there is NO pre-set client_id or client_secret to configure.

  2. Add it to my Codex MCP config—edit ~/.codex/config.toml with an [mcp_servers.breakout] entry pointing at that URL or use codex mcp add

  3. In codex > open chat and give the prompt mentioned above and follow the process of adding the MCP

Did this answer your question?