/docs/auth
Your agent signs in. You approve it.
MindMap uses OAuth 2.1, so agents never see your password. You approve each client once, choose what it may do, and can revoke it at any time.
How sign-in works
- The client calls
/mcpwithout a token and gets401with aWWW-Authenticateheader that points to the server’s resource metadata. - It reads
/.well-known/oauth-protected-resourceand/.well-known/oauth-authorization-server, then registers itself with dynamic client registration. - Your browser opens MindMap. You sign in if needed, then approve or deny the client on the consent screen, which shows its name and the scopes it asks for.
- The client exchanges the code, with PKCE, for a token and sends it as a Bearer token on every call to
/mcp.
Scopes
| Scope | Allows | Tools |
|---|---|---|
mindmaps:read | Read your mind maps and their activity. | list_mindmaps, get_mindmap, get_mindmap_activity |
mindmaps:write | Create, edit and delete your mind maps. | create_mindmap, edit_mindmap, delete_mindmap |
A call without the scope it needs returns FORBIDDEN_SCOPE. Connected agents and revoking them stay in the web app: no tool can see or change them.
Revoke an agent
Open Settings → Connected agents and choose Revoke. The agent’s next call returns 401, and it has to sign in and be approved again.
Discovery URLs
| Document | URL |
|---|---|
| Protected resource metadata | https://mindmap.jpamorgan.com/.well-known/oauth-protected-resource |
| Authorization server metadata | https://mindmap.jpamorgan.com/.well-known/oauth-authorization-server |
| MCP server card | https://mindmap.jpamorgan.com/mcp/server-card |
| AI catalog | https://mindmap.jpamorgan.com/.well-known/ai-catalog.json |