Skip to main content

Required Headers

Important: The Accept header with text/event-stream is REQUIRED. Without it, you will receive a 406 Not Acceptable error.

With Token URL (Self-sufficient)

Required Headers:
  • Content-Type: application/json
  • Accept: application/json, text/event-stream
Optional Headers:
  • x-alloy-user-token: JWT token for user isolation
  • x-alloy-userid: Override user ID when needed
  • x-credential-id: Use specific credential for operations
  • x-redirect-uri: OAuth redirect URI for credential creation

With API Authentication

Requires standard API authentication headers.
Required Headers:
  • Content-Type: application/json
  • Accept: application/json, text/event-stream
  • Authorization: Bearer YOUR_API_KEY
  • x-alloy-userid: Your user ID
Optional Headers:
  • x-alloy-user-token: JWT token for user isolation
  • x-credential-id: Use specific credential for operations
  • x-redirect-uri: OAuth redirect URI for credential creation
  • x-mcp-server-id: Alternative way to specify server ID

Complete Examples

Example with Token URL

Example with API Authentication

Request Format

All MCP requests follow the JSON-RPC 2.0 specification:

Response Format

Successful responses:
Error responses:

Available Methods

tools/list

Lists all available tools for the server.

tools/call

Executes a specific tool.

resources/list

Lists available resources.

resources/read

Reads a specific resource.

prompts/list

Lists available prompts.

prompts/get

Gets a specific prompt.