Skip to main content
MCP servers are how your agent reaches real systems: SaaS apps, internal APIs, data platforms, ticketing tools, and infrastructure controls. Register them once under Settings → Connectors. Agents attach servers by name. Credentials live in the connector configuration, never in agent definitions.

​
Connecting a server

Open Settings → Connectors, pick a server from the catalog, complete auth if required, and save. The server is then available when you create an agent.
The Settings → Connectors page showing a connected server above a catalog of MCP servers labelled by auth type

Settings → Connectors — connect a server from the catalog (each shows its auth type).

You can also use Add MCP Server to register any remote URL that is not in the catalog.
The catalog entries under Settings → Connectors (Linear, Notion, GitHub, and others) come from the shipped MCP catalog — see Initial Setup for how catalogs work and how to change what the UI offers.

​
Authentication options

  • No auth — public or network-trusted servers.
  • Header auth — static HTTP headers (API keys, bearer tokens) sent on every request.
  • OAuth (Dynamic Client Registration) — TrueForge registers as an OAuth client, runs the authorization-code flow, and stores and refreshes tokens. Users never paste tokens into the agent.
For OAuth to work, the MCP server must redirect the user back to your TrueForge instance — so the server needs to know its own public address. That is the PUBLIC_BASE_URL environment variable. It defaults to http://localhost:<port>, which is fine on your own machine; set it whenever TrueForge is reached at a different address (a domain, reverse proxy, or another host). Where to set it depends on how you run TrueForge — as an env var for npx, in packages/trueforge/.env for Docker Compose, or server.publicBaseUrl for Helm. See the Quickstart FAQ.

​
In-chat authentication

If a server uses OAuth and the user has not yet authorized it, the turn pauses and the chat UI shows a Connect button. The user completes OAuth in a popup and continues the conversation — the agent does not fail.
The chat UI showing an MCP Authentication Required panel for the linear server, with Connect and Continue buttons

In-chat MCP authentication: the turn pauses with a Connect button until the user authorizes the server, then continues.

​
Next steps