Back to settings
Codex

MCP

CodexClaude Code

Reference

Redoc
Claude Code

Use OutreachGenie in Claude Code

Add OutreachGenie to Claude Code so terminal sessions can work with workspace prospects, lists, imports, and campaign context.

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 Claude Code.

Run from the same machine. Use the API key on the machine where Claude Code runs so the local client can authenticate to the MCP server.

Keep secrets local. Use local environment variables or private Claude Code config. Do not commit live keys to .mcp.json.

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 or network where Claude Code will connect to the MCP server.

Expected result. The response should identify the workspace context. Fix credential or domain errors before editing Claude config.

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 Claude Code

Claude Code. Run the command once from the machine where Claude Code runs. It stores a named HTTP MCP server entry for this client.

Confirm registration. Use claude mcp list, claude mcp get linkedin-crm, or /mcp inside Claude Code to confirm the server is active.

Team usage. Use project scope only when the team agrees to trust the shared MCP server entry. Do not commit live API keys.

Connect Claude Code

claude mcp add --transport http linkedin-crm \
  https://api.outreachgenie.ai/mcp \
  --header "Authorization: Bearer lo_live_xxx"
Claude Code MCP server list
4

Restart and confirm tools

Restart Claude Code. Start a new Claude Code session after adding or changing the MCP server.

Check the tool list. Use /mcp to confirm OutreachGenie is connected before asking it to read CRM context.

Project scope is optional. Use the project-scoped command only when you want a repo-level server entry. Do not commit actual API keys in .mcp.json.

Restart and confirm tools

/mcp

Use LinkedIn CRM MCP to verify my workspace connection.
Then list the available CRM tools.

Optional project scope:
claude mcp add --transport http linkedin-crm \
  --scope project https://api.outreachgenie.ai/mcp \
  --header "Authorization: Bearer lo_live_xxx"
Project-scoped MCP configuration
5

What you can do

Use natural language. Ask Claude for the CRM outcome. The MCP server handles the underlying tools, so teammates should use prospect, list, import, and flow language instead of 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