Labsco
MCP SERVER

Microsoft Access Database

by scanzy

Read and change a Microsoft Access or SQLite database, and move data in and out of it as CSV or Excel.

Relational SQL Databases
Summary
Legacy Access files, opened up to a conversation.

Access databases are usually where data goes to become unreachable. This reaches them with ordinary SQL, moves rows in and out through CSV and Excel, and lets you leave notes on a file so the next person does not have to guess at the schema.

What it is

An MCP server for Microsoft Access (.mdb, .accdb) and SQLite 3 (.db, .sqlite, .sqlite3) files. It opens a database file - or an in-memory one - runs SQL against it for reads and writes, imports and exports CSV, imports from Excel, and keeps human-readable notes alongside a file so the next session knows what is in it.

What you get
  • CSV imported into a database table
  • A table exported to CSV
  • An Excel sheet imported into a table
  • Notes written about a database file, or linked to it
  • Those notes read back, or discovered across a directory
  • SQL run against Access and SQLite alike, for both retrieval and updates
  • Databases opened read-only when you want them safe, or in memory when you want them temporary
Requirements

Uv, with fastmcp, pandas, sqlalchemy-access and openpyxl pulled in on the command line; the repository is cloned rather than installed from a package index. The server can read and modify any data in a database it connects to, so open with readOnly=true unless you mean to write - note that read-only is not available for in-memory SQLite. Excel import works; Excel export is not implemented.

Setup effort

Build from source — clone the repository and build it, then point your client at the binary