Back to settings
Claude Code

MCP

CodexClaude Code

Reference

Redoc
Codex CLI and IDE

Use OutreachGenie in Codex

Add OutreachGenie to Codex so local coding sessions can use workspace CRM tools through the MCP server.

MCP Server URL

https://api.outreachgenie.ai/mcp

API key env

LINKEDIN_CRM_API_KEY

Quickstart

1

Create an OutreachGenie API key

Open OutreachGenie settings. In OutreachGenie, open Settings and go to API keys. Create a workspace API key for Codex.

Set the key locally. Save the key in LINKEDIN_CRM_API_KEY on the machine where Codex runs. Restart Codex after changing environment variables so the process can read the token.

Use the hosted MCP server. Codex connects to https://api.outreachgenie.ai/mcp as a Streamable HTTP MCP server. Use NEXT_PUBLIC_MCP_API_BASE_URL when self-hosted docs should point to a different backend.

Create an OutreachGenie API key

LINKEDIN_CRM_API_BASE_URL=https://api.outreachgenie.ai
LINKEDIN_CRM_API_KEY=lo_live_xxx
OutreachGenie Settings -> API keys
2

Verify Runtime API access

Verify first. Run the verification request from the same machine where Codex will connect to the MCP server.

Expected result. The response should identify the workspace context. A 401 or 403 means the key is wrong, revoked, or not accepted by that backend.

Verify Runtime API access

curl -H "Authorization: Bearer $LINKEDIN_CRM_API_KEY" \
  "$LINKEDIN_CRM_API_BASE_URL/api/v1/runtime/auth/verify"
Successful workspace verification
3

Connect with the Codex CLI

Use the Codex CLI. Run this command once to add OutreachGenie as a named Streamable HTTP MCP server in Codex.

Bearer token environment variable. Codex reads LINKEDIN_CRM_API_KEY and sends it as the Authorization bearer token when calling the MCP server.

Confirm registration. Use codex mcp list, codex mcp get linkedin-crm, or /mcp inside Codex to confirm the server is enabled.

Connect with the Codex CLI

codex mcp add linkedin-crm \
  --url https://api.outreachgenie.ai/mcp \
  --bearer-token-env-var LINKEDIN_CRM_API_KEY
Codex MCP server list
4

Or edit config.toml

Manual config option. Add this block to ~/.codex/config.toml for a personal setup, or to a trusted project .codex/config.toml when the server should be repo-scoped.

Do not store the key in config. Keep the live key in LINKEDIN_CRM_API_KEY. The config should only name the environment variable.

Or edit config.toml

[mcp_servers.linkedin-crm]
url = "https://api.outreachgenie.ai/mcp"
bearer_token_env_var = "LINKEDIN_CRM_API_KEY"
enabled = true
startup_timeout_sec = 10
tool_timeout_sec = 60
Codex config.toml MCP block
5

Restart and confirm tools

Restart Codex. Restart the CLI or IDE session after adding the server or changing the API key environment variable.

Check the tool list. Use /mcp and start with a read-only verification prompt before importing prospects or creating lists.

Restart and confirm tools

/mcp

Use LinkedIn CRM MCP to verify my workspace connection.
Then list the available CRM tools before taking any write action.
Codex MCP status
6

What you can do

Use natural language. Ask Codex for the CRM outcome you want. The MCP server handles the underlying tools, so users do not need endpoint names.

Confirm write actions. For imports, list creation, or campaign preparation, ask for a summary first and approve the action only after the plan is correct.

Workspace checks

  • Confirm the connected workspace and available tools.
  • Check whether the current API key is valid before using write actions.
  • Ask the assistant to explain what it can do in this CRM workspace.
Prompt: Verify my LinkedIn CRM workspace connection and tell me which CRM tools are available.

Prospects

  • Look up a prospect by LinkedIn profile URL.
  • Summarize a CRM record before outreach.
  • Check whether a profile already exists before importing duplicates.
Prompt: Look up this LinkedIn profile URL and summarize the CRM record before I message them.

Prospect lists and imports

  • List existing prospect lists.
  • Create a list for a new audience, event, or search.
  • Import profile URLs into the right list and report created or matched records.
Prompt: Create a prospect list named Conference leads, import these LinkedIn profile URLs, and tell me which records were created or matched.

Flows and campaigns

  • Review which list should feed a campaign.
  • Use flow names, message intent, and list context to prepare an outreach plan.
  • Ask for a preflight summary before creating or changing campaign work.
Prompt: Use the Partner outreach flow with the Partner leads list and summarize the launch plan before creating campaign work.

Permissions and data scope

Workspace scoped

The MCP server works through a workspace API key. It only reaches data in the workspace connected to that key.

Read and write

Tools can read CRM context and perform write actions such as creating lists or importing prospects. Review assistant actions before approving changes.

Key rotation

Revoke and recreate a key from Settings -> API keys if a teammate leaves, the key is exposed, or an integration no longer needs access.

Troubleshooting

Authentication

Authentication errors usually mean the API key was copied incorrectly, revoked, or belongs to another workspace.

Connection

Connection errors usually mean the client cannot reach the configured backend or MCP server domain.

Do

Do not commit live workspace API keys to .mcp.json, config.toml, screenshots, or support tickets.

Support

Manage API keys

Rotate keys, revoke exposed credentials, or create a new MCP key.

Runtime reference

Open the Redoc reference for backend runtime endpoints.

On this page

QuickstartWhat you can doPermissionsTroubleshootingSupport