MCP gateway you deploy: a Tracekit signer decides and signs each call; agents send each run's token.
Connect Remote server
claude mcp add --transport http tracekit-mcp-gateway https://{tracekit_gateway}/mcp --header "X-Tracekit-Run: <X_TRACEKIT_RUN>" --header "Authorization: Bearer <YOUR_API_KEY>"
{
"mcpServers": {
"tracekit-mcp-gateway": {
"url": "https://{tracekit_gateway}/mcp",
"headers": {
"X-Tracekit-Run": "<X_TRACEKIT_RUN>",
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
{
"servers": {
"tracekit-mcp-gateway": {
"type": "http",
"url": "https://{tracekit_gateway}/mcp",
"headers": {
"X-Tracekit-Run": "<X_TRACEKIT_RUN>",
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://{tracekit_gateway}/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools
The tool list was not available in our last check.
Headers
| Name | Description |
|---|---|
X-Tracekit-RunRequired, secret | <run_id>.<run_token> of the agent's run (register_run): new for every run, so the agent framework sets it per run; one typed in once works for one run |
AuthorizationOptional, secret | Bearer <token>: the agent's identity, when the gateway's http.authenticators accept a bearer or Kubernetes service account token (else a client certificate) |
Details
| Endpoint | https://{tracekit_gateway}/mcp (Streamable HTTP) |
| First published | 10 Nov 2026 |
| Last updated | 10 Nov 2026 |
| Registry name | io.github.Cygnux-Labs/tracekit-mcp-gateway |
More cloud and devops servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
