Skip to content
CodeBook

Tool connections

Connect MCP servers and supported REST APIs, enable selected tools and grant stations access.

An agent can always read its card and, with a repository connected, the code. Tool connections give workers access to services such as your CI system or issue tracker. CodeBook supports MCP servers and built-in REST API recipes.

This page is about tools your workers use. For the opposite direction — outside agents using your workflow — see The MCP server.

The catalogue

Open Tool connections → Browse in the workflow. There are 33 connectable entries, organized by category.

Category Examples
Code & docs Context7, DeepWiki, GitMCP, GitHub, Microsoft Learn, AWS Knowledge, Cloudflare Docs, Postman, Hugging Face
Testing & CI CircleCI, Buildkite, Semaphore, Cypress Cloud, Checkly, Currents, Sauce Labs, Datadog, Browserbase, TestRail (a REST recipe), and the CircleCI, Buildkite, Semaphore, Checkly and Currents APIs (REST recipes for test run pipelines)
Web & research Exa, Tavily, Firecrawl, Apify
Project tools Linear
Data & infrastructure Supabase, Neon
Payments Stripe
Customers Intercom

For a custom MCP server, supply its address and supported authentication. REST connections use the API recipes in the catalogue. Entries marked Needs OAuth sign-in cannot be connected in this panel.

Testing is a connection

The CodeBook application server does not execute repository code. Agents can ask a connected testing service — your CI system, a test platform or a cloud browser — or a command runner on a machine you own to run tests. Reading code alone is not a test run.

Connect that service from the Testing & CI category. One that is not in the catalogue can be added by its address; tick This connection runs tests on it.

Once a testing service is connected and its tools are switched on:

  • A Test station can be held to it. A station contract's rule Has a run from a connected testing service counts a test report only when its structured report names a run at one of these connections (or a CI runtime adapter), with its counts — see The Test station.

  • It reaches every station that works on pull requests. The second switch below does not apply to it: the testing service is offered at each station that works with the repository. The factory's policy and each agent's own permissions still apply.

  • Agents are told to use it. Before recording a pass on a pull request, the agent runs the tests there, or reads the run the service already started for the latest commit, waits for the result, and reports what ran and the outcome, naming the run. A failing run is a fail.

  • Missing test execution is explicit. With no testing service connected, agents are told about that limit. A verified proof run can still supply execution evidence from a person’s computer, a factory runner or a hosted sandbox. A review by reading the code is recorded separately. Repository reports and proof runs

What the service reports on the pull request itself — a check or a status — is what CodeBook reads before it merges: a failing check sends the card back to the developer.

How a server signs in

Choose a connectable entry and read its sign-in fields. Include only the credentials needed for its tools.

  • Open — answers anyone. One click.
  • API key — you paste a key or personal access token. Adding one connects immediately, so a key that does not work is a message at once, not a mystery in the middle of a run.
  • REST API entries use a built-in recipe for the vendor’s documented API. Connecting asks for your instance's address and the recipe's own fields (for TestRail, an email and an API key), which become one encrypted header; the fields are never kept. The recipe's tools then sit under the same switches, grants and permissions as any server's. See The Test station. A test run pipeline can use the CircleCI, Buildkite, Semaphore and Checkly API recipes to trigger and read work. Currents API supplies results. Test run pipelines

Two switches

Connecting a server enables nothing by itself. Two switches stand between a tool and a run:

  1. Every tool is off until you switch it on. A connected server lists the tools it offers; you turn on the ones you want. A server that offers thirty tools does not hand your agents thirty tools.
  2. For ordinary tools, allow the station to use connections. Under the station's Permissions, use tool connections is off by default.

Testing connections have the PR-station behavior described above. An engineer on Development can have live documentation while the analyst on Backlog has nothing, and a payments tool can be limited to the one finance station that needs it.

In the record

Every tool call an agent makes is a step in its run. Open the run under the station's Runs and the call is there, in order, with everything else the run did.

Tool output is data

Whatever a tool returns — a web page, a document, an issue — is read as information about the task, never as an instruction. Every skill CodeBook wrote says so, and the grants above hold whatever the content says. See The security model.