Database Gateway

Created By
centralminda year ago
Universal MCP-Server for your Databases optimized for LLMs and AI-Agents.
Overview

What is CentralMind Gateway?

CentralMind Gateway is an open-source tool designed to generate secure, AI-optimized APIs from your structured databases, ensuring compliance with data protection regulations.

How to use CentralMind Gateway?

To use CentralMind Gateway, connect it to your structured database, configure the connection settings, and run the discovery command to generate the API configuration. You can then deploy the API using various options like Docker or standalone binaries.

Key features of CentralMind Gateway?

  • Automatic API generation based on database schema and data samples.
  • Support for multiple databases including PostgreSQL, MySQL, and Snowflake.
  • Built-in PII protection and compliance features.
  • Auto-generated API documentation with Swagger and OpenAPI specifications.
  • Flexible deployment options including Docker and Kubernetes.

Use cases of CentralMind Gateway?

  1. Enabling secure access to customer data for AI-driven applications.
  2. Generating APIs for analytics tools without exposing direct database access.
  3. Supporting AI models in customer support scenarios with optimized data access.

FAQ from CentralMind Gateway?

  • Can CentralMind Gateway handle all types of databases?

Currently, it supports PostgreSQL, MySQL, ClickHouse, and Snowflake, with plans for more integrations.

  • Is there a cost associated with using CentralMind Gateway?

No, CentralMind Gateway is open-source and free to use.

  • How does CentralMind Gateway ensure data security?

It filters out PII and sensitive data, ensuring compliance with GDPR and other regulations.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
centralmind
Star
368
Language
Go
License
Apache-2.0 license
Category

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