NAME

anyevent-mcp - initialize MCP configuration and manage users and permissions

SYNOPSIS

anyevent-mcp init
anyevent-mcp manage-rules fs-default
anyevent-mcp create-user chatgpt
anyevent-mcp revoke-user chatgpt
anyevent-mcp edit-rules-file /path/to/rules.ini

DESCRIPTION

anyevent-mcp sets up the shared AnyEvent::MCP configuration and manages permission rules saved by its servers. Use it to review permissions you have allowed or denied permanently, remove a rule, or change the order in which rules are checked.

manage-rules opens a graphical rule manager; edit-rules opens the rule file in your text editor. Both take a rule profile name. For example, anyevent-mcp manage-rules fs-default manages the default filesystem server's rules. The corresponding *-file commands accept a pathname when an application stores its rules elsewhere.

init ensures the private global configuration contains a persistent master secret, from which servers derive their connection credentials. You normally do not need to run it: servers initialize their global configuration automatically. Repeating init leaves an existing secret unchanged.

See AnyEvent::MCP::Intro for setting up and connecting to the servers, "GLOBAL CONFIGURATION" in AnyEvent::MCP for the configuration file format, and "RULE FILES" in AnyEvent::MCP::Server::Permissions for permission rules.

COMMANDS

init

Ensure that the private global configuration and master secret exist. An existing secret is preserved; missing secrets are generated and saved. --config FILE selects a different configuration file for this command.

manage-rules NAME

Open the YAD rule deletion and reordering interface for the named profile. For a filesystem server started with --name code, use profile fs-code.

edit-rules NAME

Open the named profile's rule file in a text editor.

manage-rules-file $file

Open the rule manager for the explicit pathname $file.

edit-rules-file $file

Open $file in a text editor. Use these explicit-file commands for applications whose rule files do not use the named-profile convention.

create-user USER

Enable a new named user; rotate a revoked user at the next generation. Use --program or --instance for a scoped override.

revoke-user USER

Disable a user, preserving the generation for later rotation. In a narrower scope, a negative definition also blocks inherited credentials. Implicit global:default is revocable. Restart affected servers after changes; these commands do not print secrets. Use server --print-url[=USER] for URLs.

User commands rewrite the selected INI file in canonical form. Existing settings are retained, but comments and formatting are not preserved.

Named profiles use anyevent-mcp/rules/NAME.ini in the user configuration directory. Editing uses $VISUAL, $EDITOR, sensible-editor or vi. For server URLs, use each server's --print-url option.

OPTIONS

--config FILE

Use FILE instead of default global configuration ($XDG_CONFIG_HOME/anyevent-mcp/global.ini, or ~/.config/anyevent-mcp/global.ini). Relevant to init and user management; rule management uses its own profile or pathname.

--program NAME

Select [program NAME] for user management.

--instance NAME

Select [instance NAME] for user management. Cannot combine with --program.

--help

Print command synopsis, available commands and configuration defaults, then exit without running a command.