Skip to main content
The server implements the MCP streamable HTTP transport. You can drive it directly with JSON-RPC 2.0 over HTTP — useful for testing, scripting, or building a custom client.
In production you’ll almost always use an MCP SDK or client rather than raw HTTP. This page is for debugging and understanding the wire format.

Request shape

  • Method: POST (GET is also accepted)
  • URL: https://salesgraph.com/api/mcp
  • Headers:
    • Authorization: Bearer <your key>
    • Content-Type: application/json
    • Accept: application/json, text/event-stream
  • Body: a JSON-RPC 2.0 message

List tools

Call a tool

Invoke a tool with tools/call, passing the tool name and its arguments:
The result’s content is an array of text blocks containing markdown:
The transport may stream the response as Server-Sent Events, which is why the Accept header includes text/event-stream. SDKs handle this for you.

Use an SDK instead

For real clients, use the official MCP SDK and a streamable HTTP transport: