NAME

anyevent-mcp - initialize MCP configuration and manage permission rules

SYNOPSIS

anyevent-mcp init
anyevent-mcp manage-rules fs-default
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 creates the private global configuration and its master secret, from which servers can derive their connection credentials. You normally do not need to run it: a server creates a missing secret when it loads its configuration. Use init when you want to create the configuration explicitly; it refuses to overwrite an existing file.

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

Create the private global configuration and master secret. Unlike ordinary configuration loading, this fails rather than overwriting an existing file. --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.

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