> ## Documentation Index
> Fetch the complete documentation index at: https://docs.genseo.co/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Server

> Connect Claude, Codex, Cursor, and other MCP clients to Genseo.

The hosted Genseo MCP server exposes project-bound SEO tools through the Model Context Protocol. It uses Streamable HTTP and the same allowlisted operations as the Genseo Public API.

## Endpoint

```text theme={null}
https://api.genseo.co/mcp
```

An MCP connection can only access the project attached to its authorization. It cannot enumerate a workspace, create projects, read billing data, or access internal database operations.

## Before you connect

You need:

1. A Genseo account and project.
2. A project-bound API key from **Project → Brand → API / Developer**.
3. An MCP client that supports Streamable HTTP or a local stdio process.

<Warning>
  Keep the key in environment or encrypted secret storage. Never place credentials in the MCP URL.
</Warning>

## Claude Code

Create `.mcp.json` in your plugin or project configuration:

```json theme={null}
{
  "mcpServers": {
    "genseo": {
      "type": "http",
      "url": "https://api.genseo.co/mcp",
      "headers": {
        "Authorization": "Bearer ${GENSEO_API_KEY}"
      }
    }
  }
}
```

Set the key before starting Claude Code:

```bash theme={null}
export GENSEO_API_KEY="gs_live_..."
```

Open `/mcp` and verify the `genseo` connection.

## Codex

Use an environment-backed Bearer token:

```json theme={null}
{
  "mcpServers": {
    "genseo": {
      "type": "http",
      "url": "https://api.genseo.co/mcp",
      "bearer_token_env_var": "GENSEO_API_KEY"
    }
  }
}
```

Then set the key before starting Codex:

```bash theme={null}
export GENSEO_API_KEY="gs_live_..."
```

## Other MCP clients

Configure the same Streamable HTTP endpoint and send this request header from the client's secure credential storage:

```text theme={null}
Authorization: Bearer gs_live_...
```

Clients that do not support remote HTTP MCP can use the local CLI server described below.

## Local stdio MCP

Install the Genseo CLI globally:

```bash theme={null}
npm install -g @genseo/cli
```

Configure the client to launch `genseo-mcp`:

```json theme={null}
{
  "mcpServers": {
    "genseo": {
      "command": "genseo-mcp",
      "env": {
        "GENSEO_API_BASE": "https://api.genseo.co/v1",
        "GENSEO_API_KEY": "${GENSEO_API_KEY}"
      }
    }
  }
}
```

Or run without a global installation:

```json theme={null}
{
  "mcpServers": {
    "genseo": {
      "command": "npx",
      "args": ["-y", "--package", "@genseo/cli", "genseo-mcp"],
      "env": {
        "GENSEO_API_BASE": "https://api.genseo.co/v1",
        "GENSEO_API_KEY": "${GENSEO_API_KEY}"
      }
    }
  }
}
```

## Verify the connection

Ask the agent:

```text theme={null}
Show the Genseo project connected to this account.
```

A successful connection calls `genseo_me` and returns the authorized project. If the returned project is unexpected, stop and replace the credential before using write tools.

## Available tools

| Area                | Read tools                                                                                | Write tools                                                                                         |
| ------------------- | ----------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| Account and project | `genseo_me`, `genseo_project_get`                                                         | —                                                                                                   |
| Keywords            | `genseo_keywords_list`, `genseo_keyword_metrics`                                          | `genseo_keywords_create`, `genseo_keywords_generate`                                                |
| Posts               | `genseo_posts_list`, `genseo_posts_get`                                                   | `genseo_posts_create_draft`, `genseo_posts_update`, `genseo_posts_generate`, `genseo_posts_publish` |
| Integrations        | `genseo_integrations_list`, `genseo_integration_fields`, `genseo_integration_connect_url` | `genseo_integration_mapping_save`                                                                   |
| Webhooks            | `genseo_webhooks_list`                                                                    | `genseo_webhooks_create`, `genseo_webhooks_delete`                                                  |

Every tool includes a human-readable title and safety annotations that identify read-only and potentially destructive operations.

## Required agent behavior

1. Call `genseo_me` before another Genseo tool.
2. Use only the returned project.
3. Read a post before updating it.
4. Prefer drafts before generation or publishing.
5. Check integrations before publishing.
6. Ask for confirmation before `genseo_posts_publish` unless autonomous publishing was explicitly requested.

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](https://github.com/Genseo-co/genseo-mcp) or follow the [AI Plugins guide](/developers/plugins).