Generate a personal access token in your Trulit user settings, then add a small JSON block to your client (for Cursor it is ~/.cursor/mcp.json, for Claude Desktop it is claude_desktop_config.json). The bridge runs via npx, so there is nothing to install globally.

No. The MCP server is included on every Trulit plan. You only pay for the underlying actions your agent performs (test runs, AI generations) at the same metered rates as the UI.

Can my agent run real test executions?

Yes. Through the bridge an agent can queue automation runs against any project it has access to, then stream back status, screenshots and logs as the run progresses.

Where does my data go?

Only your agent and the Trulit API see your data. The bridge is a thin local proxy. We never proxy through third parties and never use your workspace content to train models.

MCP · stdio transport

Connect any agent to your Trulit workspace

One personal access token plugs Cursor, Claude Desktop, Claude Code or any MCP client straight into Trulit. Generate test cases, run automations and triage defects from your editor's chat.

Start free Book a demo

6+MCP clients

0global installs

SHA-256hashed tokens

Trulitworkspace

CuCursor

ClClaude Desktop

CcClaude Code

CoContinue

ClCline

CxCodex CLI

SUPPORTED CLIENTS →

CuCursorClClaude DesktopCcClaude CodeCoContinueClClineCxCodex CLI

Capabilities

Everything your agent needs, nothing it doesn't

The bridge exposes your real workspace over a standard protocol: secured, scoped and fully auditable. Ask in plain language; it runs as real workspace calls.

trulit.list_projects()trulit.generate_suite()trulit.run_automation()

cursor: trulit mcp● connected

Works with every MCP client

Cursor, Claude Desktop, Claude Code, Continue, Cline and Codex CLI all connect through the same standard MCP bridge.

Secure personal access tokens

Tokens are SHA-256 hashed at rest, scoped to your user, inherit project access via RLS and can be revoked in one click.

Real workspace actions

Read projects and suites, draft AI test cases, trigger automation runs and stream back logs, screenshots and run status.

Zero-install bridge

Runs via npx: no global install, no daemon. Add a JSON block to your client config and you are connected.

Install

Three steps to a connected agent

Generate a token, paste one config block, restart your agent. That's the whole setup.

Generate a token

In Trulit, open User settings → MCP & API tokens, then New token. Copy it once and store it safely.

Add the server to your agent

Paste the snippet into your client config and swap in your personal access token.

Restart and chat

Fully restart the agent, then ask it to list projects, generate a suite or run an automation.

~/.cursor/mcp.jsonclaude_desktop_config.jsonagent chat

Architecture

Why an MCP bridge beats one-off plugins

Most test tools ship a bespoke plugin per editor and lag months behind new AI clients. Trulit speaks the protocol.

Capability

One-off plugins

Trulit bridge

New AI client support

months of lag

same day

Integrations to maintain

one per editor

just one

Auth & config

different each tool

one token, one block

Install footprint

plugin + updates

npx, zero install

Reference

Frequently asked questions

Q1What is the Trulit MCP server?

It is a Model Context Protocol bridge that lets any MCP-compatible AI agent (Cursor, Claude Desktop, Claude Code, Codex and others) read and write inside your Trulit workspace using a personal access token. Your agent can list projects, draft test cases, trigger runs and inspect defects without leaving its chat.

Q2Which AI tools work with it today?

Anything that speaks MCP. We test against Cursor, Claude Desktop, Claude Code, Continue, Cline and Codex CLI. New MCP clients work out of the box because the bridge implements the standard stdio transport.

Q3How do I install it?

Generate a personal access token in your Trulit user settings, then add a small JSON block to your client (for Cursor it's ~/.cursor/mcp.json, for Claude Desktop it's claude_desktop_config.json). The bridge runs via npx, so there is nothing to install globally.

Q4Is it secure?

Tokens are SHA-256 hashed at rest, scoped to your user identity, inherit your project access via row-level security and can be revoked at any time. All traffic goes over HTTPS to the Trulit edge function and is fully auditable.

Q5Does it cost extra?

The MCP bridge is included with every Trulit plan. Usage counts against your existing workspace limits, so there's no separate integration fee to connect your agents.

Connect your first agent today

Spin up a token, paste one config block and let your agent run inside Trulit. Free to start, no card required.

Start free Book a demo