MCP servers
Plug an existing MCP tool server into the agent's toolbox.
A capability that already exists as an MCP server, a Jira bridge, an internal API gateway, doesn't need rebuilding as a custom tool. Register it; its tools join the agent's toolbox.
Add a server
- Open Extending → MCP Servers.
- Click Add MCP server.
- Enter Name, URL (SSE or HTTP), and optional Headers, one per
line, e.g.
Authorization: Bearer ${MCP_TOKEN}.
This writes utils/mcp.json in the project, the whole team and the
CLI in CI get the same server list:
{
"servers": {
"issue-tracker": {
"url": "https://mcp.example.com/sse",
"headers": { "Authorization": "Bearer ${TRACKER_TOKEN}" }
}
}
}${VAR} values resolve at run start, from the project's secrets first and the environment second, the token never
lands in the file.
Servers connect when a run starts. An unreachable server is retried once, then the run continues without it, with a warning in the log, an unavailable helper doesn't fail the suite, and the warning explains any missing tool.
Forge
Let the model draft the pieces of your project you would otherwise write by hand — UI prompts from screenshots, custom tools from a description, and soon tests from recordings.
Secrets
Keep credentials out of tests, stored encrypted on your machine, hidden from the model, redacted from logs and reports.