Cyndra API

The Cyndra MCP server.

One URL, no credentials. Point Claude, ChatGPT or any MCP client at it and they can search Cyndra, read any page as markdown, and pull pricing, changelog and case studies.

MCP manifest OpenAPI spec

Connect

Add the server.

{
  "mcpServers": {
    "cyndra": {
      "type": "http",
      "url": "https://www.cyndra.ai/mcp"
    }
  }
}

Or from the CLI: npx @cyndra/cli mcp-config.

Transport: Streamable HTTP. Protocol revision 2025-06-18, with 2025-06-18, 2025-03-26, 2024-11-05 all accepted.
Stateless: no session id, so every request stands alone.
JSON-RPC batches are answered, even though the current revision drops them, because clients built against 2025-03-26 still send them.
A client whose Accept allows only text/event-stream gets its response framed as a single SSE event.

Tools

What the server exposes.

Tool	What it does
`search_cyndra_content`	Search every page Cyndra publishes (product, pricing, industries, departments, guides, comparisons) and return ranked hits with the markdown URL of each.
`get_cyndra_page`	Fetch the markdown body of one Cyndra page by its site-relative path, for example /pricing or /manual/first-day. Use search_cyndra_content or list_cyndra_pages to find valid paths.
`list_cyndra_pages`	List every indexed Cyndra page with its section and markdown URL. Optionally filter to one section such as industries, departments, manual or cookbook.
`get_cyndra_pricing`	Return Cyndra's pricing as structured data: the credit rate, what every plan includes, each tier's monthly price and credit allowance, and the top-up packs.
`get_cyndra_changelog`	Return Cyndra's product and platform releases, newest first, with each item tagged as a new feature, improvement or fix.
`list_cyndra_case_studies`	Return published client case studies with their industry, headline result and the URL of the full write-up in markdown.

Verify

Check the handshake yourself.

curl -s https://www.cyndra.ai/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize",
       "params":{"protocolVersion":"2025-06-18","capabilities":{},
                 "clientInfo":{"name":"probe","version":"1"}}}'

curl -s https://www.cyndra.ai/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/list"}'

FAQ

MCP questions.

What is the Cyndra MCP server URL?

https://www.cyndra.ai/mcp, using the Streamable HTTP transport. The manifest is at https://www.cyndra.ai/.well-known/mcp.json.

Does the Cyndra MCP server need authentication?

No. Every tool it exposes is read-only, so there is nothing to authorise. Add the URL and start calling tools.

Which MCP protocol versions does Cyndra support?

2025-06-18, 2025-03-26, 2024-11-05. The server echoes whichever revision your client opens with, so older clients connect without a version mismatch.

Which tools does the Cyndra MCP server expose?

search_cyndra_content, get_cyndra_page, list_cyndra_pages, get_cyndra_pricing, get_cyndra_changelog, list_cyndra_case_studies. All read-only.

Why does GET on the Cyndra MCP endpoint return 405?

The server opens no server-initiated SSE stream, and the Streamable HTTP transport specifies 405 for that case. POST your JSON-RPC messages to the same URL.