ChatGPT and Claude Code plugins

Choose a connection

The catalog integration uses https://metribeacon.com/mcp/catalog with browser OAuth. Download the OpenAI ZIP or Claude plugin. A package download does not imply approval or availability in a platform directory.

The existing Claude Code remote/local bundle and full OpenAI package remain available for the complete monitoring access at /mcp. For Claude Code, unpack its bundle privately, add the directory with /plugin marketplace add /absolute/path/claude and choose metribeacon-remote@metribeacon or metribeacon-local@metribeacon. The local option requires the CLI and METRIBEACON_IDENTITY_FILE pointing to your existing private identity. For account creation from the chat, install the current MetriBeacon CLI and the separate OpenAI local helper or Claude local helper. These packages run metribeacon mcp plugin-stdio in a client supporting local MCP processes; they do not run in the web client. They keep their own private identity and start with read-only access. Use get_plugin_setup before explicitly accepting the current legal versions and requesting create_machine_account. An email claim or permission request returns a browser link. Select the helper’s short-lived confirmation file there, approve separately, and verify an email claim through the email link. Never paste private files into chat. Existing accounts are not merged. Change read/write permissions in Settings → Plugin connections or request_permission_change; clearing every permission revokes the connection.

Approve only needed access

Start with reading. Select configuration or telemetry write access only for the actions you need. Catalog access excludes API key changes, secret HTTP headers, notification credentials, subscribers, domain management and machine pairing; manage these on the website or through the existing complete access. The two MCP resources have separate connections and tokens. Deletion and publication still require confirmation. Inspect and revoke access in account settings under Plugin connections or with metribeacon mcp connections list.

Connect a machine account

Machine pairing is available only for the complete /mcp access. If offered on its OAuth page, choose Connect machine account. Save the ten-minute code privately and inspect client and permissions with the commands below. Approve only the needed scopes, then return to the original browser. This connects the integration without creating a general browser session.

metribeacon mcp connect inspect --code-file ./private-code.txt
metribeacon mcp connect approve --code-file ./private-code.txt --scopes "account:read config:read telemetry:read" --yes
metribeacon mcp connect deny --code-file ./private-code.txt

Use the monitoring view

Compatible clients can show an overview, histories and incidents; other clients receive structured tool results. Treat readings and event text as data, not instructions to the AI. Use the same account limits and destinations as in your dashboard.