mcp-tools

MCP Tools provides a collection of capabilities that conform to the Model Context Protocol, exposing a range of tools that an LLM can invoke to interact with the outside world. The available tools cover common system operations (bash, cat, grep, sed), environment and file management (file_system), networking and HTTP requests (curl), container and cloud-oriented tasks (docker), and software development workflows (git, github_issues, github_pull_requests, github_repository, github_search). There are also data interaction tools like postgresql and weather (get_weather), as well as email (gmail). Each tool is designed to be invoked through the MCP interface with a defined input schema, enabling secure and structured interactions between the LLM and external services. To use the package, request the MCP Kit or your MCP client to load the tools provided by mcp-tools and pass tool definitions and parameters per the MCP Tools documentation. The tool list includes common operations such as executing shell commands, reading files, making HTTP requests, manipulating GitHub issues and PRs (when a GITHUB_TOKEN is provided), querying a PostgreSQL database, and retrieving weather data by location. Tools can be combined to perform complex automation and data retrieval tasks within a single MCP session.

Prerequisites:

• Node.js and npm installed on your system (or a Node.js-compatible runtime that can run npx).

Install and run:

1. Ensure Node.js and npm are up to date.
   • On macOS/Linux: curl -fsSL https://deb.nodesource.com/setup_current.x | bash - sudo apt-get install -y nodejs
   • On Windows, install from https://nodejs.org/
2. Verify installation:
   • node -v
   • npm -v
3. Run the MCP Tools server (no global install required thanks to npx):
   • npx -y mcp-tools

Optional: If your environment requires authentication for specific tools (e.g., GitHub or Gmail), prepare the necessary tokens or credentials as environment variables (see additional notes). For example, to enable GitHub-based tools, set GITHUB_TOKEN in your environment before starting the MCP Tools session.

Environment variables and configuration options:

• GITHUB_TOKEN: Required for github_* tools (issues, pull requests, repository, search). Ensure this token has the necessary scopes for the operations you intend to perform.
• Any other service-specific credentials (e.g., Gmail access for gmail tool) should be provided as environment variables or through your MCP client’s secure secrets management.

Common issues:

• If npx fails due to network restrictions, consider installing the package locally or using an alternative runner compatible with the MCP Tools distribution.
• Some tools may require network access or specific system permissions (e.g., executing shell commands or reading/writing files). Ensure the environment running the MCP server has the necessary permissions.
• When using github_* tools, ensure the GITHUB_TOKEN has the correct scopes (repo, read:user, etc.) for the requested actions.

Configuration tips:

• Use descriptive tool input schemas to validate parameters before invoking tools to avoid runtime errors.
• Combine multiple tools to implement complex workflows, such as fetching data via curl, processing it with grep/sed, and then storing results with file_system or inserting into a PostgreSQL database.