Skip to main content
The server has an MCP endpoint at /mcp. Connected to it, Claude can read the workspace and make the same decisions the dashboard offers, from Claude Code while you work on the code or from the Claude app. Settings › MCP shows this server’s MCP address and the command to add it, ready to copy.

​
Add it to Claude Code

Then run /mcp inside Claude Code, choose truecourse and authenticate. Your browser opens the sign-in page; sign in and pick the workspace. One connection is one workspace.

​
Add it to the Claude app

In the Claude app, open Settings › Connectors, choose Add custom connector, and give it the same address. Claude signs in the same way, and the connector is then available in the Claude app on the web and desktop, and in Claude Code. On a Claude Team or Enterprise plan, an admin may need to add it for the organization. This needs a server Claude can reach over the internet, so it does not work with a local server.

​
Local mode

A local server has no sign-in. Add it with its local address and it connects straight to the local workspace:

​
What Claude can do

Read
  • The workspace’s repositories, documents and sources, and whether the corpus is stale
  • One document, or one section of it
  • Open conflicts, with both sides
  • Flows, filtered by status, and one flow with its milestones and tests
  • Runs, one run’s results filtered by outcome, and each failure with its evidence
  • What is blocked, and on which dependency
  • Claim coverage
  • Which dependency values are filled in. Values themselves are never returned.
Decide
  • Resolve a conflict, or undo a resolution
  • Force-include or force-exclude a document, or undo either
  • Dismiss a flow, or restore it
  • Restore a dismissed claim
  • Enter a dependency’s connection values
  • Add, edit, pause, sync and delete sources
Every decision goes through the same code as the dashboard, with the same effects. Resolving the last open conflict of a repository whose Flow generation stopped on it starts that generation again, exactly as it does from the dashboard. Claude cannot start a document scan, Flow setup, Flow generation or Flow run, and cannot change members, repositories, models or credits.

​
Setting up the server

A local server needs nothing. A server with sign-in needs two environment variables, set together: In the WorkOS dashboard, under Connect › Configuration:
  1. Enable MCP Auth, with both Client ID Metadata Document and Dynamic Client Registration.
  2. Add the TRUECOURSE_MCP_URL address as an MCP resource indicator.
Without the two variables, /mcp answers that its sign-in is not configured, and Settings › MCP says the same. See Self-hosting.