Skip to main content
The hosted Genseo MCP server exposes allowlisted AI visibility, site health, and content tools through Streamable HTTP. ChatGPT and other marketplace clients connect with OAuth; local clients may use a project-bound API key. Start with the Genseo ChatGPT app guide if you use ChatGPT.

Endpoint

OAuth can list all projects available to the connected account. A chat selects one project and sends its project_id with every later tool call. API keys continue to expose only their bound project. MCP never exposes billing, project creation, project deletion, credentials, or internal database operations.

Before you connect

You need:
  1. A Genseo account and project.
  2. OAuth support in the client, or a project-bound API key from Project → Brand → API / Developer.
  3. An MCP client that supports Streamable HTTP or a local stdio process.
Keep the key in environment or encrypted secret storage. Never place credentials in the MCP URL.

Claude Code

Create .mcp.json in your plugin or project configuration:
Set the key before starting Claude Code:
Open /mcp and verify the genseo connection.

Codex

Use an environment-backed Bearer token:
Then set the key before starting Codex:

Other MCP clients

Configure the same Streamable HTTP endpoint and send this request header from the client’s secure credential storage:
Clients that do not support remote HTTP MCP can use the local CLI server described below.

Local stdio MCP

Install the Genseo CLI globally:
Configure the client to launch genseo-mcp:
Or run without a global installation:

Verify the connection

For OAuth-capable clients, add the remote endpoint and complete the browser sign-in described in OAuth connection. Then ask the agent:
A successful connection calls genseo_me or genseo_projects_list. Select one returned Project ID and keep it fixed for the chat.

Available tools

Every tool includes a human-readable title, JSON input/output schema, structured output, OAuth metadata, and safety annotations. See the complete MCP tool reference. Removal tools are retained for project-bound API-key compatibility. OAuth-connected Autopilot calls to destructive deletion tools are rejected with action_not_available.

Required agent behavior

  1. Call genseo_me or genseo_projects_list first.
  2. Select one returned project and include its ID in every project tool.
  3. Read a post before updating it.
  4. Prefer drafts before generation or publishing.
  5. Check integrations before publishing.
  6. Use autonomous writes only when Agent Autonomy is enabled for the selected project.
Treat authorization and project-boundary errors as final. Back off after rate limits and treat 202 Accepted as successful queueing.

Plugin package

For an installable package containing the MCP configuration and shared Agent Skills, use the public Genseo MCP repository or follow the AI Plugins guide.