# Install Traceblox in your agent client

Reviewed 2026-09-13. Hosted Streamable HTTP MCP setup for Codex, Claude Code, Cursor, ChatGPT and Claude chat. Chat connections are supported; verify on first connect.

## Before connecting
Create or join a Traceblox workspace. Add the connection for your app, sign in through its browser authorization flow, and grant project access in Traceblox Connections. Keep existing MCP entries when merging configuration. API keys are an optional alternative for unattended clients; use a separate key per app through its supported private credential flow.

Endpoint: https://mcp.traceblox.com/mcp. Local tools and hosted tools have different names; inspect tools/list.

## 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

```sh
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.

Cloud agents: Claude Code cloud sessions need their own remote MCP configuration and authorized credentials. A user-scoped desktop entry is not transferred to a cloud runner. Add the hosted URL in the cloud environment's supported MCP setup; repository configuration must not contain tokens.

Official reference: https://code.claude.com/docs/en/mcp

## 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

```sh
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.

Cloud agents: Codex cloud runs require a remote connection in that environment. Desktop MCP configuration does not prove cloud attachment. Do not copy setup-only secrets into repository files to keep them available after setup. Verify tools and a write/readback in the actual cloud run.

Official reference: https://developers.openai.com/codex/mcp

## 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

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

[Install in Cursor](cursor://anysphere.cursor-deeplink/mcp/install?name=traceblox&config=eyJ1cmwiOiJodHRwczovL21jcC50cmFjZWJsb3guY29tL21jcD9jbGllbnQ9Y3Vyc29yIn0%3D)

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.

Cloud agents: In Cursor cloud agents, open the MCP dropdown at cursor.com/agents and add this remote server separately. Team servers are managed under Dashboard → Integrations & MCP. Complete OAuth for your own account. The desktop install button does not configure cloud agents.

Official reference: https://cursor.com/docs/mcp

## 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

```text
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.

Cloud agents: This is a hosted chat connection; no local plugin or VM helper is needed. Availability depends on your ChatGPT plan and workspace permissions.

Official reference: https://developers.openai.com/plugins/deploy/connect-chatgpt

## 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

```text
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.

Cloud agents: Claude web and Desktop chat use the remote connector. No local Python plugin or VM helper is needed.

Official reference: https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp

## 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

```text
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 reference: https://docs.x.ai/grok-bot/computer-and-apps

## Grok CLI (separate from Grok Bot)

If you are using the Grok CLI, set SCHOLIA_CLOUD_API_KEY in the actual client environment and register the endpoint:

```sh
grok mcp add --transport http traceblox 'https://mcp.traceblox.com/mcp' \
  --header 'Authorization: Bearer ${SCHOLIA_CLOUD_API_KEY}'
grok mcp doctor traceblox
```

Reference: https://docs.x.ai/build/features/mcp-servers

## Verify a real trace

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 tools and verification steps: https://traceblox.com/agents/connect.md

## Local installation

For local SQLite storage, follow the maintained plugin installation guide: https://github.com/dougfirlabs/scholialang-mcp. Discover the installed local tools and verify a local write and readback. Local storage does not imply hosted sync.

## Troubleshooting

- Unauthorized: reconnect through your app’s sign-in flow. API-key clients should check their private credential configuration. Never print a token for diagnosis.
- Connected but no projects: grant the connection project access in Traceblox Connections.
- Existing traceblox entry: inspect its URL and credential mode first. Edit the existing entry instead of adding a duplicate; remove an obsolete bearer header before switching to OAuth.
- Entry saved but tools missing: reconnect or restart the client and inspect its MCP status and tool list.
- Existing configuration: merge the traceblox entry; do not replace other servers.
- Encrypted workspace: use a compatible encryption-capable client; a generic HTTP config alone does not implement the encryption protocol.
- No write receipt or failed readback: report the failure and keep the source event for retry. Configuration is not proof of recording.

Local Gemma atom drafting: https://traceblox.com/guides/local-gemma4.md
Cost measurement: https://traceblox.com/guides/measure-token-savings.md