Introduction

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is OpenLinkSoftware_mcp-odbc-server?

OpenLinkSoftware_mcp-odbc-server is a generic ODBC server designed for the Model Context Protocol (MCP), enabling Large Language Models to access ODBC-compatible data sources seamlessly.

How to use OpenLinkSoftware_mcp-odbc-server?

To use the mcp-odbc server, follow the installation steps to set up the environment, configure the ODBC connection, and utilize the provided tools to execute SQL queries and interact with the database.

Key features of OpenLinkSoftware_mcp-odbc-server?

  • Transparent access to ODBC data sources for Large Language Models.
  • Tools for listing schemas, tables, and executing SQL queries.
  • Support for various ODBC connectors and database management systems.

Use cases of OpenLinkSoftware_mcp-odbc-server?

  1. Integrating AI applications with existing databases.
  2. Executing complex SQL queries through a user-friendly interface.
  3. Facilitating data analysis and reporting using Large Language Models.

FAQ from OpenLinkSoftware_mcp-odbc-server?

  • What is required to run the mcp-odbc server?

You need Node.js, the MCP SDK, and the appropriate ODBC drivers installed on your system.

  • Can I use this server with any ODBC-compatible database?

Yes, the server is designed to work with any ODBC-compatible database, provided the correct drivers are installed.

  • Is there any support for troubleshooting?

Yes, the documentation includes troubleshooting steps and links to screencasts for visual guidance.

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
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)

2 days ago