English Français العربية

Odiseo

Official registry Search and web

SEO layer for agents: research, content, QA, approvals and publishing via MCP OAuth.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http odiseo 'https://www.odiseo.help/api/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "odiseo": {
            "type": "http",
            "url": "https://www.odiseo.help/api/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Odiseo CLI
  2. Requirements
  3. Quickstart
  4. Commands
  5. Connect without the CLI
  6. Security
  7. Development
  8. License

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:

ClientInstallation method
CursorMerges odiseo into ~/.cursor/mcp.json
CodexReplaces only [mcp_servers.odiseo] in ~/.codex/config.toml
Claude CodeRuns claude mcp add in user scope
OpenClawRuns 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

Frequently asked questions

What is Odiseo?

SEO layer for agents: research, content, QA, approvals and publishing via MCP OAuth.

How do I install Odiseo?

It runs as a remote server. In Claude Code: claude mcp add --transport http odiseo 'https://www.odiseo.help/api/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Odiseo need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Odiseo open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains Odiseo?

It is published by odiseohelp-app. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.