MCP server and sign-in
Agensi runs one remote MCP server over Streamable HTTP. New connections use the sign-in-first endpoint.
| Endpoint | Behaviour |
|---|---|
https://mcp.agensi.io/mcp/auth | Default for new connections. Every request needs a valid OAuth token, search included. |
https://mcp.agensi.io/mcp | Older connections. Every tool call needs sign-in here too. Connecting and listing the tools works before sign-in, so the agent can start it. |
OAuth 2.1#
- Discovery:
/.well-known/oauth-protected-resourceonmcp.agensi.io, and/.well-known/oauth-authorization-serveronmcp.agensi.ioandwww.agensi.io. - Registration: dynamic client registration is open. A redirect URI is required: https, localhost or a custom scheme such as
claude://. - Flow: authorization code with PKCE, S256 only. Public clients.
- Scopes:
readto browse skills, creators and the user's library.installto buy and use skills, paying from the user's balance only after the user approves. - Tokens: access tokens last 1 hour. Refresh tokens last 30 days and rotate on every use. Reusing an old refresh token revokes the connection.
- No API keys. Only OAuth tokens are accepted.
One agent per account. When a new client receives its first token, every other client on that account loses access.
Usage limits. Each account can load skills (get_skill, including single files) up to 60 times a minute and 1,000 times a day, and start using up to 200 new skills a day (100 during its first 24 hours); skills you own count only toward the per-minute limit, and daily limits reset at 00:00 UTC.