Skip to Content
API ReferenceMCP Server

MCP Server

Use the hosted Genfeed MCP server to give AI clients API-key scoped access to content, workflows, publishing, analytics, and ads.

Endpoint: https://mcp.genfeed.ai/mcp

Transport: Streamable HTTP.

Authentication: Authorization: Bearer <gf_... API key>.

Open https://mcp.genfeed.ai for Claude Code and Codex setup.

Connect Genfeed

Open the guided Connect Genfeed flow  to select your client, create or select an MCP-scoped key, copy secret-safe configuration, and run an authenticated connection check.

Export the copy-once key where your MCP client runs:

export GENFEED_API_KEY=gf_live_xxx

Treat API keys like passwords. Do not commit them or paste them into shared logs.

Keys can also be created, scoped, rotated, and revoked from organization settings or the REST API — see API Keys. The mcp preset is approval-first: it can draft, schedule, and approve posts, but not publish directly.

Connect via OAuth

Claude.ai, ChatGPT, and other OAuth-capable MCP clients can connect without a manually created API key. Add https://mcp.genfeed.ai/mcp as the custom MCP server URL. The client discovers Genfeed’s authorization server from /.well-known/oauth-protected-resource, opens the Genfeed sign-in and consent screen, and returns to the client with a resource-bound access token.

The OAuth token appears in the same API key settings surface as manual keys and can be revoked there at any time. The manual GENFEED_API_KEY setup remains available for headless, CI, and local clients that do not support browser OAuth.

Connect Claude Code

Claude Code can connect remote HTTP MCP servers from the terminal:

claude mcp add --transport http genfeed --scope user https://mcp.genfeed.ai/mcp --header "Authorization: Bearer $GENFEED_API_KEY"

Verify with:

claude mcp list

You can also open /mcp inside Claude Code and inspect the genfeed server.

Connect Codex

Codex CLI and the Codex IDE share ~/.codex/config.toml. Add the server with:

codex mcp add genfeed --url https://mcp.genfeed.ai/mcp --bearer-token-env-var GENFEED_API_KEY

Equivalent config.toml:

[mcp_servers.genfeed]
url = "https://mcp.genfeed.ai/mcp"
bearer_token_env_var = "GENFEED_API_KEY"

Tools

Each call uses the permissions on the API key.

  • Content and media: articles, images, videos, music, avatars, batches.
  • Workflows: list, create, execute, inspect status.
  • Publishing: list and publish social posts.
  • Analytics and ads: analytics, campaigns, Google Ads, Meta Ads.
  • Agents and admin: threads, approvals, role-gated admin tools.

Skills

MCP gives an agent Genfeed’s tools; Agent Skills give it the content knowledge to use them well. Install the catalog with bunx skills add genfeedai/skills.

HTTP Details

The endpoint accepts POST, GET, and DELETE. Production requests must include:

Authorization: Bearer gf_live_xxx

Missing, invalid, or expired keys return 401 errors.

Local Self-Hosted Surface

Self-hosted Genfeed uses http://localhost:3014/mcp when the MCP service is running. Cloud uses:

https://mcp.genfeed.ai/mcp

Troubleshooting

  • Discovery fails: use exactly https://mcp.genfeed.ai/mcp and a Streamable HTTP client.
  • 401 errors: confirm GENFEED_API_KEY is set and sent as a bearer token.
  • Wrong endpoint: check /v1/config on the MCP host.
Last updated on
CLIEndpoint Reference