MCP Server

Streamable-HTTP MCP server exposing Inqud's OpenAPI spec and public docs as tools for AI agents. Public, no auth.

The Inqud MCP server exposes our public OpenAPI spec and documentation as tools that any MCP-compatible AI client can call. Once connected, your AI assistant can search endpoints, inline schemas, and fetch docs pages on demand — without leaving your editor.

• Endpoint: https://mcp.inqud.com/v1/mcp

• Transport: Streamable HTTP (JSON-RPC over HTTP POST)

• Auth: none

Setup

Claude Code

One-line install:

claude mcp add --transport http inqud https://mcp.inqud.com/v1/mcp

Or add manually to ~/.claude.json (user scope) or .mcp.json (project scope):

{
  "mcpServers": {
    "inqud": {
      "type": "http",
      "url": "https://mcp.inqud.com/v1/mcp"
    }
  }
}

Verify with /mcp inside Claude Code — inqud should be listed as connected.

Cursor

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (per-project):

{
  "mcpServers": {
    "inqud": {
      "url": "https://mcp.inqud.com/v1/mcp"
    }
  }
}

Restart Cursor. Open Cursor Settings → Tools & MCPs → User MCP Servers (Cmd+Shift+J) to confirm the server is green and lists 5 tools.

Codex CLI

Add to ~/.codex/config.toml:

[mcp_servers.inqud]
url = "https://mcp.inqud.com/v1/mcp"

Codex auto-detects the Streamable HTTP transport from the url field. Run codex and type /mcp to verify the server is listed.

If your Codex version fails to initialize the HTTP server (see openai/codex#11284), fall back to the mcp-remote stdio bridge:

[mcp_servers.inqud]
command = "npx"
args = ["-y", "mcp-remote", "https://mcp.inqud.com/v1/mcp"]

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json (on Windows: %USERPROFILE%\.codeium\windsurf\mcp_config.json):

{
  "mcpServers": {
    "inqud": {
      "serverUrl": "https://mcp.inqud.com/v1/mcp"
    }
  }
}

Open the Cascade panel → MCPs icon (or Windsurf Settings → Cascade → MCP Servers) and click Refresh. The inqud entry should appear with 5 tools.

Other clients

Any MCP client that only supports stdio can use the mcp-remote bridge:

npx -y mcp-remote https://mcp.inqud.com/v1/mcp

Wire that command into your client's MCP config as a stdio server. This works for Cline, Continue, Zed, and others.

For raw HTTP debugging:

curl -s -X POST https://mcp.inqud.com/v1/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'

Available tools

Tool	What it does
lookup_list_endpoints	List every endpoint in the public API (method, path, summary, tag).
lookup_search_endpoints	Ranked search over endpoints by keyword.
lookup_get_endpoint	Full operation detail for a given method + path, with all $ref s inlined.
lookup_search_docs	Search docs.inqud.com.
lookup_get_doc_page	Fetch the full markdown of a docs page by URL.

Try it

Once connected, prompt your agent like this:

• "How do I verify the signature on Inqud webhooks? Show me a code example."

• "What's the request body for creating a crypto-acquiring checkout? Show me the schema with all required fields."

• "Show me how to create an on-ramp checkout via the API — request shape and response."

• "How do I set up webhooks to track mass payout batch and individual payment status updates?"

• "Walk me through the crypto recurring flow from creating a plan to an active subscription, and show me the endpoint to create a plan."

The agent will pick the right tool (lookup_search_endpoints, lookup_get_endpoint, lookup_search_docs, lookup_get_doc_page) automatically.