MCP guided setup
Choose OAuth or Manual token in the workspace connection screen.
Open connection guide ↗OAuth is the preferred path
A supported client initiates the authorization handshake, opens the Telemio consent page, and returns to the client.
01
Open your MCP client
Use an installed Telemio integration or a client that supports a registered OAuth connection. OAuth support varies by harness.
02
Add the remote server
Use the HTTPS MCP URL below; do not include a workspace bearer token in a shared configuration.
https://mcp.telemio.sh/mcp
03
Choose Connect / Authenticate
The client requests authorization and opens your browser. The Telemio consent screen shows the requested scopes.
04
Sign in to Telemio
Use your WunderCorp/Cognito credentials or your supported federated sign-in, then return to the client.
05
Verify a read
Ask the agent to list available workspaces and summarize recent service health. Confirm an MCP tool is actually called.
Important: A public MCP URL alone does not guarantee that every client can perform OAuth. Clients need a compatible OAuth registration/redirect flow. If a raw custom-MCP setup does not support it, use the manual key tab in the Telemio console.
Manual setup and reference
Workspace keys remain available as an explicit compatibility path, with a separate trusted environment variable.
MCP reference
Read the client and workspace rules in the agent reference.
Read reference ↗