For developers

An MCP server, not another tab.

One command, and your agent knows your strategy.

Ambix is a remote MCP server your team’s AI clients and CLIs connect to. Once connected, your agent pulls the team’s strategy, live initiatives and latest findings straight into the conversation — in real time, mid-task. No copy-paste, no context-switching, no stale doc to hunt down.

Context lives in Ambix; the work happens in the AI clients your team already uses — no lock-in to any vendor. Teammates who don’t use one can browse the same workspace in a normal web app. Here is what you’d be wiring up.

Works with Claude, Claude Code, Cursor, Codex, VS Code — and any AI tool that speaks MCP.

Agentic, not copy-paste

When your agent has a question about direction, it asks Ambix — and reads the team’s strategy, active initiatives and latest findings back in the same turn. Nothing to paste in, nothing to keep in sync, no tab to switch out to. The product context is just there, underneath whatever your agent is already doing — and every write is confirmed with you before it lands.

With Claude Code it’s a single line — no config to hand-edit, no keys:

claude mcp add --transport http ambix https://mcp.ambix.ai

Every other client — Claude, Cursor, Codex, VS Code — is a browser sign-in away below.

Endpoint: One MCP server at https://mcp.ambix.ai — served at the root, no path suffix.
Transport: Streamable HTTP. Works with any MCP-capable client — Claude, Claude Code, Cursor, Codex, VS Code, or your own. MCP is an open standard: swap clients tomorrow and Ambix comes along. No lock-in to any AI vendor.
Auth: OAuth 2.1 with resource indicators (RFC 8707). You sign in through the browser when you connect — no API keys to paste, no tokens to rotate by hand. Access is membership-gated and checked server-side on every request: once a removal propagates, the next call from that session is refused — no key or token to chase down. Your memberships decide what you can reach; one connection can switch between the workspaces you belong to without re-connecting.
Tool surface: A compact, fixed set of tools. A few essentials are always on — get_workspace_context, get_strategy, list_workspaces — and every other operation is discovered by intent (find_tools) then run by name (call_tool). For example: find_tools("log a customer interview") surfaces the matching write tool; call_tool runs the one you name, and the client confirms the write with you before anything lands. Around a dozen operations sit behind those two, so your client’s tool list never grows past a handful no matter how much the product grows. Because your client discovers tools by intent at call time instead of pinning names, new operations appear on their own and nothing in your setup breaks when the surface changes.
Your data: Your data stays in the EU, encrypted in transit. Every change is recorded, so you keep the full history. Workspaces are isolated server-side on every request — no cross-workspace reads, ever.
The web app: Teammates who don’t use an AI client get an overview of where things stand — strategy, active initiatives and latest findings — without requiring an AI license. Nothing to install, nothing to configure. When more is needed, the product team can use their AI clients to pull together clear summaries, visuals and presentations from the workspace and share them in seconds.
Delivery tools: Ambix never writes to Jira, Linear, or GitHub, but connects through MCP to work alongside them — so strategy and priorities stay aligned with the work happening everywhere else. Your tracker owns ticket status; there’s no second backlog to groom.
Writes: Ambix proposes, your team confirms. The AI client never silently mutates your workspace — every write is confirmed in the conversation.

Connecting

Pick your client — each one signs in through the browser the first time, and that’s the whole setup.

In Claude, open Settings → Connectors and choose “Add custom connector”.
Paste the server URL below and save.
When Claude asks for an OAuth Client ID, paste the Client ID below — leave the client secret empty.
Sign in to Ambix once — use your work email. That’s the whole setup.

server url

https://mcp.ambix.ai

oauth client id

lZ9ke7V6EU1c8X2flhjtKXPbinmWRMDi

GitHub Copilot CLI (advanced — fragile workaround)

The standalone copilot CLI tries to reconnect MCP servers remotely and runs into Ambix’s no-dynamic-registration policy (copilot-cli#2717). Use Copilot in VS Code if you can — it just works. If you need the CLI, this wrapper keeps the server URL out of Copilot’s reach. It depends on current Copilot behaviour and may break when that issue is fixed.

Save this as ~/.copilot/ambix-bridge.sh and run chmod +x on it.

ambix-bridge.sh

#!/bin/sh
# ~/.copilot/ambix-bridge.sh  —  then: chmod +x ~/.copilot/ambix-bridge.sh
exec npx -y mcp-remote@0.1.38 https://mcp.ambix.ai 3336 --host 127.0.0.1 \
  --static-oauth-client-info '{"client_id":"lZ9ke7V6EU1c8X2flhjtKXPbinmWRMDi"}' 2>>/tmp/ambix-bridge.log

Point Copilot at the script (no URL in the config) — ~/.copilot/mcp-config.json:

mcp-config.json

{
  "mcpServers": {
    "ambix": {
      "type": "local",
      "command": "/Users/you/.copilot/ambix-bridge.sh",
      "tools": ["*"]
    }
  }
}

Menus move around between releases — if yours looks different, search the settings for “MCP” or “connectors”.

Sign up to create your workspace — the connector then authenticates, and your workspace membership decides what you can reach.

Built in Sweden. We run our own product work on Ambix every day — the server described on this page is the one we plan in. More detail: how it works and the plain facts.

See how it works →