SurrealDB MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is SurrealDB MCP Server?

SurrealDB MCP Server is a Model Context Protocol (MCP) server that provides a standardized interface for AI assistants to interact with a SurrealDB database, enabling them to query and manipulate data within a configured SurrealDB instance.

How to use SurrealDB MCP Server?

To use the SurrealDB MCP Server, install it via npm and configure it according to the AI assistant you are using (e.g., Cline, Claude, GitHub Copilot). Follow the installation guide specific to your assistant to set up the server and connect it to your SurrealDB instance.

Key features of SurrealDB MCP Server?

  • Standardized interface for AI assistants to access SurrealDB.
  • Supports various operations like query, select, create, update, delete, and more.
  • Easy integration with popular AI assistants and tools.

Use cases of SurrealDB MCP Server?

  1. Enabling AI assistants to perform data operations on SurrealDB.
  2. Facilitating real-time data manipulation and querying for AI applications.
  3. Integrating with automation tools like n8n for enhanced workflows.

FAQ from SurrealDB MCP Server?

  • What is SurrealDB?

SurrealDB is a scalable, distributed, document-graph database with real-time capabilities.

  • How do I install the server?

You can install the server globally using npm with the command npm install -g surrealdb-mcp-server.

  • What environment variables are required?

You need to set SURREALDB_URL, SURREALDB_NS, SURREALDB_DB, SURREALDB_USER, and SURREALDB_PASS to connect to your SurrealDB instance.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
JavaScript
License
View license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago