Connect an agent over MCP

OpenSEO includes an MCP server. Every feature in the app is available to Claude, Cursor, Codex and other agents that can connect to an MCP server over HTTP.

1. Create an API key

Create an API key in the OpenSEO app settings. Keys start with oseo_. Treat a key like a password: anyone who has it can run actions that are billed to your YepAPI key.

2. Find your endpoint

The MCP endpoint is {API_URL}/mcp, where {API_URL} is the base URL of your OpenSEO API. On a self-hosted install with default settings that is http://localhost:4100, so the endpoint is http://localhost:4100/mcp.

Every request must carry your key as a Bearer token:

Authorization: Bearer oseo_your_key

3. Add it to your client

Most MCP clients accept a JSON config like this one. Replace {API_URL} and the key with your own values.

{
  "mcpServers": {
    "openseo": {
      "type": "http",
      "url": "{API_URL}/mcp",
      "headers": {
        "Authorization": "Bearer oseo_your_key"
      }
    }
  }
}

The file this goes in, and the exact field names, vary by client. Check your client's documentation for remote HTTP servers with custom headers.

Claude Code

With Claude Code you can add the server from the command line:

claude mcp add --transport http openseo {API_URL}/mcp \
  --header "Authorization: Bearer oseo_your_key"

What agent actions cost

OpenSEO does not charge for MCP or API access. When an agent runs an action that fetches data, YepAPI bills your key for it, the same as when you run it yourself. An agent can run many actions quickly, so keep an eye on your YepAPI balance. See example prices.

What an agent can do

The server offers 60 tools, listed with their prices in MCP tools. Tools that spend take dry_run and max_cost_usd, and background runs require a ceiling. For worked examples, see Work with an AI agent.

REST API

The same key works with the REST API, for scripts and your own tools. Send it in the same Authorization header.