Integrations

Repositories on any host or inside CodeBook, draft pull requests, tool connections, the MCP server, outside runtimes and adapters, worker SDKs, events, production monitoring, linked MadeBook and OpenBook workspaces, and the governance handoff.

• RepositoriesConnecting GitHub, GitLab or a self-hosted Gitea to a workflow, the System Map analysis and its limits on very large repositories, the push webhook CodeBook registers and repairs, creating a repository, and why opening pull requests is a per-station grant.
• Pull requestsDraft pull requests linked to the card that produced them, what agents are told about conflicts, who merges, and how a merge moves the card.
• Tool connectionsConnecting MCP servers so your workers have tools — the catalogue, the two switches between a tool and a run, and what cannot be connected yet.
• The MCP serverEvery workflow is also an MCP server, so outside agents can read cards, move them and trigger workers — the tools it offers, how tokens are scoped, and what a token can never do.
• External worker runtimesRun a station through MCP pull, signed webhooks, GitHub Actions, Devin, or a dedicated adapter for GitLab CI/CD, CircleCI, Buildkite, Cursor, Jules or Copilot.
• Command runnersRun your repository's own commands — tests, lint, build — on a machine you own, so agents can ask for them by name. The application server does not execute repository code.
• Dedicated runtime adaptersWork a station through GitLab CI/CD, CircleCI, Buildkite, Cursor, Jules or GitHub Copilot with the vendor's own API, a credential you create and explicit state mapping.
• Worker SDKsBuild an external CodeBook worker in TypeScript or Python with a workflow-scoped token.
• Events and outcome reportingConnect signed outbound events and inbound triggers to systems outside CodeBook.
• Production monitoringConnect Sentry, Datadog, PagerDuty, Opsgenie, Grafana / Alertmanager or a generic webhook to the System Map — the address and headers each source uses, how incidents are linked to runtimes, services and modules, the mapping table, deploy events, and where production incidents change what CodeBook does.
• Linked products — MadeBook and OpenBookLink a workspace to MadeBook and OpenBook, run work under MadeBook governance, receive stories and epics from OpenBook and report back, and see which parts of the lifecycle have run for real.
• The governance handoff to MadeBookIn a workspace linked to MadeBook, MadeBook holds the rules and the record and CodeBook enforces its answers — models asked before use, sessions ended, evidence reported, one audit trail and retention of run bodies.