MCP HTTP Transport

By default, the TradeStaq MCP server uses stdio transport (standard input/output). For remote access or multi-client setups, you can use HTTP transport instead.

Remote Server

TradeStaq hosts a public MCP server at:

https://mcp.tradestaq.com/mcp

This is always running the latest version. No installation required — just point your AI client to the URL.

Connecting to the Remote Server

Claude Desktop:

{
  "mcpServers": {
    "tradestaq": {
      "url": "https://mcp.tradestaq.com/mcp"
    }
  }
}

Claude Code:

claude mcp add --transport http tradestaq https://mcp.tradestaq.com/mcp

Remote Server Details

Self-Hosting with --http Flag

You can run the MCP server locally in HTTP mode for development, testing, or internal use:

npx @the-staq/tradestaq-mcp --http

This starts an HTTP server on the default port.

Port Configuration

Custom port example:

npx @the-staq/tradestaq-mcp --http --port 8080

Then connect your AI client to http://localhost:8080/mcp.

Self-Hosted Configuration

Claude Desktop (local HTTP):

{
  "mcpServers": {
    "tradestaq": {
      "url": "http://localhost:3100/mcp"
    }
  }
}

Health Endpoint

Both the remote server and self-hosted instances expose a health check:

curl https://mcp.tradestaq.com/health
# or
curl http://localhost:3100/health

Response:

{
  "status": "ok",
  "version": "1.0.0",
  "uptime": 86400
}

Use this endpoint for monitoring, load balancer health checks, or verifying the server is running.

When to Use HTTP vs stdio

Next Steps

• Setup Guide — Full setup instructions for all clients
• Authentication — How auth works over HTTP
• Troubleshooting — Connection issues and fixes