About Odiseo
Odiseo CLI connects supported coding clients to an authorized organization's SEO MCP service. It handles OAuth or API-key login, client configuration, and connection checks for research, content, review, and publishing workflows.
Key features
- 01OAuth device-flow and API-key login
- 02Install MCP settings in four clients
- 03Check credentials and endpoint connectivity
- 04Research sites and build content plans
- 05Create and review articles
Use cases
- 01Connect Cursor to an organization's SEO service
- 02Check MCP credentials before a work session
- 03Research a site and prepare article briefs
- 04Review content and manage publishing after approval
MCP support
Installs the Odiseo Streamable HTTP MCP server in Codex, Claude Code, Cursor, or OpenClaw, or clients can connect directly to its endpoint. The service exposes SEO research, content creation and review, and publishing workflow tools.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://www.odiseo.help/api/mcpclaude mcp add --transport http help-odiseo https://www.odiseo.help/api/mcp{"mcpServers":{"help-odiseo":{"type":"http","url":"https://www.odiseo.help/api/mcp"}}}Open in Cursor{"servers":{"help-odiseo":{"type":"http","url":"https://www.odiseo.help/api/mcp"}}}Open in VS Code{"mcpServers":{"help-odiseo":{"type":"http","url":"https://www.odiseo.help/api/mcp"}}}{"mcpServers":{"help-odiseo":{"serverUrl":"https://www.odiseo.help/api/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
Details
From the project READMEOdiseo 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
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.