Skip to content

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.

Terminal window
anycap mcp --help

If the command is missing, run anycap update.

Store the machine-specific absolute root in Claude’s local project scope:

Terminal window
claude mcp add --scope local anycap -- anycap mcp --allow-root "$PWD"

MCP startup never opens a browser. Existing CLI login is loaded automatically and credentials are refreshed on every tool call.

  1. Call anycap_auth_status.
  2. If unauthenticated, call anycap_login and show its verification URL and user code.
  3. After the human completes login, call anycap_login_poll with the returned session ID.
  4. Call anycap_status to verify the server and account.

Effective local file access is the union of:

  • repeatable --allow-root flags
  • 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.

See the MCP tool reference for all 23 tools and their current read/write boundaries.