Stream MCP Server

MCP (Model Context Protocol) is a standard way for AI clients to call tools and read resources from external systems.

The Stream MCP Server exposes Stream operations (payments, invoices, customers, products, etc.) as MCP tools so clients like Claude Desktop, Cursor, and VS Code can use them directly.

Resources vs tools: MCP resources (such as the OpenAPI documentation) do not require a Stream API key. Tools that call the Stream API—payments, customers, invoices, products, coupons, and the rest, do require a valid key in your client configuration.

Main Feature: API Documentation Integration​

The primary feature of this MCP server is direct integration with Stream API documentation.

• It exposes the full OpenAPI spec as an MCP resource.
• AI clients can read the latest API schema and stay aligned with current endpoints.
• This improves tool accuracy for request fields, validation, and endpoint usage.

Hosted endpoint​

Stream hosts the MCP server at:

https://mcp.streampay.sa/mcp

Configure your client to use this URL. Include Authorization when you use tools that hit the Stream API; you can omit it if you only read documentation resources.

Client configuration (Claude Desktop / Cursor / VS Code)​

Add this to your MCP config file (claude_desktop_config.json or mcp.json). Use the headers block whenever you rely on tools that require the Stream API (omit it for resources-only use, such as the OpenAPI spec).

{
  "mcpServers": {
    "stream": {
      "url": "https://mcp.streampay.sa/mcp",
      "headers": {
        // Required for operational tools (payments, customers, etc.); omit if you only read docs resources (e.g. OpenAPI).
        "Authorization": "Bearer sk_live_your_key_here"
      }
    }
  }
}

Available Tools​

Payment Links​

Customers​

Products​

Coupons​

Invoices​

Payments​

Resources​

Reading these resources does not require your Stream API key in the client (unlike the operational tools above).