Connect AnyCap through MCP
AnyCap CLI v0.5.0 includes a local stdio MCP server with 23 typed tools. It runs inside the existing CLI binary and shares the same authentication, HTTP client, model discovery, and local media handling. It has been verified with MCP protocol version 2025-06-18.
Verify support
Section titled “Verify support”anycap mcp --helpIf the command is missing, run anycap update.
Configure a host
Section titled “Configure a host”Store the machine-specific absolute root in Claude’s local project scope:
claude mcp add --scope local anycap -- anycap mcp --allow-root "$PWD"The Codex CLI command installs a global server definition. Omit a fixed root and let each project session advertise its root or use the server working directory fallback:
codex mcp add anycap -- anycap mcp{ "mcpServers": { "anycap": { "type": "stdio", "command": "anycap", "args": ["mcp", "--allow-root", "/absolute/path/to/media"] } }}Authenticate inside MCP
Section titled “Authenticate inside MCP”MCP startup never opens a browser. Existing CLI login is loaded automatically and credentials are refreshed on every tool call.
- Call
anycap_auth_status. - If unauthenticated, call
anycap_loginand show its verification URL and user code. - After the human completes login, call
anycap_login_pollwith the returned session ID. - Call
anycap_statusto verify the server and account.
Authorize local files
Section titled “Authorize local files”Effective local file access is the union of:
- repeatable
--allow-rootflags - the platform path list in
ANYCAP_MCP_FILE_ROOTS - roots advertised by the MCP client
- the process working directory when no other roots are configured
Canonical checks reject path traversal, sibling-prefix confusion, and symlink escape. Keep roots as narrow as possible. HTTP(S) URLs and existing AnyCap upload references do not require local access.
Explore the tools
Section titled “Explore the tools”See the MCP tool reference for all 23 tools and their current read/write boundaries.