Protocols

Connect over MCP.

The agent-native way in: your client discovers the tools and calls them as part of its own reasoning.

Claude Desktop & Claude Code

Add the server to your MCP config, replace YOUR_BUYARY_KEY with a key from your dashboard, and restart the client.

claude_desktop_config.json
{
  "mcpServers": {
    "buyary": {
      "type": "http",
      "url": "https://services.buyary.com/mcp/",
      "headers": {
        "Authorization": "Bearer YOUR_BUYARY_KEY"
      }
    }
  }
}

Or, in Claude Code, one line:

terminal
claude mcp add --transport http buyary https://services.buyary.com/mcp/ --header "Authorization: Bearer YOUR_BUYARY_KEY"

Any other MCP client

Buyary speaks the remote HTTP transport, so any MCP client can connect with two facts:

connection
URL:    https://services.buyary.com/mcp/\nHeader: Authorization: Bearer YOUR_BUYARY_KEY

Use the canonical endpoint with its trailing slash, /mcp/. Today the no-slash form can redirect in a way that drops the Authorization header on some clients, so configure /mcp/ directly while that routing behavior is being resolved.

What your agent discovers

Two tools: get_product_intelligence for a single product and get_product_intelligence_batch for up to five at once. Your agent calls them on its own when a buying question needs product data.

Prefer plain HTTP? The REST API is the same service →