Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings
/cliPublic

Fine-grained control over model context protocol (MCP) clients, servers, and tools. Context is God.

License

NotificationsYou must be signed in to change notification settings

mcpgod/cli

Repository files navigation

Fine-grained control over model context protocol (MCP) clients, servers, and tools. Context is God.

oclifVersionDownloads/weekLicenseCoverage

Overview

MCPGod is a CLI tool designed to help developers manage MCP servers with speed and ease. Whether you need to add, run, list, or remove servers—or even interact with server tools—MCPGod provides a streamlined interface to handle all these tasks on Windows, macOS, or Linux.

Features

  • Client Management
    Add, remove, and list MCP servers for specific clients.
  • Tool DiscoveryList every tool on any MCP server.
  • Tool CallingRun any tool on any MCP server directly from the command line.
  • Tool/Client PermissionsAllow or block specific tools for specific clients.
  • Detailed LoggingLog every server run from every client, with timestamps and clean output for easy debugging.

Installation

Installmcpgod globally usingnpm:

npm install -g mcpgod

Verify the installation:

mcpgod --version

Or run directly withnpx.

npx -y mcpgod

Usage

Access the CLI with themcpgod command (ornpx -y mcpgod). Below are some common examples:

  • Add a Server to a Client

    Add an MCP server to a client (e.g., Claude) withmcpgod add <SERVER> -c <CLIENT>:

    mcpgod add @modelcontextprotocol/server-everything -c claude
  • Only Add Specific Tools to a Client

    Only add specific tools to a client withmcpgod add <SERVER> -c <CLIENT> --tools=<COMMA_DELIMITED_LIST>:

    mcpgod add @modelcontextprotocol/server-everything -c claude --tools=echo,add
  • List Servers for a Client

    List all configured servers for a specific client withmcpgod list -c <CLIENT>:

    mcpgod list -c claude
  • Remove a Server

    Remove an MCP server from your client's configuration withmcpgod remove <SERVER> -c <CLIENT>:

    mcpgod remove @modelcontextprotocol/server-everything -c claude
  • Run a Server

    Run a server process with detailed logging withmcpgod run <SERVER>:

    mcpgod run @modelcontextprotocol/server-everythingmcpgod run ./mcp-server.pymcpgod run ./mcp-server-node.mjs
  • List Available Tools for a Server

    Display the list of tools available on a server withmcpgod tools <SERVER>:

    mcpgod tools @modelcontextprotocol/server-everythingmcpgod tools ./mcp-server.pymcpgod tools ./mcp-server-node.mjs
  • Call a Specific Tool on a Server

    Interact with a tool by passing key-value properties withmcpgod tool <SERVER> <TOOL> [optional parameters]:

    mcpgod tool @modelcontextprotocol/server-everything add a=59 b=40mcpgod tool ./mcp-server.pyecho message=himcpgod tool ./mcp-server-node.mjsecho message=hi

For a complete list of commands and options, simply run:

mcpgod --help

Logging

When running a server,mcpgod logs output to:

~/mcpgod/logs

Each log file is organized by server name and timestamped to help you trace and debug any issues that arise.

Development

mcpgod is built with theOclif framework and uses theModel Context Protocol SDK for robust interactions with MCP servers.

Clone the repository to get started with development:

git clone https://github.com/mcpgod/cli.gitcd mcpgodnpm install

Run the CLI in development mode:

./bin/dev

Publishing

Automatic publishing is handled by theversion, tag and github release workflow. A new npm version is published whenever a version bump is merged into themain branch. The workflow can also be triggered manually from theActions tab.

To enable publishing, set the following repository secrets:

  • NPM_TOKEN – authentication token for npm.
  • GH_EMAIL andGH_USERNAME – used by the README update step.

Once the secrets are configured, pushing a new version or running the workflow manually will build the project, create a GitHub release and publish the package to npm.

Linting workflows

Before committing changes to workflows, you can lint them locally:

npm run lint:workflows

Contributing

Contributions are always welcome! To contribute:

  1. Fork the repository.
  2. Create a branch:
    git checkout -b feature/your-feature
  3. Make your changes, and commit them:
    git commit -am'Add new feature'
  4. Push your branch:
    git push origin feature/your-feature
  5. Open a Pull Request on GitHub.

License

This project is licensed under theMIT License.


Additional Resources


About

Fine-grained control over model context protocol (MCP) clients, servers, and tools. Context is God.

Topics

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Contributors3

  •  
  •  
  •  

[8]ページ先頭

©2009-2025 Movatter.jp