Version: 1.0.2 Last Updated: 2025-10-09
- Installation & Setup
- Compatibility
- Usage & Features
- Troubleshooting
- Security & Safety
- Performance
- Advanced Topics
A: No, for most operations. The Access Database Engine is sufficient for:
- Connecting to databases
- Querying data (SELECT)
- Modifying data (INSERT, UPDATE, DELETE)
- Creating and modifying tables
- Managing relationships and indexes
You do need Microsoft Access installed for:
- VBA code manipulation (Phase 3 tools)
- Forms and reports automation (Phase 4 tools)
- Some advanced database administration tasks
A: We recommend Access Database Engine 2016 or later (64-bit) for full compatibility.
Compatibility:
- ✅ ACE 2016/2019/365: Full support, all database formats
⚠️ ACE 2010-2013: Limited support, some newer databases may fail- ❌ ACE 2007 or earlier: Not recommended
A: No. Access MCP Server is Windows-only because:
- Microsoft Access databases require the Access Database Engine (Windows-only)
- VBA and Forms/Reports require Access COM automation (Windows-only)
- The .NET implementation uses Windows-specific libraries
A: After installation:
- Open Claude Desktop
- Ask: "Are you connected to the Access MCP Server?"
- Claude should confirm connection and list available tools
You can also check:
- Settings → Developer → MCP Servers
- Look for "access-mcp-server" with "Connected" status
A: Try these steps:
- Make sure you have the 64-bit Access Database Engine installed
- Restart Claude Desktop completely (File → Exit, then reopen)
- Check Claude Desktop logs:
%APPDATA%\Claude\logs - Try manual installation (see packaging/README.md)
- Report the issue on GitHub
A: All Microsoft Access formats:
- ✅
.accdb(Access 2007-2019/365) - ✅
.mdb(Access 97-2003)
Both formats are fully supported for all operations.
A: No. Access MCP Server is specifically designed for Microsoft Access databases. For SQL Server, you would need a different MCP server.
A: Not currently. Password-protected Access databases are not supported in v1.0.2. This feature may be added in a future release.
A: Your database was created with a newer version of Access than your installed Access Database Engine supports.
Solutions:
- Upgrade your Access Database Engine to 2016 or later
- Or open the database in Access and save it in an older format
The server automatically detects version compatibility and will provide clear error messages.
A: No. This server works with local Access database files (.accdb/.mdb) only. Web apps and SharePoint lists are not supported.
A: Multiple! You can connect to several databases simultaneously. Each connection gets a unique key. Ask Claude to "list all active database connections" to see them.
A: Yes! You don't need to know SQL. Just describe what you want in natural language, and Claude will generate and execute the appropriate SQL queries.
Example:
Show me customers from California who placed orders in 2024
Claude handles the SQL behind the scenes.
A: Tools are organized into 5 phases:
- Phase 1 (15 tools): Core data operations - connecting, querying, basic CRUD
- Phase 2 (10 tools): Schema management - creating/modifying tables, relationships, indexes
- Phase 3 (10 tools): VBA manipulation - reading/writing Visual Basic code
- Phase 4 (8 tools): Forms & reports - inspecting and exporting UI objects
- Phase 5 (7 tools): Database administration - backup, compact, analyze, split
See TOOLS_REFERENCE.md for complete details.
A: Not automatically. Access databases don't have built-in undo. Best practices:
-
Always backup first:
Create a backup before we make changes -
Use transactions for multiple operations:
Do these changes as a transaction so we can roll back if needed -
Test on a copy:
- Make a copy of your database
- Test changes on the copy
- Apply to original once verified
A: Ask Claude:
Show me the SQL query you're about to run
Or after executing:
What SQL did you just execute?
Claude can explain the queries being generated.
A: Not directly through the MCP server. However, you could:
- Use Windows Task Scheduler to run Claude Desktop with specific prompts
- Use the server programmatically (requires development knowledge)
- Manually run maintenance tasks periodically
A: The Access Database Engine is not installed or not detectable.
Fix:
- Download from: https://www.microsoft.com/download/details.aspx?id=54920
- Install the 64-bit version
- Restart Claude Desktop
- Try connecting again
A: The database file is already open somewhere else.
Fix:
- Close Microsoft Access if it's open with this database
- Close any other programs using the database
- Check for
.laccdbor.ldblock files next to your database - delete them if present - Restart your computer if the lock persists
A: Several possible causes:
Network databases:
- Check network connectivity
- Ensure network drive is mapped and accessible
- Use local databases when possible for stability
Database issues:
- Database file may be corrupted - try compact & repair
- Database may be too large - consider splitting it
Server issues:
- Restart Claude Desktop
- Check Claude Desktop logs for errors
A: VBA project access is not enabled.
Fix:
- Open Microsoft Access
- File → Options → Trust Center → Trust Center Settings
- Macro Settings → Enable "Trust access to the VBA project object model"
- Click OK
Security warning: Only enable this on development machines. See ENABLING_VBA_TESTS.md for details.
A: Several factors affect performance:
Database factors:
- Large databases take longer
- Databases on network drives are slower
- Fragmented databases need compacting
Query factors:
- Complex queries take longer
- Missing indexes slow down searches
- Large result sets take time to transfer
Improvements:
Compact my database to improve performance
Create an index on [frequently-searched-column]
A: You don't have write permissions to the database file.
Fix:
- Check file properties - ensure you have write access
- If on a network drive, check network permissions
- Run Claude Desktop as administrator (not recommended as standard practice)
- Move database to a folder where you have full permissions
A: Yes, with normal precautions:
What the server can do:
- Read and modify data in connected databases
- Create and modify database structure
- Execute any SQL you approve through Claude
What the server cannot do:
- Access databases you haven't explicitly connected to
- Run operations without your approval (via Claude)
- Access other files on your computer
- Connect to remote databases without credentials
Best practices:
- Always backup before significant changes
- Use on copies of production databases when testing
- Review changes before confirming deletions
- Disconnect when not in use
A: Claude processes your requests through Anthropic's servers, so database queries and results pass through Anthropic's systems following their privacy policy.
The MCP server itself:
- Runs locally on your computer
- Only accesses databases you explicitly connect to
- Doesn't send data anywhere except to Claude (via the MCP protocol)
For sensitive data:
- Use on non-production copies
- Avoid querying highly sensitive information
- Review Anthropic's data policies
A: No. The MCP server:
- Only runs on your local computer
- Only you can use it through your Claude Desktop
- No remote access or network exposure
- No web interface or API endpoints
A: Unfortunately, Access doesn't have transaction logs for recovery. Prevention is key:
- Always backup: Before any delete operations
- Preview first: Ask Claude "what would be deleted?" before confirming
- Use WHERE clauses carefully: Be specific about what to delete
- Test on copies: Practice on a database copy first
If data is lost:
- Restore from your backup
- Check if you have shadow copies (Windows Previous Versions)
- Consider data recovery tools (may not work with Access)
A: Typical performance:
- Connection: < 1 second
- Simple queries: 100-500ms
- Complex queries: 1-5 seconds
- Schema modifications: 500ms - 2 seconds
- Large operations: Depends on data size
Factors:
- Database size and complexity
- Network vs local database
- Available system resources
- Query complexity
A: Yes, but with considerations:
Access limitations:
- Maximum file size: 2GB
- If your database is approaching 2GB, consider splitting it
Server performance:
- Large databases work fine
- Operations may take longer
- Network databases especially affected
Recommendations:
- Keep databases compacted
- Create appropriate indexes
- Split into frontend/backend if needed
A: The server has no hard limit, but practical limits exist:
Recommended:
- Query result sets: < 10,000 records for display
- Use LIMIT/TOP clauses for large tables
- Use COUNT for totals instead of fetching all records
Example:
Show me the first 100 customers
How many total customers are there?
Instead of:
Show me all customers (might be 100,000+ records!)
A: The MCP server is designed for use with Claude Desktop, but:
Possible uses:
- Any MCP-compatible client can connect
- Could be used programmatically with MCP SDK
- Could be extended with additional tools
License: MIT License - see LICENSE for terms
A: Yes! Contributions are welcome. See CONTRIBUTING.md for:
- How to set up development environment
- Coding standards and guidelines
- Pull request process
- Feature request procedures
A: See docs/MCPB_PACKAGING.md for creating .mcpb bundles.
For team deployment:
- Create a custom
.mcpbbundle - Distribute to team members
- Each installs in their Claude Desktop
- Consider creating shared documentation for your specific use cases
A: Yes, if you're comfortable with C# and .NET development:
- Clone the repository
- Modify the tool implementations
- Build your custom version
- Package and distribute
See .claude/project specification.md for architecture details.
A: Yes, for most operations. Access Runtime provides the database engine needed for core operations.
Limitations with Runtime:
- No UI for design changes (but tools work)
- Some VBA restrictions may apply
- Forms/Reports tools may have limitations
A: Yes, Access MCP Server works on:
- Windows Server 2016 or later
- Requires Desktop Experience (GUI)
- Same prerequisites as Windows 10/11
Not supported:
- Windows Server Core (no GUI)
- Remote Desktop sessions may have limitations
A: See ROADMAP.md for:
- Current project status
- Planned features
- Technical debt
- Community requests
Potential future features:
- Password-protected database support
- Export to other formats (Excel, CSV)
- Advanced reporting capabilities
- Performance monitoring tools
- User Guide - Complete usage guide
- Tutorial - Hands-on walkthrough
- Tools Reference - All 50 tools documented
- Navigation Guide - Find any documentation quickly
- GitHub Issues - Report bugs, request features
- Bug Remediation Plan - Known issues and fixes
- GitHub Discussions (coming soon)
- Share your use cases and examples
- Help other users
Have a question not answered here?
Open an issue on GitHub and tag it with "question" - we'll add it to this FAQ!
Last Updated: 2025-10-09 Version: 1.0.2 Questions Answered: 50+