DBtoolReader

Created By
JavaPanda30a year ago
Overview

what is DBtoolReader?

DBtoolReader is a PostgreSQL database tool that provides a server interface for executing database queries and retrieving schema information. It is built using Go and integrates with the MCP (Model-Controller-Protocol) server framework, making it usable with any LLM and LLM System.

how to use DBtoolReader?

To use DBtoolReader, clone the repository, install the dependencies, build the project, and run the server. You can then execute queries and retrieve schema information through standard input/output.

key features of DBtoolReader?

  • Execute PostgreSQL database queries
  • Retrieve database schema information
  • Stdio-based server interface
  • Built on the MCP-Go framework

use cases of DBtoolReader?

  1. Executing complex SQL queries against a PostgreSQL database.
  2. Retrieving and displaying database schema information for analysis.
  3. Integrating with other tools and services that require database access.

FAQ from DBtoolReader?

  • What are the prerequisites for using DBtoolReader?

You need Go 1.16 or higher, a PostgreSQL database, and access credentials for your PostgreSQL database.

  • How do I run the server?

You can run the server by executing ./dbtoolreader after building the project.

  • Can I contribute to DBtoolReader?

Yes! Contributions are welcome, and you can submit a Pull Request.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
JavaPanda30
Star
0
Language
Go
License
-

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