Legion_mcp

Created By
TheRaLabsa year ago
Overview

What is Legion MCP?

Legion MCP (Model Context Protocol) Server is a server designed to facilitate access and querying of data in databases using the Legion Query Runner, integrated with the Model Context Protocol (MCP) Python SDK.

How to use Legion MCP?

To use Legion MCP, set up the server by installing dependencies, configuring your database connection, and running the server in either development or production mode. You can execute SQL queries and manage database operations through the MCP interface.

Key features of Legion MCP?

  • Database access via Legion Query Runner
  • Support for Model Context Protocol (MCP) for AI assistants
  • Exposes database operations as MCP resources, tools, and prompts
  • Multiple deployment options including standalone and FastAPI integration
  • Flexible configuration through environment variables and command-line arguments

Use cases of Legion MCP?

  1. Enabling AI assistants to perform database operations seamlessly.
  2. Providing a structured way to manage and query database schemas and metadata.
  3. Facilitating stateful interactions with databases for applications.

FAQ from Legion MCP?

  • What is the Model Context Protocol (MCP)?

MCP is a specification for maintaining context in AI applications, allowing for better interaction with databases.

  • How do I install Legion MCP?

You can install it using the uv dependency manager and follow the setup instructions provided in the documentation.

  • Can I run Legion MCP in production?

Yes, Legion MCP can be run in production mode with appropriate configurations.

Server Config

{
  "mcpServers": {
    "legion_mcp": {
      "command": "uv",
      "args": [
        "--directory",
        "/path/to/legion-mcp",
        "run",
        "mcp_server.py"
      ],
      "env": {
        "DB_TYPE": "pg",
        "DB_CONFIG": "{\"host\":\"localhost\",\"port\":5432,\"user\":\"username\",\"password\":\"password\",\"dbname\":\"database_name\"}"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
TheRaLabs
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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