Skip to content

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_product and create_service_account first answer with what will happen and a code (valid 5 minutes, bound to your token, the tool and the exact arguments); the second call with confirm=<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

get_skills, whoami

Products

list_products, register_product, list_applications, delete_application, list_application_access, grant_application_to_group, list_providers

People and teams

list_users, create_user, create_invitation, list_groups, add_user_to_group, create_service_account

Sign-in flows

list_flows, get_flow, list_stages, bind_stage_to_flow

Activity

list_events

Read-only

engine_request

Last updated 18 Nov 2026

MCP server · REM Platforms Blog