Skip to content
Docs
Arcus
Popular questions
↑↓ to navigate↵ to selectesc to close
Book a demo

Developers

The Developers tab covers the tools that connect Arcus to where developers work: coding agents, the terminal, AI clients, and your Git repositories. Developers don’t change how they work. Their sessions and pull requests reach Context Management in QI Home, where Arcus generates test cases from them.

  • CLI: Keep tests in your repository as .sigma files, check and run them on your own machine, and push them to Arcus. A coding agent can run it for you.
  • MCP server: Let an AI client such as Claude Code read your Arcus projects and test assets, and draft test cases back into Arcus.

Install the Arcus plugin in your coding agent, so each session reaches Context Management as context for test generation.

  • Claude Code: Set up the Arcus plugin for Claude Code.
  • Codex: Set up the Arcus plugin for the Codex CLI.
  • Cursor: Set up the Arcus plugin for Cursor or VS Code.
  • GitHub Copilot: Set up the Arcus plugin for the GitHub Copilot CLI. This is separate from Copilot, the Arcus test execution feature.

The plugin and the MCP server are separate, and you can install both. The plugin sends your coding session to Arcus. The MCP server lets your agent read from Arcus.

Connect your repositories, so every pull request your team raises reaches Context Management. Arcus generates test cases from it once it’s mapped to a sprint, which happens automatically when the pull request carries a ticket ID from your connected tracker.

  • GitHub: Install the Arcus GitHub App.
  • GitLab: Connect GitLab, so merge requests reach Arcus.
  • Bitbucket: Connect Bitbucket, so pull requests reach Arcus.

To call the Arcus API, see the API Reference, and create a key in API keys.

Was this page helpful?