Surreal Mcp

Created By
lfnovo10 months ago
Overview

What is Surreal Mcp?

Surreal Mcp is a Model Context Protocol (MCP) server that enables AI assistants to interact with SurrealDB databases, providing a standardized interface for database operations.

How to use Surreal Mcp?

To use Surreal Mcp, set up a SurrealDB instance and configure the server with the required environment variables. You can run the server using commands like uvx surreal-mcp or python -m surreal_mcp after installing the necessary dependencies.

Key features of Surreal Mcp?

  • Full SurrealQL support for executing complex queries.
  • Comprehensive CRUD operations for managing records.
  • Graph database operations for creating and traversing relationships.
  • Efficient bulk operations for multi-record inserts.
  • Smart updates and type-safe handling of SurrealDB's RecordIDs.
  • Connection pooling for efficient database management.

Use cases of Surreal Mcp?

  1. Integrating AI assistants with SurrealDB for data management.
  2. Executing complex queries and managing relationships in graph databases.
  3. Performing bulk data operations efficiently.

FAQ from Surreal Mcp?

  • What is required to run Surreal Mcp?

    You need Python 3.10 or higher and a running SurrealDB instance.

  • Can I use Surreal Mcp with any AI assistant?

    Yes, as long as the assistant is MCP-compatible.

  • Is there documentation available?

    Yes, extensive documentation is provided within the project for setup and usage.

Server Config

{
  "mcpServers": {
    "surrealdb": {
      "command": "uvx",
      "args": [
        "surreal-mcp"
      ],
      "env": {
        "SURREAL_URL": "ws://localhost:8000/rpc",
        "SURREAL_USER": "root",
        "SURREAL_PASSWORD": "root",
        "SURREAL_NAMESPACE": "test",
        "SURREAL_DATABASE": "test"
      }
    }
  }
}
Project Info
Created At
10 months ago
Updated At
10 months ago
Author Name
lfnovo
Star
-
Language
-
License
-

Recommend Servers

View All
Alloy

2 days 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)

8 hours ago
Crevio

a day ago