MCP server

Create an API key in the console under Agents & API first. The agent acts as your workspace: it can do what the API allows with that key, and nothing more. Console sessions are refused here; use a key.

Claude Code

claude mcp add --transport http outvoy https://api.getoutvoy.com/mcp \
  --header "Authorization: Bearer ov_..."

Add --scope user to make it available in every project. Run /mcp inside Claude Code to check the connection.

Claude Desktop

Claude Desktop starts local servers, so bridge the remote one with mcp-remote (it needs Node.js for npx). Open Settings → Developer → Edit Config, add this to claude_desktop_config.json and restart Claude:

{
  "mcpServers": {
    "outvoy": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://api.getoutvoy.com/mcp",
        "--header",
        "Authorization:${OUTVOY_AUTH}"
      ],
      "env": { "OUTVOY_AUTH": "Bearer ov_..." }
    }
  }
}

The header goes through an environment variable because Claude Desktop splits arguments on spaces.

Cursor

Add this to ~/.cursor/mcp.json, or to .cursor/mcp.json in a project:

{
  "mcpServers": {
    "outvoy": {
      "url": "https://api.getoutvoy.com/mcp",
      "headers": { "Authorization": "Bearer ov_..." }
    }
  }
}

Other clients

Any MCP client that supports streamable HTTP and custom headers works the same way: the URL above and an Authorization header. GET and DELETE on /mcp answer 405. A 401 never carries a WWW-Authenticate header, so clients don't fall into an OAuth discovery loop; if a call fails with 401, check the key.

curl https://api.getoutvoy.com/mcp \
  -H "Authorization: Bearer $OUTVOY_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{ "jsonrpc": "2.0", "id": 1, "method": "tools/call",
        "params": { "name": "whoami", "arguments": {} } }'

{
  "result": {
    "content": [
      {
        "type": "text",
        "text": "{\"data\":{\"apiKey\":{\"id\":\"key_gLG1KlUD\",\"name\":\"Claude Code\"},\"workspace\":{\"id\":\"org_dzfEWWtX\",\"name\":\"Acme\",\"plan\":\"growth\",\"planName\":\"Growth\",\"limits\":{\"linkedinSenders\":3,\"includedLinkedinSenders\":3,\"extraLinkedinSenders\":0,\"sandboxSenders\":5,\"enrollmentsPerMonth\":3000,\"liveCampaigns\":20},\"billing\":{\"source\":\"subscription\",\"status\":\"trialing\",\"trialEndsAt\":\"2026-11-04T14:46:02.690Z\",\"renewsAt\":\"2026-11-04T14:46:02.690Z\"},\"usage\":{...}}}}"
      }
    ]
  },
  "jsonrpc": "2.0",
  "id": 1
}

A tool answers with the same { data, meta } JSON the REST endpoint returns, as text content. A refused call is a tool result with isError: true and the same { errorCode, message, details? } the REST API answers as its text, never a JSON-RPC error. Arguments a tool doesn't know are refused (422 UNPROCESSABLE_CONTENT, naming the field in details.issues), so a misspelled argument fails loudly instead of being ignored.

Tools

Each description states the domain rules (for example, that a launch enrolls every eligible lead, or that messages only go to connected people), so the agent doesn't have to discover them by failing. On initialize the server also sends instructions: start with whoami, rehearse with a sandbox sender, always preview before launching. Tools that act on LinkedIn or delete things carry destructiveHint, so well-behaved clients ask before running them.

Example prompts

• “Create a sandbox sender called Lena and run a test campaign against 10 people from a search for heads of RevOps in Germany. Show me the preview first.”
• “Import everyone who reacted to or commented on this post into a list called Webinar follow-up: <post URL>.”
• “Draft a three-step campaign for the RevOps DE list: visit, invite with a note under 200 characters that mentions their company, then a message two days after they accept. Preview it and fix every issue before you ask me to launch.”
• “Which leads in RevOps DE are waiting, and why?”
• “Summarize every reply from the last 24 hours and draft an answer for each. Don't send anything yet.”
• “Block everyone at Globex from every campaign.”