< MCP server >

Genfeed MCP.Claude + Codex.

Connect AI clients to Genfeed content, workflows, publishing, analytics, and ads with an API key.

Endpoint

Hosted Streamable HTTP. Use localhost only for self-hosting.

https://mcp.genfeed.ai/mcp

Setup

One server. Any client.

Export a Genfeed API key, then add the remote HTTP server to your client.

AI agent setup prompt

Copy/paste

Drop this into Claude Code, Codex, or another local agent with shell access. The agent detects the client, configures Genfeed, protects the API key, and verifies the result.

Set up the Genfeed MCP server on this machine.

Endpoint: https://mcp.genfeed.ai/mcp
Authentication env var: GENFEED_API_KEY
API key settings: https://app.genfeed.ai/settings/api-keys

Do this end to end:
1. Detect whether Claude Code, Codex, or both are installed.
2. Check whether GENFEED_API_KEY is available in the shell environment.
3. If the key is missing, ask me to export it locally or send me to the API key settings URL above. Do not request or paste the key into source-controlled files, command history, logs, or this chat.
4. Configure Genfeed as a remote Streamable HTTP MCP server:
   - Claude Code: claude mcp add --transport http genfeed --scope user https://mcp.genfeed.ai/mcp --header "Authorization: Bearer $GENFEED_API_KEY"
   - Codex: codex mcp add genfeed --url https://mcp.genfeed.ai/mcp --bearer-token-env-var GENFEED_API_KEY
   - If the Codex CLI is unavailable, update the user-level ~/.codex/config.toml with:

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

5. Verify the server appears in the client's MCP list or config.
6. Report exactly what changed and any manual step still required.

The prompt references GENFEED_API_KEY by env var so the key stays out of the page and config files.

Claude Code setup

HTTP transport
  1. 01

    Export API key

    Create a gf_ key in Genfeed settings.

    export GENFEED_API_KEY=gf_live_xxx
  2. 02

    Add MCP server

    Register the hosted endpoint in user scope.

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

    Verify

    Run claude mcp list or open /mcp.

Codex setup

CLI and IDE config
  1. 01

    Export API key

    Codex reads this env var for the bearer token.

    export GENFEED_API_KEY=gf_live_xxx
  2. 02

    Add MCP server

    The CLI and IDE share ~/.codex/config.toml.

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

    Manual config

    Paste this into a user or trusted project config.

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

Details

Endpoint. API auth.

MCP calls go to https://mcp.genfeed.ai/mcp and use the permissions on the API key.

Authentication

Bearer token

Send Authorization: Bearer gf_live_xxx with every request.

Manage keys

Transport

HTTP transport

Register Genfeed as a remote MCP server. No npx or localhost for cloud.

View config

Status

Health checks

Use health and config to debug routing or stale client settings.

View health
! Keep API keys out of commits and shared logs.