Protoc Gen Go Mcp

Created By
redpanda-dataa year ago
Go protobuf compiler extension to turn any gRPC service into an MCP server
Overview

What is Protoc Gen Go Mcp?

Protoc Gen Go Mcp is a Protocol Buffers compiler plugin that generates Model Context Protocol (MCP) servers for gRPC or ConnectRPC APIs, allowing seamless integration of gRPC services with MCP functionality.

How to use Protoc Gen Go Mcp?

To use Protoc Gen Go Mcp, add an entry to your buf.gen.yaml file to configure the plugin, generate the standard *.pb.go files, and then run buf generate to create the MCP server files.

Key features of Protoc Gen Go Mcp?

  • Auto-generates MCP handlers from .proto services.
  • Outputs JSON Schema for method inputs.
  • Integrates easily with gRPC or ConnectRPC servers/clients.
  • Supports integration with buf for streamlined workflows.

Use cases of Protoc Gen Go Mcp?

  1. Creating MCP servers for existing gRPC services.
  2. Simplifying the integration of gRPC APIs with JSON Schema.
  3. Facilitating the development of tools that leverage gRPC services as MCP tools.

FAQ from Protoc Gen Go Mcp?

  • What is MCP?

MCP stands for Model Context Protocol, which is a protocol for defining tools and services in a structured way.

  • Is Protoc Gen Go Mcp compatible with all gRPC services?

Yes, it is designed to work with any gRPC service that uses Protocol Buffers.

  • What are the limitations of Protoc Gen Go Mcp?

Currently, it does not support interceptors and has some limitations with tool name mangling for long RPC names.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
redpanda-data
Star
117
Language
Go
License
Apache-2.0 license
Tags

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)

a day ago