MCP server
REM Auth's MCP server for administrators' AI agents - the tools, the two-step writes, and why it answers only on REM's internal network.
REM Auth serves an MCP server at /mcp (streamable HTTP). It is reachable only from REM's internal network; from the internet it answers 403 REM Auth's MCP is only reachable from REM's internal network.
{"mcpServers": {"rem-auth": {"type": "http", "url": "https://auth.remplatforms.com/mcp",
"headers": {"Authorization": "Bearer <your service-account or personal API token>"}}}}Rules
Your permissions only. Every call runs with the caller's own token; there is no server token. No token = 401. You see and may call only the tools your permissions allow.
Two-step writes.
create_user,create_invitation,add_user_to_group,grant_application_to_group,bind_stage_to_flow,delete_application,register_productandcreate_service_accountfirst answer with what will happen and a code (valid 5 minutes, bound to your token, the tool and the exact arguments); the second call withconfirm=<code>does it. Every write is recorded (who, tool, arguments, outcome).No secrets through the model. There is no password tool: people get an invitation link. Client secrets and token values are never returned; the answer says where a person reveals them in the admin.
Read-only escape hatch.
engine_request(path, params)is GET only and refuses tokens, keys, recovery, impersonation and system paths.
Tools
Area | Tools |
|---|---|
About |
|
Products |
|
People and teams |
|
Sign-in flows |
|
Activity |
|
Read-only |
|
Last updated 18 Nov 2026