Quickstart

Four steps from zero to a working call.

1. Get an API key

Every request needs an x-api-key header. Keys are issued by EDITED — contact your account manager or customer success representative, or email support@edited.com. Details in Authentication & access.

Already have a key? Carry on.

2. Verify the handshake

initialize is the standard MCP opening call — and the quickest check that your key works:

curl -s https://mcp.edited.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "MCP-Protocol-Version: 2025-06-18" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{ "jsonrpc": "2.0", "id": 1, "method": "initialize",
        "params": { "protocolVersion": "2025-06-18", "capabilities": {},
                    "clientInfo": { "name": "curl", "version": "0" } } }'

Mind the URL: /mcp with no trailing slash — /mcp/ gets a 307 redirect instead of an answer (see Concepts → Transports).

A JSON-RPC body back means you're in. A 401 means the key is missing or not yet enabled for MCP — see Errors. The server is stateless, so there's no session to track between calls; see Concepts → Transports for the full flow.

3. Call your first tool

Resolve a fuzzy brand query into stable identifiers:

curl -s https://mcp.edited.com/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "MCP-Protocol-Version: 2025-06-18" \
  -H "x-api-key: YOUR_API_KEY" \
  -d '{ "jsonrpc": "2.0", "id": 2, "method": "tools/call",
        "params": { "name": "mdmcp-search_brands",
                    "arguments": { "query": "Nike", "search_limit": 3 } } }'

The result is a list of brand matches, each with a stable slug you can feed into downstream queries. Every tool, with its schema and a live "Try it" widget, is in the Reference.

Prefer a UI? The official MCP Inspector gives you an interactive explorer (add your x-api-key in its Headers panel):

npx @modelcontextprotocol/inspector \
  --transport http \
  --url "https://mcp.edited.com/mcp"

4. Connect your client

curl proves the plumbing; agents are the point. Wire EDITED MCP into:

Client	Recipe
Claude Desktop	Connect Claude Desktop
Claude Code	Connect Claude Code
Your own agent (TS / Python)	Connect a custom client
Just your browser	Using the Reference

Then see Recipes → Example workflow for an end-to-end agentic flow — a natural-language question in, structured EDITED data back.