Endpoint
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:- A Genseo account and project.
- OAuth support in the client, or a project-bound API key from Project → Brand → API / Developer.
- An MCP client that supports Streamable HTTP or a local stdio process.
Claude Code
Create.mcp.json in your plugin or project configuration:
/mcp and verify the genseo connection.
Codex
Use an environment-backed Bearer token:Other MCP clients
Configure the same Streamable HTTP endpoint and send this request header from the client’s secure credential storage:Local stdio MCP
Install the Genseo CLI globally:genseo-mcp:
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: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
- Call
genseo_meorgenseo_projects_listfirst. - Select one returned project and include its ID in every project tool.
- Read a post before updating it.
- Prefer drafts before generation or publishing.
- Check integrations before publishing.
- Use autonomous writes only when Agent Autonomy is enabled for the selected project.
202 Accepted as successful queueing.