Connect the tools you use to review agent changes.
Use a coding agent, your model provider, or a shell command with Versalist. See what each connection does and where its evidence stays.
Coding agents and local runs
Connect an agent or run your own command from your repository.
Coding agents
The Versalist Model Context Protocol (MCP) server connects to Claude Code, GitHub Copilot, Codex, Cursor, Antigravity, OpenCode, JetBrains Junie. Each guide covers setup and the command-line interface (CLI).
Choose an agent guideShell commands and continuous integration
The CLI records local runs and runs your verifier command. Compare two evaluated runs in a continuous integration (CI) job. A failed comparison returns exit status 1. Local records are self-reported and are not uploaded automatically.
Read the CLI comparison guideModel providers
Add your provider credentials for supported model calls. Credentials are stored per user and provider.
Supported providers
- OpenAI
- Anthropic
- Google Gemini
- xAI
- Mistral AI
- Cohere
- DeepSeek
- AWS Bedrock
- Azure OpenAI
- Google Vertex AI
- Cloudflare Workers AI
- Groq
- Cerebras
- Together AI
- Fireworks AI
- Baseten
- DeepInfra
- OpenRouter
- Perplexity
- Ollama / custom OpenAI-compatible
Beta providers
- Replicate
Provider availability can depend on the deployment configuration. The custom endpoint option accepts an OpenAI-compatible endpoint. The endpoint must be reachable from the Versalist deployment. Private and local addresses require explicit deployment configuration. A provider listing in the tool directory does not confirm an integration.
Know what each review records
Local CLI comparisons
The CLI checks that both runs belong to the active challenge and use the same verifier command. It saves comparison records locally.
Hosted release reviews
A release review checks matching challenge, skill, rubric, and case identifiers. Model identifiers are compared when present. A person records the release decision.
Explore release reviewsCredentials and access
Provider credentials and Versalist API keys have different purposes.
- Provider credentials authorize supported model calls. The deployment stores new credentials in Google Secret Manager or an encrypted database. Existing credentials can use a different backend.
- Versalist API keys authorize the CLI, MCP server, and supported API requests. You can scope and revoke these keys.
- Company-managed provider keys are not available. Each user manages their own provider credentials.
Need another integration?
Tell us which tool your workflow uses and what you need it to do.