Integration

Autobound Content API integration

Autobound's AI Content API writes hyper-personalized sales outreach for one prospect: an email, a multi-step email sequence, a call script, a LinkedIn connection request, an SMS, an opener or a custom format. It resolves the prospect and the seller from an email or LinkedIn URL, ranks Autobound's insights about them (news, hiring, filings, social activity and more) and writes the content in a chosen writing style, language and length, returning the text with the insights it used. Each generation consumes Autobound credits (a sequence costs 2 credits per email). The Signal database is a separate Autobound product. Access requires a sales agreement with Autobound. Authentication is an API key sent in the X-API-KEY header, generated in the Autobound app settings; it is separate from the Autobound Signal API key.

Connect Autobound Content API How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Autobound Content API.Built from the 1 Autobound Content API tool below, on the connection you add once.

What you can do with Autobound Content API

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

generate_personalized_contentGenerate personalized contentPOSTWrites personalized outreach (email, sequence, call script, connection request, SMS, opener or custom) for one prospect from Autobound insights. Pass contactEmail or contactLinkedinUrl, userEmail or userLinkedinUrl, and contentType. Uses credits.

Use Autobound Content API from Claude Code, Cursor or Codex

Connect Autobound Content API in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Autobound Content API operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Autobound Content API

Create your workspace
Sign up free. Nothing to install.
Connect Autobound Content API once
Add your Autobound Content API connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.