Skip to content
Spekir
LiveMCP connector

Atlas in VS Code Copilot

Engineers query application ownership, ADRs, and technology decisions inline via GitHub Copilot Chat — without leaving VS Code. Atlas answers from the real EA data, not from memory.

Get started →

What engineers use it for

Ownership lookup

@atlas get_app_context billing-service

Type the app name in Copilot Chat while reviewing code, and Atlas returns the owner team, lifecycle status, business criticality, and the top 3 capabilities it supports — inline in the editor.

ADR lookup before you build

@atlas find_decisions authentication

Before writing an auth implementation, ask Atlas for relevant ADRs. You get the decision text, status, and a direct link to the full record in Atlas. Stop reinventing what's already been decided.

Technology radar check

@atlas list_technologies {"quadrant": "hold"}

Before adding a new dependency, check whether the library is on the 'hold' quadrant in your technology radar. Catch architectural drift before it enters the codebase.

Set up in 3 steps

Requires VS Code 1.99+ and GitHub Copilot Chat.

1

Create an MCP API key in Atlas

Go to atlas.spekir.com → Settings → MCP API Keys. Click Create API key, give it a name, and select read:* scopes. Copy the key — it is shown once in plaintext.

2

Add Atlas to VS Code settings.json

Open VS Code settings.json via Ctrl+Shift+P → Open User Settings (JSON). Add the Atlas MCP server block. Reload the window after saving.

{
  "github.copilot.chat.mcp.servers": {
    "atlas": {
      "url": "https://atlas.spekir.com/api/mcp/v1",
      "headers": {
        "Authorization": "Bearer mcp_YOUR_KEY_HERE"
      }
    }
  }
}
3

Query Atlas in Copilot Chat

Open GitHub Copilot Chat (Ctrl+Shift+I) and type @atlas followed by any tool name. Start with @atlas list_applications to confirm the connection works.

Full setup guide with troubleshooting →

Your data stays yours

Atlas MCP API keys are workspace-scoped. A key can only return data from the specific Atlas workspace it was created in. Keys can be revoked instantly from Settings → MCP API Keys.

Works with your existing Copilot plan

Atlas uses standard MCP Streamable HTTP transport. No additional Copilot plan upgrade is required. Any GitHub Copilot subscription with Copilot Chat enabled can connect to Atlas.

Frequently asked

Which VS Code and Copilot versions are required?

VS Code 1.99 or later and a current GitHub Copilot Chat extension. The github.copilot.chat.mcp.servers setting was introduced in VS Code 1.99. Update via VS Code → Check for Updates and the Extensions panel.

Does this require GitHub Copilot Business or Enterprise?

Atlas MCP works with any GitHub Copilot plan (Individual, Business, or Enterprise) as long as GitHub Copilot Chat is enabled. The MCP integration is on the VS Code side, not the Copilot plan.

Is my architecture data safe?

Atlas MCP API keys are workspace-scoped — they only return data from your specific Atlas workspace. Keys can be revoked instantly from Settings → MCP API Keys. No architecture data is sent to GitHub beyond what Copilot Chat itself processes.

Do all team members need their own API key?

Yes. Each developer should create their own key so you can revoke per-person access independently. Keys are rate-limited per key (60 req/min default), so sharing a key will exhaust the limit faster.

Can Atlas write changes back from VS Code?

No. All v1 tools are read-only. Write tools (propose_changes, get_proposal_status) are planned for v2 — any changes proposed from the IDE will go through Atlas's existing change-proposal review flow before anything is committed.

Ready to connect Atlas to VS Code?

Get started →Talk to us →