Skip to main content

Documentation Index

Fetch the complete documentation index at: https://crevio.co/docs/llms.txt

Use this file to discover all available pages before exploring further.

The Crevio MCP server uses Streamable HTTP transport — a single endpoint that accepts JSON-RPC requests and returns JSON-RPC responses (optionally streaming over Server-Sent Events). Any MCP-compatible client that supports Streamable HTTP can connect.

Base URL

https://mcp.crevio.co/mcp
A single endpoint handles everything: clients POST JSON-RPC messages to it, and the server replies with a JSON response or an SSE stream. There is no separate connection or messages endpoint to manage.

Authentication

All MCP requests require a Bearer token in the Authorization header. Use the same API tokens from your Developer settings.
curl -X POST https://mcp.crevio.co/mcp \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
MCP tokens have the same permissions as API tokens. Only share them with trusted AI tools and agents.

Connecting to Claude Desktop

Add this to your Claude Desktop configuration file (claude_desktop_config.json):
{
  "mcpServers": {
    "crevio": {
      "url": "https://mcp.crevio.co/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_TOKEN"
      }
    }
  }
}
After restarting Claude Desktop, you can ask Claude to manage your store in plain English:
“List all my products and their prices” “Create a 20% discount code called SUMMER20 that expires next month” “Who are my top 5 customers by order count?”

Connecting to Cursor

In Cursor, go to Settings > MCP Servers and add a new server:
  • Name: Crevio
  • Type: Streamable HTTP
  • URL: https://mcp.crevio.co/mcp
  • Headers: Authorization: Bearer YOUR_API_TOKEN

Other MCP clients

Any MCP-compatible client that supports Streamable HTTP transport can connect. The server implements the standard MCP specification with JSON-RPC over HTTP.
Once connected, see the Overview for how the two tools (code_search and code_execute) work and what the API exposes.