Odiseo

help.odiseoPublished by odiseo.helpOfficial publisherv0.1.0Updated Nov 2, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Odiseo is a remote SEO MCP server that lets an assistant research sites, plan and write content, run QA and approvals, and publish within an authorized…

What you can do
  • Research a site and gather SEO inputs for planning
  • Build briefs and content plans
  • Create and review articles
  • Operate the publication workflow, including approval and publishing steps
  • Verify the connection and credential through the CLI doctor command
When to use it
Use it when an assistant should help with SEO work end to end inside an Odiseo organization: site research, content briefs and articles, review, and publishing. It suits teams that already have Odiseo MCP access and want the agent to work inside their existing approval flow.
Requirements
A remote Streamable HTTP endpoint at odiseo.help/api/mcp, reachable over the network. An Odiseo account whose organization has MCP access, and OAuth (device flow or native MCP OAuth discovery) or an Odiseo MCP API key. The optional CLI needs Node.js 20 or newer and a supported client: Codex, Claude Code, Cursor, or OpenClaw.
Before you install
OAuth and device credentials grant access to the whole authorized organization, so prefer a site-scoped API key when a narrower long-lived credential is better. Publishing and approval tools are high-impact actions and should only run on explicit user instruction. The CLI stores the session in a config file and writes the bearer credential into the client's MCP configuration; revoke and log in again if a credential is exposed.

Installation

In SourceWeft

  1. Open Odiseo in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/help.odiseo%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "odiseo": {
      "type": "http",
      "url": "https://www.odiseo.help/api/mcp"
    }
  }
}

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:

bash
npx odiseo-cli login

Then install Odiseo in your client:

bash
npx odiseo-cli mcp install cursor

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

bash
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:

bash
odiseo loginodiseo login --no-open

For local development:

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

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

bash
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:

bash
odiseo mcp install codexodiseo mcp install claudeodiseo mcp install cursorodiseo mcp install openclaw

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

bash
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:

bash
odiseo mcp doctorodiseo 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:

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

For example:

bash
codex mcp add odiseo --url https://odiseo.help/api/mcpcodex 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

bash
npm installnpm run typechecknpm test

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

License

MIT

Source: README.md at commit dbe2ffd

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 25, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts