Connect claude.ai

claude.ai and Claude Desktop reach your workspace through its gateway by signing you in, so they hold no token you made.

1. Keep slate serve running on a machine in your network that holds the connections (Agents shows it online). 2. In claude.ai, add a custom connector in its settings, with your workspace's address followed by /mcp. Claude Desktop adds one the same way. 3. It sends you to this console to sign in, then asks you. The page names the app as it named itself (and who publishes it, when a domain does), where its access will go, the workspace and your role. A warning appears when the access goes to a program on your computer. Let it act lets it write where your role may; a role that cannot write anywhere shows it off, and says why. Let it in sends you back to the app; Decline sends it away with nothing. 4. Ask it as you would ask the agent's own server: it offers the tools your workspace has a connection for and your role may use.

The app acts as you, with your role as it stands at each call: every call is decided at the gateway and again on the agent, and leaves one row in the workspace's audit, with the arguments masked and never the result.

Disconnect it in People, under Connected apps (you, or an Owner): its next call is refused. A member who leaves the workspace takes their apps with them.

Claude Code takes an API token instead: Your AI client says how.