API and MCP

OutreachGenie developer resources.

Use the hosted MCP server when an agent needs workspace tools. Use the OpenAPI contract when a developer needs the typed runtime API underneath those tools.

Streamable HTTP

Hosted OutreachGenie MCP server

The production endpoint is https://api.outreachgenie.ai/mcp. It requires a workspace API key in the Authorization bearer header. The key limits tools to the connected OutreachGenie workspace. Keep it in an environment variable, do not commit it, and rotate it if it is exposed.

What the MCP tools cover

  • Verify the workspace connected to an API key
  • List and create prospect lists
  • Look up, import, attach, and update prospects
  • List, inspect, and create outreach flows
  • Inspect the template fields available to a flow
  • Prepare a runtime campaign from an approved flow and list

Approval boundary

Read operations can verify access and inspect workspace state. Before creating a list, importing or updating a prospect, creating a flow, or preparing a campaign, show the intended change and ask the user to approve it.

OpenAPI 3.0.3

Typed runtime API

The official OpenAPI document describes the authenticated runtime endpoints used by the extension and MCP server. Every operation has a unique operation ID, description, typed request data, and response schema. The production server is https://api.outreachgenie.ai. Requests use the same workspace bearer key as MCP.

Errors an agent can recover from

API discovery routes return JSON or RFC 9457 problem details, including a stable code, a plain-language detail, and a resolution hint. The MCP endpoint returns JSON-RPC errors. A missing bearer key returns 401 and explains that a workspace API key is required.

Command line setup

Connect Codex or Claude Code

OutreachGenie does not publish a separate general-purpose CLI. The supported command line path is the MCP command built into the agent host. Follow the official setup page for the exact command, keep the bearer token in an environment variable, then restart the agent host so it can discover the tools.

Machine-readable discovery

Stable resource URLs

Agents and registries can use the files below without signing in. They identify the authenticated service and its documentation; they do not expose a user's workspace data or API key.