§ docs / the discovery layer for agent commerce

Client setup

Every MCP-compatible client can reach Nitrograph at:

https://api.nitrograph.com/mcp

Transport is streamable HTTP, stateless. No API key. Free tier is IP-rate-limited; pay-to-continue is advertised in 402 responses when you run out of quota.

Support matrix

This page is the single source of truth for what works where. If copy elsewhere (CLI wizard, marketing, tool descriptions) disagrees, this table wins.

| Client | Preferred path | Auto-install via npx nitrograph | Notes | | --------------- | ------------------------- | :-------------------------------: | ------------------------------------------------------------ | | Claude Code | Nitrograph plugin | ✓ | Preferred path includes MCP, skill, and /discover. | | Claude Desktop | Custom Connector on claude.ai | ✓ (stdio fallback) | Doesn't take remote HTTP in local JSON yet — connector syncs down. | | Cursor | ~/.cursor/mcp.json | ✓ | Native streamable HTTP. | | Windsurf | ~/.codeium/windsurf/mcp_config.json | ✓ | Uses serverUrl, not url. | | Cline (VS Code) | VS Code settings.json | — | Manual config only; no filesystem marker for auto-detect. | | Zed | ~/.config/zed/settings.json via mcp-remote | — | Zed doesn't speak HTTP MCP; bridge through stdio. | | Hermes | ~/.hermes/config.yaml | — | Native streamable HTTP. |

The "Auto-install" column reflects what npx nitrograph detects on disk and writes to. Anything marked — is a fully supported client — it just doesn't have a stable filesystem fingerprint for us to detect, so you paste the config block below.

Below is the exact config per client. Restart the client after editing its config file.

Claude Code

Preferred plugin install:

/plugin marketplace add nitrographtech/claude-plugins
/plugin install nitrograph@nitrograph

This installs the MCP server, the Nitrograph skill instructions, and a /discover command. If you only want the MCP server, add it manually:

claude mcp add --transport http nitrograph https://api.nitrograph.com/mcp

Store it globally with --scope user; without it the server is added only to the current project's ~/.claude.json entry.

Codex

Install the Codex plugin marketplace entry from the nitrograph npm repo:

codex plugin marketplace add nitrographtech/cli --sparse .agents/plugins
codex plugin marketplace upgrade nitrograph-plugins

Restart Codex, open the plugin directory, select Nitrograph Plugins, and install Nitrograph. The plugin provides the Nitrograph skill and MCP wiring so Codex knows to discover, inspect, then call services directly.

Claude Desktop

Claude Desktop doesn't take remote HTTP servers in its local JSON config yet. Add Nitrograph as a Custom Connector on claude.ai instead; it syncs into the desktop app automatically.

Cursor

~/.cursor/mcp.json (or .cursor/mcp.json inside a workspace):

{
  "mcpServers": {
    "nitrograph": {
      "type": "streamableHttp",
      "url": "https://api.nitrograph.com/mcp"
    }
  }
}

Windsurf

~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "nitrograph": {
      "serverUrl": "https://api.nitrograph.com/mcp"
    }
  }
}

Windsurf uses serverUrl, not url.

Cline (VS Code)

VS Code settings JSON:

{
  "cline.mcpServers": {
    "nitrograph": {
      "type": "streamableHttp",
      "url": "https://api.nitrograph.com/mcp"
    }
  }
}

Zed

Zed doesn't speak HTTP MCP natively. Bridge through mcp-remote in ~/.config/zed/settings.json:

{
  "context_servers": {
    "nitrograph": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://api.nitrograph.com/mcp"]
    }
  }
}

Hermes

~/.hermes/config.yaml:

mcp_servers:
  nitrograph:
    url: https://api.nitrograph.com/mcp

Verifying the connection

Once registered, your client should list four tools:

Ask your agent to run nitrograph_discover with any query. It should return a ranked, pre-formatted list. If you see 402 or a payment challenge, that means you've exhausted the free tier.