agentic

agentic-mcp serves as a multi-provider gateway that wraps various AI model CLI tools (Claude, Codex, Gemini, Copilot, OpenCode) behind a single MCP server interface. This lets you query any configured provider individually or run parallel requests across multiple providers. Once configured, you can list available providers, ping them to check readiness, and use ask_<provider> commands to request outputs from specific models. The server also supports ask_all to compare responses side-by-side and provider_metrics to monitor usage and performance. guided setup and discovery prompts are included to help you add new providers by editing a providers.json file rather than modifying code. The README emphasizes a quick start: install or run via npx agentic-mcp setup --client claude-code to configure Claude Code, then verify with list_providers, ping_claude, and help_claude. This centralizes access to multiple AI providers through a consistent MCP CLI surface.

Prerequisites:\n- Node.js >= 22 (and npm) installed on the machine.\n- A writable working directory and network access to fetch packages.\n\nInstallation options:\n1) Run without global install (recommended):\n\nbash\nnpx agentic-mcp setup --client claude-code\n``\nThis installs and configures the MCP server for the Claude Code provider. You can then use commands like `agentic-mcp list_providers`, `agentic-mcp ping_claude`, and `agentic-mcp ask_claude "your prompt"`.\n\n2) Install globally and then configure:bash\nnpm install -g agentic-mcp\nagentic-mcp setup --client claude-code\n\nThis achieves the same configuration flow but via a global CLI installation.\n\n3) Alternative (if you prefer package management):\nbash\nnpm install -g agentic-mcp && agentic-mcp setup --client claude-code\n```\nAfter setup, the MCP server loads the configured providers from providers.json (default bundled or user-specified via --config or AGENTIC_MCP_CONFIG).\n\nNotes:\n- Ensure you are connected to the internet during installation so dependencies can be fetched.\n- The CLI supports non-interactive writes with --yes and can perform dry-runs with --dry-run.

Tips and caveats:\n- Node.js version: The project requires Node.js >= 22. Make sure your runtime matches this requirement.\n- Configuration source: Providers are defined in providers.json. You can override the default by setting AGENTIC_MCP_CONFIG or using --config. Changes are non-destructive by default (merge mode) and only update the agentic-mcp entry, with backup and atomic replace behavior.\n- Environment variables: AGENTIC_MCP_CONFIG can point to a providers.json file or content.\n- CLI capabilities: Use list_providers, ping_<provider>, help_<provider>, and provider_metrics to survey status and performance.\n- Non-default providers: To add a new provider, edit providers.json — no code changes required.\n- Troubleshooting: If setup fails, use --dry-run to preview changes, verify paths, and re-run with --yes after addressing errors.\n- CLI flags: Common options include --config, --model, --working-dir, --system-prompt, --auto-mode, --effort, --max-budget, --file, --providers, --async, and --session-id for advanced workflows.