Back to Browse

Cli MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

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

About

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

Remote endpoints: streamable-http: https://www.odiseo.help/api/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry.

Endpoint verified · Requires authentication · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

file_system

Applies to the server that hosts this plugin, not to your machine.

env_vars

Applies to the server that hosts this plugin, not to your machine.

Shell Command Execution

Runs commands on the server that hosts it, not on your machine.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "help-odiseo-mcp": {
      "url": "https://www.odiseo.help/api/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

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

Reviews

No reviews yet

Be the first to review this server!