Connecting agents

Estratos is a standard remote MCP server. Any client that speaks the Model Context Protocol can read and write your company's memory — no bespoke integration. This section walks through connecting each agent your team uses, and how to troubleshoot connections.

How connecting works

For most agents you install the Estratos Memory plugin from a marketplace; for anything else you point the client at the raw MCP endpoint. Either way, the first time the agent connects it runs a one-time OAuth handshake in your browser:

1. The agent discovers the Estratos authorization server from the endpoint automatically.
2. Your browser opens the Estratos consent screen.
3. You pick which workspace to connect (if you belong to more than one) and review the scopes the client is requesting.
4. You click Allow, and the agent receives a token scoped to that one workspace.

No client ID, secret, or API key goes into any config. The token identifies you and your workspace on every call — you never pass a workspace or account as a parameter.

What installs

The Estratos Memory plugin bundles the MCP memory server plus skills — retrieval, recording, hierarchy, and naming. Generic MCP clients that can't install a plugin get the tools only and rely on the server's built-in tool descriptions.

Everything on this page mirrors the Connect › Configure agents screen inside the app, where each card shows the same steps with a copyable marketplace URL and a live "Test your connection" status.

Pick your agent

• Claude Desktop — install from the plugin marketplace
• Codex — Codex app and CLI
• Copilot Cowork — Microsoft 365 plugin marketplace
• Generic MCP client — any MCP-capable agent, manual setup
• Troubleshooting — reconnecting, token expiry, and testing a connection

Requirements

Connecting an agent requires the API access entitlement on your workspace's plan. Only workspace Owners can approve the OAuth consent and bind a token to a workspace. Once connected, what a member's agent can do is bounded by that member's role — see roles and permissions.

Prefer the raw endpoint or a headless setup?

The plugin is the easy path, but everything is a standard MCP + OAuth surface underneath. If you're building your own client, wiring CI, or want the protocol-level details — endpoints, scopes, discovery documents, dynamic registration — see the MCP server reference.