cli

MCPGod is a CLI tool designed to help you manage MCP servers with speed and ease. It provides commands to add, run, list, and remove MCP servers for different clients, discover tools on servers, and call specific tools directly from the command line. With MCPGod, you can also adjust permissions for tools on a per-client basis and review detailed logs of server runs to aid debugging. The CLI approach makes it straightforward to orchestrate multiple MCP servers across environments from a single interface.

You can install and run MCPGod globally, then use commands like add, list, run, tools, and tool to manage your MCP ecosystem. For example, you can attach a server to a client, view the available tools for a server, run a server with verbose logging, and invoke a tool with key-value parameters. The toolset is designed to work with common server implementations (as shown in the examples), and supports running servers written in Node.js or Python, or any tool that adheres to the MCP tooling interface.

Prerequisites:

• Node.js and npm installed on your system
• Internet access to install packages from npm

Step-by-step installation:

1. Install the MCPGod CLI globally using npm:

npm install -g mcpgod

2. Verify installation and version:

mcpgod --version

3. (Optional) Run directly with npx if you don’t want a global install:

npx -y mcpgod

4. If you’re contributing or developing locally, clone the repo and install dependencies:

git clone https://github.com/mcpgod/cli.git
cd mcpgod
npm install

5. Run in development mode (if you’re developing the CLI):

./bin/dev

Prerequisites recap:

• Node.js (recommended latest LTS)
• npm (comes with Node.js) or yarn if you prefer
• Access to npm registry to fetch mcpgod package

Tips and observations:

• The MCPGod CLI logs server runs to a dedicated log directory at ~/mcpgod/logs for traceability.
• You can use npx mcpgod to run the CLI without installing globally.
• This CLI is designed to manage MCP servers and their tools; if you’re integrating new server implementations, ensure they expose a compatible tooling interface that MCPGod expects.
• When scripting automated workflows, consider exporting environment variables as needed for authentication or configuration per client or per server.
• Common issues usually stem from misconfigured server references or tool permissions; use the mcpgod tools and mcpgod tool commands to enumerate and verify available tooling before invoking actions.
• If you modify repository code, follow the development steps in the README (clone, npm install, run in development mode) to validate changes locally.