NV oOS Gateway

Fleet-scoped MCP server for NV oOS WordPress sites — one API key, every bound site; tools namespaced as <site-slug>.<tool> over streamable HTTP.

View on nvoos.pro

Hosted MCP Server

npx add-mcp 'https://mcp.nvoos.pro/mcp'

Installs into Claude Code, Codex, Cursor and more

Documentation

NV oOS MCP Gateway icon

A public, fleet-scoped Model Context Protocol endpoint for the NV oOS (Open Operator System) WordPress platform. One key, every bound site: tools appear namespaced as <site-slug>.<tool>.

Endpoint

POST /mcp   (JSON-RPC 2.0 · streamable HTTP · MCP 2026-07-28)
GET  /mcp   (server discovery JSON)

Authentication

Every request requires a public API key: Authorization: Bearer <your-key>. Keys are issued by the operator of this gateway and map to a set of sites; tool scoping is enforced server-side by each site's Fleet Operator allowlist.

Example (Claude Desktop)

{
      "mcpServers": {
        "nvoos": {
          "type": "http",
          "url": "https://mcp.nvoos.pro/mcp",
          "headers": { "Authorization": "Bearer YOUR_KEY" }
        }
      }
    }

Example (Claude Code)

claude mcp add --transport http nvoos https://mcp.nvoos.pro/mcp --header "Authorization: Bearer YOUR_KEY"
    # or install the plugin: /plugin marketplace add nvdigitalsolutions/nvoos-mcp-gateway

For editors, the nvoos-mcp-bridge npm package provides a stdio relay:

npx -y @nvdigitalsolutions/nvoos-mcp-bridge
# env: MCP_AI_BASE_URL=https://mcp.nvoos.pro/mcp
# env: MCP_AI_TOKEN=<your-key>

Health

GET /health — public status (no auth required).