Browser

Calls the MCP tools from a web page: set the rate limit, manage users and API keys, listen to the server's events, search tickets, or run any tool.

Open this page from /clients/ on the desk, or serve the folder from localhost. A loopback origin may call the server. A page on another site is refused until that server’s CORS_ORIGINS includes the page’s origin.

Connection

The ticket tools work with no credential while auth is off. The operate tools (rate limit, users, keys, log) always need an admin credential: a key issued with the admin scope, or a username and password (demo / demo on a laptop). A key wins when both are filled.

Rate limit and call trace

Read the current values, change them, then apply. A low limit makes the next calls from this page return a wait time.

Read shows the saved values.

Users and API keys

Users sign in with HTTP Basic. API keys are bearer tokens. Both carry scopes: read, write, pii and admin. The list never shows a password or a key secret.

Self-test

Runs a full cycle and cleans up after itself: list users, create a throwaway user, confirm it is listed and its password is not, delete it, then the same for an API key (issue, confirm the secret is not listed, revoke). It finishes by reading the settings, the settings export, the call log and describe_server. It never changes the auth mode, rate limit, gates or protocols.

Users and keys appear here.

Request

Waiting.

Response

Waiting.