AI Outreach MCP Connector

Connect MCP-compatible clients (and Perplexity Remote MCP when it rolls out) directly to the AI Outreach API using a hosted URL. Your client sends your `X-API-Key`; we forward calls to public API endpoints (including `/api/v1/*` and select webhooks/public feeds).

Endpoints

https://aioutreach.io/mcp/httphttps://aioutreach.io/mcp/sse

Use `HTTP` when possible (stateless, no session affinity). `SSE` is provided for legacy clients.

Authentication

Send your AI Outreach API key as either:X-API-Key: amai_…orAuthorization: Bearer amai_…

Client Config Examples

Goal: URL-based remote MCP connection (no `npx`, no local installs).

VS Code (`.vscode/mcp.json`)

{
  "servers": {
    "aioutreach": {
      "type": "http",
      "url": "https://aioutreach.io/mcp/http",
      "headers": {
        "X-API-Key": "amai_YOUR_KEY"
      }
    }
  }
}

Cursor (`~/.cursor/mcp.json`)

{
  "mcpServers": {
    "aioutreach": {
      "transport": { "type": "http" },
      "url": "https://aioutreach.io/mcp/http",
      "headers": {
        "X-API-Key": "amai_YOUR_KEY"
      }
    }
  }
}

Some clients name the top-level key `servers` instead of `mcpServers`. If Cursor rejects this, paste the endpoint URL and add the header in the UI if available.

Tools Exposed

We keep tools narrow and typed; expensive operations require explicit confirmation flags.

public_routes_listList all public HTTP routes (from `/api/openapi`)

public_api_callCall a public HTTP route by path+method (writes require confirmWrite=true)

credits_getGET /api/v1/credits

forms_listGET /api/v1/forms

forms_createPOST /api/v1/forms

leads_submitPOST /api/v1/leads (requires confirmCreditCost=true)

workflow_statusGET /api/v1/workflows/{id}/status

Perplexity’s own help center notes Remote MCP is rolling out; see Local and Remote MCPs for Perplexity.