What are the prerequisites for the server machine?
Python 3.x, git, `uv` (Python project manager), and `wgrib2` installed and accessible in the system’s PATH are required. Also, an MCP Client environment must be able to connect to this server.
@yskmasumoto
Basic information
An MCP server for executing wgrib2 commands from MCP Client. Designed with a simple approach where converted files are saved to a specific folder.
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"wgrib2-easy-mcp": {
"command": "uv",
"args": [
"pip",
"install",
"-r",
"requirements.txt"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
A simple MCP server designed to execute wgrib2 commands remotely via an MCP Client. Processed files are saved to a designated output directory. It is intended for users who need to interact with GRIB2 meteorological data files through a remote client interface.
Clone the repository, install dependencies with uv pip install -r requirements.txt, and configure environment variables—notably the required OUTPUT_DIR (must exist before starting). Start the server with uv run --with python-dotenv --with mcp src/server.py. Connect your MCP Client and invoke the available tools, providing the path to a GRIB2 file. A sample script (src/sample/sample.py) demonstrates usage patterns.
Python 3.x, git, `uv` (Python project manager), and `wgrib2` installed and accessible in the system’s PATH are required. Also, an MCP Client environment must be able to connect to this server.
Set the environment variable `OUTPUT_DIR` to an absolute path (the directory must exist before starting the server). Optionally set `WGRIB2_PATH` (defaults to `wgrib2` in PATH) and `TEST_GRIB2_FILE` for the sample script.
Three stable MCP tools: `list_contents` (lists inventory), `show_details` (displays message details), and `show_help` (provides wgrib2 help documentation).
No. Element extraction and conversions to CSV/binary are currently under development and are only demonstrated in the sample script for illustration. Stable tools for these operations are not yet provided.
All generated files (e.g., CSV, binary extracts) are saved directly into the directory specified by the `OUTPUT_DIR` environment variable on the server machine. This directory must exist before launching the server.
MCP server that exposes a V8 JavaScript runtime as a tool for AI agents like Claude and Cursor. Supports persistent heap snapshots via S3 or local filesystem, and is ready for integration with modern AI development environments.
📄 The PDF intelligence layer for AI agents — Agent Document Twin, evidence-first extraction, visual crops, OCR provenance, trust reports, and benchmark-gated releases. MCP server for Claude, Cursor, VS Code, and any MCP client.
A Model Context Protocol (MCP) server that provides file system context to Large Language Models (LLMs). This server enables LLMs to read, search, and analyze code files with advanced caching and real-time file watching capabilities.
MCP Workspace Server: A secure Model Context Protocol server providing file, git, and GitHub tools for AI assistants within a sandboxed project directory.
Comments