docs
Cloud plansOpen dashboard →

Connect your agent to Traceblox

Set up hosted MCP, confirm a real trace, and keep the instructions available to your agents.

Download the complete Markdown guide

Before connecting

  1. Create a workspace in the dashboard, then create a workspace API key. Copy its one-time secret into your private credential manager.
  2. Supply the key as SCHOLIA_CLOUD_API_KEY in the environment of the process that actually runs the client. Desktop apps do not necessarily inherit variables exported in a terminal.
  3. Use the full Streamable HTTP endpoint: https://mcp.traceblox.com/mcp. A browser GET is not a connection test.
  4. Merge configuration into existing files. Keep real keys out of project files, transcripts, and source control.

Claude Code

With Claude Code installed, paste this command into your terminal. Sign in to Traceblox in the browser and approve the connection. No API key is needed. The login command requires Claude Code 2.1.186 or later; older versions can authenticate from /mcp.

Terminal · add and sign in
claude mcp add --transport http --scope user traceblox 'https://mcp.traceblox.com/mcp?client=claude-code' &&
claude mcp login traceblox

Open /mcp in Claude Code and confirm Traceblox is connected. Grant this connection access to the intended projects in Traceblox Connections, then run the connection check below.

Official Claude Code reference

Codex

With Codex installed, paste this command into your terminal. Sign in to Traceblox in the browser and approve the connection, then start a new chat. No API key is needed. This adds the hosted MCP connection; a public Traceblox plugin directory listing is not yet verified.

Terminal · add and sign in
codex mcp add traceblox --url 'https://mcp.traceblox.com/mcp?client=codex' &&
codex mcp login traceblox

Check Traceblox in Codex MCP settings or /mcp. Grant this connection access to the intended projects in Traceblox Connections, then run the connection check below. A saved configuration alone does not prove tool access.

Official Codex reference

Cursor

Choose Install in Cursor, approve adding the server, then use Connect in Cursor MCP settings to sign in to Traceblox. No API key is needed. If the button cannot open Cursor, merge this configuration with your existing MCP servers.

Fallback configuration · .cursor/mcp.json
{
  "mcpServers": {
    "traceblox": {
      "url": "https://mcp.traceblox.com/mcp?client=cursor"
    }
  }
}

Confirm Traceblox and its tools in Cursor MCP settings. Grant this connection access to the intended projects in Traceblox Connections, then run the connection check below.

Official Cursor reference

ChatGPT

In ChatGPT web, open Settings → Security and login and enable Developer mode if available. Open Plugins, select the plus button, and add Traceblox with this MCP URL under Connection. Create the connection, sign in to Traceblox through OAuth, and review the discovered tools. Availability depends on your account and workspace policy.

Remote MCP URL · add a connection
https://mcp.traceblox.com/mcp?client=chatgpt

Supported; verify on first connect. Grant project access in Traceblox Connections, confirm tool discovery, and run the write/readback check below. Inline widget rendering requires a separate check in the actual chat.

Official ChatGPT reference

Claude chat / Desktop

In Claude web or Desktop, open Settings → Connectors (or Customize → Connectors) → Add custom connector and paste this URL. Complete OAuth, then enable the connector in the conversation. Team and Enterprise owners may need to add it for the organization first. Desktop chat uses this remote connection.

Remote MCP URL · add a custom connector
https://mcp.traceblox.com/mcp?client=claude

Supported; verify on first connect. Grant project access in Traceblox Connections, confirm tool discovery, and run the write/readback check below. A Claude Code plugin installation does not verify Claude chat or its inline widgets.

Official Claude chat / Desktop reference

Grok Bot

Open Settings → Plugins to review available connections. This brief helps your Bot check its supported setup. A Traceblox marketplace listing or direct custom-MCP installer has not been verified for Grok Bot; the Grok CLI is a separate client.

Setup brief · give this to your Bot
Connect this task to Traceblox using https://mcp.traceblox.com/mcp.
Read https://scholialang.com/agents/connect.md for the hosted setup and tool schemas.
Check which MCP or plugin connection method this Bot supports. Ask for the workspace token through a secure credential flow, never in chat.
After connection, list the tools, create a test trace, append an observation, and read it back. Report any unsupported connection step.

Confirm the connection exposes Traceblox tools to the Bot itself. Installing a CLI on its computer does not establish native Bot tool access. Do not claim success without a write and readback.

Official Grok Bot reference

Grok CLI

This configuration is for the CLI. It does not establish native Grok Bot integration.

Grok CLI
grok mcp add --transport http traceblox 'https://mcp.traceblox.com/mcp' \
  --header 'Authorization: Bearer ${SCHOLIA_CLOUD_API_KEY}'
grok mcp doctor traceblox
Official Grok CLI reference

Verify the first trace

Give your agent this check:

Use Traceblox for this project's explicit work records. Discover the hosted tools, list relevant DAGs, and create a test DAG if needed. Append an Observation describing this connection check, then read that atom back using its returned ID. Report the DAG ID, atom ID, and readback result. Do not include secrets or hidden reasoning.

Hosted tool schemas and the complete write/readback sequence

A saved configuration or successful local write does not establish hosted storage or cloud sync. Encrypted workspaces also require a client that implements the encryption protocol.

Run locally

Use the maintained local plugin installation guide for SQLite storage. Inspect the local server's tools and verify a local write and readback; hosted tool names differ.

Local Gemma atom drafting · Measure token and cost savings

If the connection fails