Local and remote MCP access
Connect a compatible AI client to your monitoring with limited access.
On this page
What you need
A compatible MCP client. Local access needs an installed CLI and private identity file; remote access needs an authorised connection.
How to do it
- For remote access, enter https://metribeacon.com/mcp in your client and follow its sign-in and permission prompts.
- For local access, configure the client to start metribeacon mcp stdio using your private identity file.
- Start with read access and check the available tools. Add write access only for actions you want the client to perform.
Good to know
MCP uses the same workspace access and account allowances as the app. A device key is not a remote MCP token. Do not put tokens in URLs or give a client more rights than needed.
Local access uses the saved CLI identity. Remote access uses OAuth or the documented machine token flow. You can revoke a remote connection in account settings.
metribeacon mcp stdio --config "$HOME/.config/metribeacon/identity.json"If something goes wrong
Sign in again if a remote token expires. An insufficient_scope error means you have not granted the required permission; review it before reconnecting.
Related guides
- Complete MCP tool catalog
Find monitoring tools and check their inputs before asking a client to make changes.
- MCP OAuth and PKCE
Approve a remote MCP client's access and revoke it when no longer needed.
- Machine identity and recovery
Create a machine account without a browser and keep its recovery identity safe.