Grpcurl MCP Server

Interacts with gRPC services using the grpcurl command-line tool via Model Context Protocol. Exposed over MCP by the grpcurl mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

This project is an Model Context Protocol (MCP) server designed to interact with gRPC services using the grpcurl tool. It leverages the grpcurl command-line utility to perform various operations on gRPC services, such as invoking methods, listing services, and describing service details.

• Invoke gRPC Methods — Use reflection to invoke gRPC methods with custom headers and JSON payloads
• List gRPC Services — Retrieve a list of all available gRPC services on the target server
• Describe gRPC Services — Get detailed descriptions of gRPC services or message types

Its toolset

Everything the assistant can do here goes through one of these:

• invoke — Invoke a gRPC method using reflection
• Parameters — - method: Fully-qualified method name (e.g., package.Service/Method)
• request — JSON payload for the request
• headers — (Optional) JSON object for custom gRPC headers
• list — List all available gRPC services on the target server
• describe — Describe a gRPC service or message type
• Tools — The Tools tool exposed by this server

Configuration

You will need one environment variable: ADDRESS. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Go 1.23.0 or later - grpcurl tool installed on your system

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

When to reach for it

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Grpcurl's toolset — invoke, Parameters, request and 4 more — is a fair guide to whether it matches your workflow. It is maintained by wricardo; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the grpcurl mcp server does with a few real requests.