Connect

Connect once. Skills + live data, inside your agent.

Connect your agent in a couple of clicks — the marketing-agent skills and the public-data MCP, in Claude, ChatGPT, OpenClaw, and more. Read-only, OAuth, no API key.

Read-only · OAuth One prompt, or a web connector $0.001 / record · no LLM key Browse agents

Pick your agent

Connect Claude

Web connector — the smoothest path

  1. 1

    Add UnifAPI to Claude

    One click opens Claude's Add custom connector dialog with the name and server URL already filled in:

    Add to Claude

    Check the two values, click Add, then Connect to sign in with OAuth.

  2. 2

    Prefer to set it up by hand?

    In Claude, open Settings → Connectors → Add custom connector.

    Name it "UnifAPI" and paste the server URL:

    https://mcp.unifapi.com

    Leave Authentication as OAuth, then Add and Connect.

  3. 3

    Try it with Claude

    “Use UnifAPI to pull the current top Hacker News story and summarize it.”

    Open Claude with task

Prefer raw HTTP, or wiring MCP by hand? The MCP docs cover the server URL, OAuth metadata, and the API-key bearer fallback.

Connect once, both halves

One pasted prompt (or a web connector) adds the public-data MCP server; npx skills add brings the marketing-agent skills. No API key to paste.

Read-only, OAuth

Sign in once in the browser. UnifAPI reads public data — it never posts, and it never holds your social or platform credentials. Eyes, not hands.

Reuse the assistant you have

Runs in the Claude, ChatGPT, or Codex plan you already pay for — no separate LLM key. UnifAPI bills only the public-data records returned, at $0.001 each.

FAQ

Connect & MCP questions

Connecting your agent, OAuth, billing, and the public-data boundary.

Any client that speaks the Model Context Protocol over Streamable HTTP can use UnifAPI. Verified setup shapes are documented for Claude, ChatGPT custom MCP apps, OpenClaw, Hermes, Claude Code, Codex, Cursor, and VS Code; other general-agent or app surfaces work when they expose a compatible remote MCP connector. The canonical server URL is https://mcp.unifapi.com. OAuth is recommended; API-key bearer headers are available for clients that require a static token.

Under a minute. Use the in-client listing when available, or add the UnifAPI MCP URL, authenticate in the browser when your client opens OAuth, and start asking your agent for public-data analysis. No API key needs to be pasted on the recommended path.

UnifAPI exposes three MCP tools over the live public-data operation catalog: list_operations to discover operations, get_operation to inspect parameters, schemas, examples, and billing metadata, and call_api to invoke a concrete operation. Skills and custom prompts use those tools to complete creator research, market monitoring, sales enrichment, SEO evidence, and other public-data workflows.

The MCP server is free to connect. Tool calls spend the same workspace credits as direct HTTP API calls, billed by returned records rather than a monthly subscription. Your first top-up includes a one-time credit bonus.

Not for the recommended OAuth path. Add https://mcp.unifapi.com, sign in when your MCP client opens the browser, and the token is bound to your UnifAPI workspace. API keys are only needed for clients that cannot handle OAuth and require an Authorization bearer header.