Connect Claude to Glacier

Glacier's MCP server lets Claude read and write your workspace natively — create cards, move them across the board, draft docs, and pull metrics, all without leaving your conversation. Connection takes under two minutes.

Recommended: Claude.ai web

The easiest way to connect is through claude.ai. No config files or API keys needed.

Open claude.ai and go to Settings → Connectors (or Integrations, depending on your plan).
Click Add custom connector.
Paste the Glacier MCP URL:
```
https://www.getglacier.ai/api/mcp
```
Glacier's sign-in page will open. Sign in with your Glacier account email (it doesn't need to match your Claude.ai email).
Click Authorize.

Claude now has access to your Glacier workspace from any conversation.

Already connected but tools aren't showing? Remove the Glacier connector and re-add it — this triggers a fresh OAuth sign-in.

Claude Code (developer path)

Claude Code (the CLI) supports OAuth — no API key required.

claude mcp add --transport http glacier https://www.getglacier.ai/api/mcp

On first connection, Claude Code opens a browser window for a one-time sign-in. After that, tokens refresh automatically and persist across sessions.

Or add it directly to your project's .mcp.json:

{
  "mcpServers": {
    "glacier": {
      "type": "http",
      "url": "https://www.getglacier.ai/api/mcp"
    }
  }
}

Tip: You can also copy the snippet pre-filled from Project Settings → MCP & developer → Quick setup inside Glacier.

Advanced: API key auth

API key auth is available for Claude Desktop, Cursor, VS Code, CI environments, and any client that doesn't support OAuth.

Get an API key: In Glacier, go to Account Settings → MCP API Key and click Generate key. Copy it — it starts with glc_sk_ and is shown once.

Claude Desktop

Open your Claude Desktop config file:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

Add Glacier under mcpServers:

{
  "mcpServers": {
    "glacier": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/client-http"],
      "env": {
        "MCP_SERVER_URL": "https://www.getglacier.ai/api/mcp",
        "MCP_AUTH_TOKEN": "glc_sk_your-key-here"
      }
    }
  }
}

Quit and reopen Claude Desktop. The Glacier tools appear in the tool panel.

Claude Code (static token)

If you prefer a fixed token for CI or shared environments:

claude mcp add --transport http glacier https://www.getglacier.ai/api/mcp \
  --header "Authorization: Bearer glc_sk_your-key-here"

Cursor / VS Code

In your .cursor/mcp.json or VS Code MCP settings:

{
  "mcpServers": {
    "glacier": {
      "url": "https://www.getglacier.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer glc_sk_your-key-here"
      }
    }
  }
}

Multi-workspace accounts

If your Glacier account belongs to more than one workspace, Claude sees all of them after sign-in. Use list_workspaces to discover the workspace IDs, then pass workspace_id to board and card tools to target the right one.

"List my Glacier workspaces and tell me what projects are in each."

What Claude can do

Once connected, Claude has tools for the full Glacier workflow.

Board

List columns and cards, check WIP limits
Create cards from a brief — one at a time or in batch
Move cards between columns, update fields, set priority
Read card descriptions, labels, assignees, and linked GitHub issues

Docs

List, read, create, and update workspace docs
Link a doc to a card, or create a doc from a meeting summary

Metrics

Pull throughput and cycle time for any project
Generate weekly status reports grounded in real data

Team & organisation

List workspace members and roles
List and create labels

Troubleshooting

Tools don't appear in Claude.ai. Remove the Glacier connector from Claude.ai settings and re-add it — this reruns the OAuth flow.

Tools don't appear in Claude Code. Check that your .mcp.json or ~/.claude.json has the correct URL: https://www.getglacier.ai/api/mcp. If you're using OAuth, make sure you completed the browser sign-in when Claude Code first connected. Re-add the server entry and restart Claude Code to trigger a fresh sign-in.

401 Unauthorized. Your API key may have been rotated, or your OAuth session may have expired. For OAuth, re-add the connector or reconnect from Claude Code. For API keys, generate a new key in Account Settings and update your config.

Wrong email warning during OAuth. Use the email tied to your Glacier account on the Glacier sign-in screen — it doesn't need to match the email on your AI tool. If you accidentally signed in with the wrong email, disconnect and reconnect to restart the OAuth flow.

Claude can't find a project. Make sure you're passing the correct workspace_id to workspace-level tools. Use list_workspaces to confirm the ID.

Still stuck? Email us at hello@getglacier.ai or open an issue at getglacier.ai/docs.