MCP Grpcurl

Created By
wricardoa year ago
Model Context Protocol (MCP) server to interact with gRPC services using the grpcurl tool
Overview

what is MCP Grpcurl?

MCP Grpcurl is a Model Context Protocol (MCP) server designed to interact with gRPC services using the grpcurl tool, allowing users to perform various operations on gRPC services.

how to use MCP Grpcurl?

To use MCP Grpcurl, install the grpcurl tool, set up the MCP server, and run the server to invoke methods, list services, or describe service details.

key features of MCP Grpcurl?

  • Invoke gRPC methods with custom headers and JSON payloads.
  • List all available gRPC services on the target server.
  • Describe gRPC services or message types in detail.

use cases of MCP Grpcurl?

  1. Testing and debugging gRPC services.
  2. Interacting with gRPC APIs in a development environment.
  3. Automating gRPC service interactions in CI/CD pipelines.

FAQ from MCP Grpcurl?

  • What are the requirements to use MCP Grpcurl?

You need Go 1.23.0 or later and the grpcurl tool installed on your system.

  • How do I install grpcurl?

You can install grpcurl by following the instructions on its GitHub page: https://github.com/fullstorydev/grpcurl.

  • Can I use MCP Grpcurl for production services?

While MCP Grpcurl is primarily designed for development and testing, it can be adapted for production use with proper configuration.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
wricardo
Star
0
Language
Go
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago