Overview
The MCP endpoint, OAuth flow, and multi-workspace headers.
Tellzm exposes a Model Context Protocol server at https://mcp.tellzm.com so AI assistants like Claude can act on your workspaces directly. The same surface powers the n8n-nodes-tellzm community package.
What you get
- 300+ tools across Tasks, Projects, Forms, Pages, Data Tables, Calendars, Routines, Spaces, Apps, Diagrams, Reports, and the MCP catalog itself
- OAuth 2.0 + PKCE authentication
- Per-credential rate limiting (600 req/min sliding window)
- Multi-workspace policy: include or exclude specific workspaces, decide whether future workspaces are auto-included
- HMAC-signed outbound webhooks for event triggers
Endpoints
| Endpoint | What it does |
|---|---|
https://tellzm.com/oauth/authorize | OAuth 2.0 authorization (browser flow) |
https://api.tellzm.com/oauth/token | Token exchange + refresh |
https://mcp.tellzm.com/mcp | The MCP JSON-RPC surface |
https://api.tellzm.com/mcp/whoami | Returns your credential's workspace list + scopes |
https://api.tellzm.com/mcp/catalog | Public list of every available tool module |
https://mcp.tellzm.com/.well-known/oauth-protected-resource | OAuth metadata (RFC 9728) |
Connecting from Claude
In Claude's Settings → Connectors, add a new MCP connector pointed at https://mcp.tellzm.com. Claude walks the user through the same OAuth + consent flow described in n8n credentials.
Connecting from your own client
The server speaks standard MCP over Streamable HTTP. Use the official MCP SDKs (TypeScript, Python). After completing the OAuth handshake, point a StreamableHTTPClientTransport at https://mcp.tellzm.com/mcp and pass the access token as Authorization: Bearer <token>.
Multi-workspace requests
Pass the target workspace's slug in the request header:
X-Tellzm-Workspace-Slug: ibrand
The server validates the slug against your credential's authorized list. If you omit the header, requests run against the credential's default workspace.