Claude
Connect Claude Desktop, Claude Code or claude.ai over MCP. Nothing to install, no key to copy.
Digitalyser.io runs a remote MCP server with an embedded OAuth 2.1 authorization server. Claude discovers it, registers itself, and asks the user what the connection may do. You copy no secret anywhere.
The endpoint
https://app.digitalyser.io/api/mcpTransport is Streamable HTTP. SSE is deliberately not served — the July 2026 protocol revision dropped SSE resumption, and under SSE the URL parameter never reaches the POST, which would break project scoping. Any client that requires an SSE endpoint cannot use this server; use the REST facade instead.
Claude Code
claude mcp add --transport http digitalyser https://app.digitalyser.io/api/mcpThe first call opens the consent screen in your browser. Pick a project, tick what the agent may do, and you are connected.
Claude Desktop and claude.ai
Add a custom connector pointing at the same URL. Claude performs dynamic client registration (RFC 7591) and PKCE on its own.
If the consent screen warns that the redirect points at a local port on your machine, that is normal for a desktop application. Authorise only if you just started the connection yourself.
What Claude sees
Three tools, not a hundred:
| Tool | Effect |
|---|---|
listCapabilities | Returns the catalogue this credential may use, each with its JSON Schema |
invokeCapability | Runs one. Returns a value, a questionnaire to fill in, or a proposal |
applyProposal | Applies a diff the user has seen. The diff is recomputed and compared before writing |
The catalogue is deliberately not a fixed tool list. It varies by credential, by plan and by the capabilities the user ticked at consent — a frozen tool list would announce capabilities the server would then refuse, which is a lie one line earlier.
The write path
No capability writes on first call. A propose returns a proposalId and a diff; the user reads it;
applyProposal then recomputes the diff server-side and compares. A stale diff, a replayed handle, an
expired one, or one belonging to another project is refused.
Start read-only. The consent screen offers a Read only preset — connect with it, ask Claude about your last audit, and widen the scope once you have seen what the tool does with your data.
Discovery, for client authors
curl https://app.digitalyser.io/.well-known/oauth-protected-resource/api/mcp
curl https://app.digitalyser.io/.well-known/oauth-authorization-serverThe first is RFC 9728 protected-resource metadata and names the authorization server. The second is
RFC 8414 and carries the endpoints, with S256 as the only supported PKCE method. Both are public.