CockroachDB MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is CockroachDB MCP Server?

CockroachDB MCP Server is a middleware component that connects to a CockroachDB instance, exposing database and table schemas as resources, and allowing users to run SQL queries and analyze them.

how to use CockroachDB MCP Server?

To use the CockroachDB MCP Server, clone the repository, install dependencies, build the project, and run the server with the appropriate database URL and optional auth token.

key features of CockroachDB MCP Server?

  • Exposes database and table schemas as resources.
  • Executes SQL queries with options for execution plan analysis.
  • Provides cluster metadata information.

use cases of CockroachDB MCP Server?

  1. Querying available databases in a CockroachDB instance.
  2. Retrieving table schemas for specific databases.
  3. Running and debugging SQL queries.

FAQ from CockroachDB MCP Server?

  • How do I install the CockroachDB MCP Server?

Clone the repository, install dependencies using pnpm, and build the project with tsc.

  • What is required to access cluster metadata?

An auth token is required to access cluster metadata resources.

  • Can I use this server with other applications?

Yes, it can be integrated with applications like Claude for Desktop and Cline.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
TypeScript
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.

a day ago