MCP Guardian

Created By
eqtylaba year ago
Manage / Proxy / Secure your MCP Servers
Overview

What is MCP Guardian?

MCP Guardian is a tool designed to manage, proxy, and secure access to your MCP servers, providing real-time control over your LLM assistant's activities.

How to use MCP Guardian?

To use MCP Guardian, follow the quick start guide for your operating system (Linux/macOS or Windows) to install necessary dependencies and build the project. Once set up, you can manage multiple MCP server configurations and monitor LLM activities.

Key features of MCP Guardian?

  • Message Logging: Trace all of an LLM's MCP server activity.
  • Message Approvals: Approve or deny individual tool call messages in real-time.
  • Automated Message Scans: Future feature for real-time automated checks for safety and privacy.
  • Multi-server Management: Easily switch between different MCP server configurations.

Use cases of MCP Guardian?

  1. Managing access to multiple LLMs across different MCP servers.
  2. Ensuring compliance and safety in LLM operations through message approvals.
  3. Monitoring LLM activities for auditing and debugging purposes.

FAQ from MCP Guardian?

  • What platforms does MCP Guardian support?

MCP Guardian supports Linux, macOS, and Windows.

  • Is there a graphical interface for MCP Guardian?

Currently, MCP Guardian operates through command-line interfaces, but a GUI may be considered in future updates.

  • How can I contribute to MCP Guardian?

Contributions are welcome! Please check the GitHub repository for guidelines.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
eqtylab
Star
47
Language
Rust
License
Apache-2.0 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
Crevio

2 days ago