Integration registry
Connect Atlas to the models and tools your team approves
Every entry names the connection, the Atlas implementation evidence, and the vendor-recognition status. Test-backed means covered by the Atlas repository. It does not mean vendor-certified.
Test-backed
A source path and automated test exist in the Atlas repository.
Protocol supported
Atlas implements a documented protocol boundary such as MCP.
Machine readable
The same registry is available at /integrations.json for tools and crawlers.
Local model runtime
Test-backedOllama
Atlas detects an Ollama server on localhost, lists installed chat models, and registers them through its OpenAI-compatible provider path.
- Connection
- Local HTTP API on port 11434
- Data boundary
- Local endpoint selected by the user
- Vendor recognition
- not submitted
- Evidence reviewed
- 2026-08-03
Ollama has not listed, certified, or endorsed Atlas. Offline mode must be enabled separately.
Local model runtime
Test-backedLM Studio
Atlas falls back to the LM Studio model endpoint on localhost when Ollama is unavailable and registers discovered chat models as a local provider.
- Connection
- OpenAI-compatible HTTP API on port 1234
- Data boundary
- Local endpoint selected by the user
- Vendor recognition
- not submitted
- Evidence reviewed
- 2026-08-03
LM Studio has not listed, certified, or endorsed Atlas. Offline mode must be enabled separately.
Hosted model router
Test-backedOpenRouter
Atlas supports OpenRouter as a model provider and sends OpenRouter's public app attribution headers with the cli-agent category.
- Connection
- OpenRouter API with your OpenRouter key
- Data boundary
- External hosted provider
- Vendor recognition
- attribution ready
- Evidence reviewed
- 2026-08-03
No attributed request has been approved or sent. OpenRouter usage is not appropriate until its route matches the organization's data policy.
Tool and context protocol
Protocol supportedModel Context Protocol
Atlas connects to local and remote MCP servers and exposes discovered tools, prompts, and resources through its terminal workflow.
- Connection
- Local stdio or remote HTTP transport
- Data boundary
- The configured MCP server and its credentials
- Vendor recognition
- not applicable
- Evidence reviewed
- 2026-08-03
Protocol support does not validate every server. Each MCP server inherits the access of its process, tools, and credentials.
Need an integration reviewed?
Atlas separates implementation evidence from vendor recognition. Request a protocol or model-runtime evaluation and include the deployment boundary your team needs.