MCP Server ODBC via SQLAlchemy

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is MCP Server ODBC via SQLAlchemy?

MCP Server ODBC via SQLAlchemy is a lightweight server designed for ODBC connections, built using FastAPI, pyodbc, and SQLAlchemy. It is compatible with Virtuoso DBMS and other databases that support SQLAlchemy.

How to use MCP Server ODBC via SQLAlchemy?

To use the MCP server, clone the repository, set up your ODBC Data Source Name (DSN), and configure your environment variables. You can then connect to various databases using the provided connection URLs.

Key features of MCP Server ODBC via SQLAlchemy?

  • Fetch and list all schema names from the connected database.
  • Retrieve table information for specific schemas.
  • Generate detailed descriptions of table structures.
  • Execute stored procedures and SQL queries with results in JSONL or Markdown formats.

Use cases of MCP Server ODBC via SQLAlchemy?

  1. Managing database schemas and tables.
  2. Executing complex SQL queries and retrieving structured results.
  3. Integrating with various database management systems using a unified interface.

FAQ from MCP Server ODBC via SQLAlchemy?

  • What databases are supported?

The server supports any DBMS that implements a SQLAlchemy provider, including Virtuoso, PostgreSQL, MySQL, and SQLite.

  • Is there a specific installation requirement?

Yes, you need to install the uv package and configure your ODBC DSN properly.

  • Can I execute stored procedures?

Yes, the server allows executing stored procedures, particularly with Virtuoso.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
Python
License
Apache-2.0 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