Operate

MCP server

Connect an AI client to inspect and manage Authometry with separately approved read and write access.

Start with the MCP URL

Point the MCP client at the environment issuer followed by /mcp. Authometry returns a protected-resource challenge so the client can discover the authorization server, register as a public OAuth client when needed, and start Authorization Code with S256 PKCE.

https://authometry.ch3n.cc/mcp

Review and connect

Sign in with an Authometry admin account. The consent page identifies the MCP client, its dynamic-registration status, the canonical MCP resource, and every requested permission. Connect only when those details match the client you started from.

Access tokens are audience-bound to this MCP URL. Authometry rejects tokens issued for another API or environment.

Inspect Authometry

list_environments returns environments in the token's workspace.
list_applications searches non-secret OAuth client configuration.
list_scopes reports resource scope sensitivity and application usage.
list_authorization_traces searches recent redacted protocol traces.
get_authorization_trace returns one redacted trace with its explanation and steps.

Pass an environment slug or UUID when needed. Omitting it selects the workspace's default environment.

Manage through the dashboard API

Approve mcp:write to let the client create services, edit applications, manage scopes and policies, rotate or revoke credentials, apply configuration, and perform the other operations available in the dashboard.

list_management_operations returns every supported method and path template.
management_api_read calls any supported dashboard GET operation.
management_api_write sends POST, PATCH, or DELETE operations through the same API handlers as the website.

Existing connections remain read-only until you reconnect and approve mcp:write. Dashboard role checks, tenant boundaries, optimistic versions, audit logs, and destructive confirmations still apply.