🔍 Rust MCP Server + Inspector Example: SSE Transport with an Add Tool

Created By
RGGHa year ago
Rig MCP Server Example (April 7, 2025)
Overview

What is Rig MCP Server?

Rig MCP Server is a demonstration project that showcases how to set up a Model Context Protocol (MCP) server and client using Server-Sent Events (SSE) for communication. It includes a simple tool that adds two numbers and integrates with the RIG agent for LLM prompting.

How to use Rig MCP Server?

To use the Rig MCP Server, clone the repository and run the server using cargo run. In a separate terminal, start the MCP Inspector with the command npx @modelcontextprotocol/inspector sse http://127.0.0.1:3001/sse. You can then access the web interface at http://localhost:5173.

Key features of Rig MCP Server?

  • Sets up a custom MCP server using ServerSseTransport.
  • Connects a MCP client to the server.
  • Registers a custom tool: AddTool, which adds two numbers.
  • Lists registered tools via MCP.
  • Integrates with RIG and prompts an LLM agent using the tool.

Use cases of Rig MCP Server?

  1. Demonstrating the setup of an MCP server and client.
  2. Providing a simple tool for adding numbers.
  3. Integrating with LLM agents for enhanced functionality.

FAQ from Rig MCP Server?

  • What programming language is used for Rig MCP Server?

The project is developed in Rust.

  • How can I view the MCP Inspector UI?

You can view the MCP Inspector UI by visiting http://localhost:5173.

  • Is there a way to contribute to the project?

Yes! You can open an issue or start a discussion on the GitHub repository.

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

20 hours ago
Gpt Scrambler

2 days ago