How do I install Odiseo?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Odiseo need an API key?

No required environment variable is listed on this record.

When was Odiseo last checked?

Last checked 2026-11-08. SEO layer for agents: research, content, QA, approvals and publishing via MCP OAuth.

Odiseo MCP server

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://www.odiseo.help/api/mcp

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

1claude mcp add --transport http help.odiseo-mcp https://www.odiseo.help/api/mcp

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "help.odiseo-mcp": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://www.odiseo.help/api/mcp"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 0.1.0
Last checked

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

Odiseo CLI

Connect Codex, Claude Code, Cursor, or OpenClaw to the Odiseo SEO MCP from one command.

Odiseo gives an agent the tools to research a site, build briefs and content plans, create and review articles, and operate the publication workflow inside the organization you authorize.

Requirements

Node.js 20 or newer
An Odiseo account whose organization has MCP access
One supported client: Codex, Claude Code, Cursor, or OpenClaw

Quickstart

Authenticate in the browser with the OAuth device flow:

npx odiseo-cli login

Then install Odiseo in your client:

npx odiseo-cli mcp install cursor

Replace cursor with codex, claude, or openclaw. Finally, verify the credential and MCP endpoint:

npx odiseo-cli mcp doctor

The login command shows a short code and opens the Odiseo approval page. The resulting session is stored in ~/.config/odiseo/config.json with owner-only permissions. The install command places that bearer credential in the selected client's user-level MCP configuration.

Commands

`odiseo login`

Starts the OAuth device authorization flow:

odiseo login
odiseo login --no-open

For local development:

odiseo login --base-url http://localhost:3000 --no-open

Advanced users can authenticate with an existing Odiseo MCP API key instead:

odiseo login --key seoap_your_key

API keys can be scoped to a site and a narrower permission set. Browser OAuth and device authorization represent the complete organization membership.

`odiseo mcp install`

Installs an authenticated Streamable HTTP server definition:

odiseo mcp install codex
odiseo mcp install claude
odiseo mcp install cursor
odiseo mcp install openclaw

The default endpoint is https://odiseo.help/api/mcp. Override it for a local or self-hosted environment:

odiseo mcp install cursor --endpoint http://localhost:3000/api/mcp

Client behavior:

Client	Installation method
Cursor	Merges `odiseo` into `~/.cursor/mcp.json`
Codex	Replaces only `[mcp_servers.odiseo]` in `~/.codex/config.toml`
Claude Code	Runs `claude mcp add` in user scope
OpenClaw	Runs `openclaw mcp set` with Streamable HTTP transport

Cursor and Codex config files are written atomically with mode 0600. Claude Code and OpenClaw own and protect their respective configuration stores.

`odiseo mcp doctor`

Sends a real MCP initialize request with the stored credential:

odiseo mcp doctor
odiseo doctor

It reports the MCP server name, protocol version, and latency. It also gives specific guidance for expired credentials, missing subscription access, and HTTP authentication failures.

`odiseo logout`

Removes the credential stored by this CLI. Client configurations are left in place so you can re-run odiseo login and odiseo mcp install <client> without losing unrelated settings.

Connect without the CLI

Every supported client can also use Odiseo's native MCP OAuth discovery. Add only this URL:

https://odiseo.help/api/mcp

For example:

codex mcp add odiseo --url https://odiseo.help/api/mcp
codex mcp login odiseo

claude mcp add --transport http odiseo https://odiseo.help/api/mcp

openclaw mcp set odiseo \
  '{"url":"https://odiseo.help/api/mcp","transport":"streamable-http","auth":"oauth"}'
openclaw mcp login odiseo

Cursor users can use the Add to Cursor button on odiseo.help/mcp.

Security

The CLI never prints a saved bearer token.
File writes are atomic and use owner-only permissions where supported.
Child processes are launched directly, never through a shell.
OAuth/device credentials grant access to the authorized organization.
Publishing and approval tools remain high-impact actions: agents should call them only after an explicit user instruction.
Use a site-scoped seoap_ API key when a narrower long-lived credential is preferable.

If a credential is exposed, revoke it in Odiseo and run odiseo login again.

Development

npm install
npm run typecheck
npm test

Build output is generated in dist/. The package has no runtime dependencies.

License

MIT

Odiseo

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Odiseo?

Does Odiseo need an API key?

What transport does Odiseo use?

When was Odiseo last checked?

Documentation

Odiseo CLI

Requirements

Quickstart

Commands

`odiseo login`

`odiseo mcp install`

`odiseo mcp doctor`

`odiseo logout`

Connect without the CLI

Security

Development

License