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
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago