Reach · 08.08
MCP OAuth
Discovery, dynamic client registration, and PKCE — how Agentis authenticates against an external MCP server on an agent's behalf.
The standard OAuth dance, automated end to end
Connecting to an MCP server that requires OAuth doesn't ask an operator to hand-register a client somewhere first. Agentis performs discovery against the server's published metadata, registers itself dynamically as a client, and completes the flow with PKCE — the same code-verifier/code-challenge mechanism modern OAuth expects for a public client with no static secret. The result is a connection an agent can actually use, without an operator needing to understand OAuth internals to get there.
Continue
Agentis both consumes external MCP servers and publishes its own workflows as JSON-RPC 2.0 Streamable-HTTP tools — one registry, many projections.
Hand-written connectors, templated HTTP connectors, a generic HTTP fallback, and custom JSON-Schema manifests.