run_ai_pack — Tetrees MCP MCP Tool Mutating
run_ai_pack
(run ai pack) is one of 26 tools on the
Tetrees MCP
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call run_ai_pack from your client
- Claude Code Tetrees MCP run_ai_pack run in your project directory
- Claude Desktop Tetrees MCP run_ai_pack ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Tetrees MCP run_ai_pack ~/.cursor/mcp.json
- VS Code Tetrees MCP run_ai_pack .vscode/mcp.json
- Zed Tetrees MCP run_ai_pack ~/.config/zed/settings.json
- Windsurf Tetrees MCP run_ai_pack ~/.codeium/windsurf/mcp_config.json
- Cline Tetrees MCP run_ai_pack ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Tetrees MCP run_ai_pack ~/.gemini/settings.json
- Grok Tetrees MCP run_ai_pack .mcp.json (in your project root)
- ChatGPT Tetrees MCP run_ai_pack Settings → Connectors → Advanced → Developer mode
- Claude.ai Tetrees MCP run_ai_pack Settings → Connectors → Add custom connector
- LangChain Tetrees MCP run_ai_pack pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://ex.tetrees.ai/mcpOther tools on this server
- accept_ai_pack_terms
- search_ai_packs
- list_owned_ai_packs
- acquire_free_ai_pack
- download_ai_pack
- get_ai_pack_report
- list_agent_models
- get_ai_pack_runtime_profile
- quote_agent_run
- prepare_local_ai_pack_run
- execute_client_extension
- propose_ai_pack_growth
- accept_ai_pack_growth
- list_ai_pack_growth
- select_ai_pack_growth_version
- create_ai_pack_draft
- update_ai_pack_draft
- upload_ai_pack
- upload_ai_pack_image
- get_ai_pack_submission_readiness
- submit_ai_pack_for_audition
- quote_ai_pack_audition
- run_ai_pack_audition
- get_ai_pack_private_report
- publish_ai_pack
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.