Devart Mcp Server Access

Devart MCP Server for Microsoft Access

Devart MCP Server for Microsoft Access

Devart MCP Server for Microsoft Access enables AI clients to interact with your data through a secure server running in your environment. It turns a regular AI chat into a practical way to work with real-world business data — and it is faster than conventional export or manual querying.

Key benefits

Devart MCP Server for Microsoft Access allows you to:

• Work with data intuitively through natural language.
• Retrieve the required data for analysis within minutes.
• Generate reports faster with AI-powered assistance.
• Minimize manual data handling and integration maintenance.

How it works

Devart MCP Server for Microsoft Access helps AI clients communicate directly with Microsoft Access databases using natural-language prompts. It translates AI requests into structured queries, executes them through Devart connectivity drivers, and returns clean, structured results for seamless AI-powered data access.

Quick start

To get started with Devart MCP Server for Microsoft Access:

1. Download and install Devart ODBC Driver for Microsoft Access.

2. Download and install Devart MCP Server for Microsoft Access.

3. In Devart MCP Server for Microsoft Access, configure your data connection and integration settings.

4. Run your first natural-language query.

Need an MCP Server for multiple data sources?

Manual installation and configuration

Prerequisites

Before building and running Devart MCP Server for Microsoft Access, ensure the following components are installed:

• .NET 8 SDK
• ODBC connection — Devart.AI.McpServer.Odbc.Access.csproj Devart ODBC Driver for Microsoft Access (requires manual download and installation)

Step 1: Clone the repository

Clone the project repository and navigate to the project directory:

1. Open Command Prompt.

2. Enter the following command:

git clone https://github.com/devart-ai-connectivity/devart-mcp-server-access.git
cd devart-mcp-server-access

Step 2: Build the MCP Server from source

You can build Devart MCP Server for Microsoft Access from source using ODBC.

To build the MCP server with ODBC, select the command based on the bitness of your data source.

• For 64-bit data source, run the following command:

dotnet publish Devart.AI.McpServer.Odbc/Devart.AI.McpServer.Odbc.Access/Devart.AI.McpServer.Odbc.Access.csproj -c ReleaseAccess -r "win-x64" /p:TargetFramework=net8.0

• For 32-bit data source, run the following command:

dotnet publish Devart.AI.McpServer.Odbc/Devart.AI.McpServer.Odbc.Access/Devart.AI.McpServer.Odbc.Access.csproj -c ReleaseAccess -r "win-x86" /p:TargetFramework=net8.0

Note

The target platform must match the bitness of your ODBC data source.

Step 3: Configure the database connection for the MCP Server

1. Create an mcpserver.json configuration file in the directory containing the built MCP Server executable.

2. In the file, configure the database connection:

{
  "Connections": [
    {
      "Name": "my_access",
      "DsnName": "your_dsn_name",
      "ProtocolType": "stdio"
    }
  ]
}

Alternatively, you can configure the database connection using the connection string:

{
  "Connections": [
    {
      "Name": "my_access",
      "ConnectionString": "Driver={Devart ODBC Driver for Microsoft Access};Server=localhost;User ID=access;Password=your_password;Database=your_database;",
      "ProtocolType": "stdio"
    }
  ]
}

where:

• Name — The name of the ODBC connection.

• DsnName — The name of your data source.

• ProtocolType — A transport protocol. The possible options are: stdio or http.

• HttpPort (required if ProtocolType is set to http) — The port number for the http protocol.

Step 4: Run the MCP server

After you configure the MCP Server, you can start it.

Note

This step is required only when ProtocolType is configured as http. If you use the stdio transport protocol, your AI client starts the server automatically.

To start the server, run the following command:

Devart.AI.McpServer.Odbc.Access.exe run my_access

where my_access is the name of the ODBC connection.

Step 5: Integrate with Claude Desktop

1. Open claude_desktop_config.json, the Claude configuration file.

Tip

If you can't locate the configuration file, it may not exist yet. To create it, open Claude Desktop and navigate to File > Settings > Developer, then click Edit Config. The folder with the claude_desktop_config.json file opens.

2. Add one of the following objects, depending on the transport protocol used by MCP Server:

• STDIO

{
  "mcpServers": {
    "devart": {
      "command": "C:\\path\\to\\Devart.AI.McpServer.Odbc.Access.exe",
      "args": [
        "run",
        "my_access"
      ]
    }
  }
}

where:

• devart is the connector name that will appear in Claude Desktop.

• C:\\path\\to\\Devart.AI.McpServer.Odbc.Access.exe is the path to the executable file.

• my_access is the connection name specified in the mcpserver.json configuration file.

• HTTP

    "mcpServers": {
      "devart": {
        "command": "npx",
        "args": [
          "-y",
          "mcp-remote",
          "http://localhost:5000/sse"
        ]
      }
    }
  

  where:

  • devart is the connector name that will appear in Claude Desktop.
  • 5000 is the MCP Server listening port.

3. Save the file.

4. Restart Claude Desktop.

Devart MCP Server for Microsoft Access is now integrated with Claude, and devart appears in the Claude Desktop app in Customize > Connectors.

You can also integrate Devart MCP Server for Microsoft Access with other AI clients such as Cline, Codex, Cursor, Visual Studio Code, Windsurf, Zed.

Supported clients

Devart MCP Server for Microsoft Access supports integration with the following AI clients:

• Claude Desktop
• Visual Studio Code
• Cursor
• Codex
• Windsurf
• Cline
• Zed
• ...and other MCP-compatible AI clients

Typical use cases

Devart MCP Server for Microsoft Access is a practical fit for teams working with Microsoft Access as their primary data source.

• Small business data analysis
  Let small business owners and operations staff query customer records, order histories, and financial data stored in Access databases without learning SQL.

• Departmental reporting and analytics
  Access inventory, project tracking, HR, or budget data from departmental Access databases that have no dedicated reporting layer.

• Legacy data exploration
  Use AI to explore and document the contents of legacy Access databases before migration — understanding tables, relationships, and data quality.

• Migration planning and data assessment
  Analyze Access database structure and content to prepare for migration to a modern database platform, with AI assistance to speed up the assessment.

• Non-technical user self-service
  Enable team members without SQL knowledge to get answers from Access databases that historically required developer involvement.

• Secure local AI access to Access files
  Work with MDB and ACCDB files on local or network drives without uploading data to cloud services or external platforms.

Licensing and activation

Devart MCP Server for Microsoft Access is distributed as a free single-source MCP server.

To connect to Microsoft Access, the server requires the corresponding Devart ODBC Driver for Microsoft Access, which is a paid product.

A 30-day free trial is available for the Devart ODBC Driver for Microsoft Access.

See the product page and documentation for the latest installation and activation details.

Support

• Documentation
• Submit a request
• Suggest a feature
• Join our forum

Other Devart connectivity solutions

• MCP Server Universal
• ODBC Driver for Microsoft Access