← Back to directory
A

ArcadeDB MCP Server

Official
Built-in MCP server for ArcadeDB multi-model database
GitHub source repository ↗
★ 1.1k Stars Category · Database Very popular Source revision 9c9d024dbc9a
37FMRS · D
Reliability
4/20
Security and permissions
5/20
Maintenance
15/20
Documentation
7/20
Setup experience
6/20

ArcadeDB MCP Server is a built-in database MCP server suitable for AI applications needing integration with a multi-model database. It offers comprehensive data model support but requires users to have basic knowledge of ArcadeDB. Setup requires Docker and appropriate client configuration.

Read the FMRS scoring method →

ArcadeDB is a high-performance multi-model DBMS supporting graph, document, key-value, search engine, time-series, and vector embeddings. This MCP server is a built-in component of ArcadeDB, enabling AI assistants and LLMs to interact with ArcadeDB via the Model Context Protocol (MCP) for querying and managing databases. It is licensed under Apache 2.0 and maintained by the ArcadeDB team.

Tools

The tool list has not been reviewed yet.

Setup

  1. Ensure Docker is installed and running.
  2. Use Docker to run the ArcadeDB MCP server image: docker run --rm -p 2480:2480 -p 2424:2424 arcadedata/arcadedb:26.3.1 (note: this starts the ArcadeDB server; the MCP server is built-in).
  3. Configure the MCP client to use stdio transport. Since no specific client config example is provided, refer to the MCP client documentation; typically you need to specify the command as docker run with appropriate arguments.

Fit and risk

Best for

  • AI integrations needing multi-model data support
  • Developers who want to query and manage databases directly from AI assistants
  • Applications using ArcadeDB as their backend database

Not for

  • Users who don't need database functionality
  • MCP clients that require non-stdio transports (e.g., SSE or HTTP)
  • Users not interested in ArcadeDB itself and just want a generic database MCP

Required permissions

  • Database read and write access
  • Create and manage databases, indexes, and schemas
  • Execute queries and manage data models

Risks and side effects

  • Potential exposure of sensitive data if misconfigured
  • Database operations could lead to data loss or corruption; handle with care
  • As a database server, ensure network access control and authentication mechanisms are in place

Troubleshooting

  1. Check if the Docker container is running and ports are mapped correctly
  2. Ensure the client configuration correctly points to the MCP server
  3. Check ArcadeDB logs to diagnose connection or query issues
  4. Verify database credentials and permissions are set correctly

Use cases

AI assistant interaction with databases
LLM integration
Multi-model data management
Vector search and similarity retrieval

Supported clients

Claude DesktopFull support