tRPC <-> MCP

Created By
Jacsea year ago
Serve tRPC routes as an MCP server
Overview

what is tRPC <-> MCP?

tRPC <-> MCP is a tool that allows you to serve tRPC routes as an MCP (Model Context Protocol) server, enabling seamless integration between tRPC and MCP.

how to use tRPC <-> MCP?

To use tRPC <-> MCP, you need to initialize it in your TypeScript project, define your routes, and then serve them using the MCP server.

key features of tRPC <-> MCP?

  • Easy integration of tRPC routes with MCP.
  • Supports TypeScript for type safety.
  • Allows for custom metadata in routes.

use cases of tRPC <-> MCP?

  1. Building APIs that require both tRPC and MCP functionalities.
  2. Creating server applications that need to handle complex data interactions.
  3. Enabling real-time communication between different services using MCP.

FAQ from tRPC <-> MCP?

  • Can I use tRPC <-> MCP with any TypeScript project?

Yes! tRPC <-> MCP is designed to work with any TypeScript project that uses tRPC.

  • Is there any specific setup required?

You need to install the necessary packages and follow the initialization steps outlined in the documentation.

  • What are the benefits of using MCP with tRPC?

MCP provides a structured way to manage data interactions, making it easier to build scalable applications.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Jacse
Star
-
Language
-
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)

a day ago