Skip to main content
The Genseo plugin combines workflow instructions with a connection to the hosted Genseo MCP server. One public repository supports Claude and Codex:
The plugin teaches compatible agents to call genseo_me first, stay inside the authorized project, prefer drafts, inspect integrations before publishing, and request confirmation before publishing unless autonomous publishing was explicitly requested.

​
What the plugin contains

No Genseo application source code or credentials are included in the plugin repository.

​
Claude Code developer install

Clone the public repository:
Create a project-bound API key in Genseo and expose it only to the Claude Code process:
Open /mcp in Claude Code and confirm that the genseo server is connected. Then ask Claude to show the connected Genseo project.

​
Codex developer install

The same repository includes a Codex manifest and environment-backed Bearer-token configuration. Set the API key before launching Codex:
You can also connect the hosted endpoint manually using the configuration on the MCP Server page.

​
Authentication

Developer installations currently use a project-bound Genseo API key. Store it in the client’s environment or encrypted secret storage. The public marketplace connection will use browser-based OAuth so users can select a project and approve access without copying an API key into the client.

​
Verify the connection

After installation:
  1. Confirm the genseo MCP server is connected.
  2. Call genseo_me.
  3. Verify the returned project name and domain.
  4. List a small number of keywords or posts.
  5. Test write actions with a draft, not a live publish action.
Publishing changes a live website through a configured CMS integration. Review the target post and request confirmation before publishing.

​
Support