Hosting

Self-hosted ArcadeDB database with built-in MCP module; remote HTTP or local stdio transport.

Transport

Streamable HTTP at the database server MCP endpoint, or stdio via the bundled bin/mcp-stdio.sh launcher.

Endpoint

Local process; no hosted endpoint documented

Authentication

ArcadeDB account authentication is required. HTTP accepts Basic Auth or a bearer API token. Configure allowed users and MCP operation permissions in ArcadeDB Studio; do not use root credentials for a routine read-only integration.

Requirements

• Use ArcadeDB 26.8.1 or later because the official security advisory says the MCP authorization bypass was fixed in 26.8.1; the current product site documents release 26.10.2.
• Docker deployment uses the official arcadedata/arcadedb image; native installation requires Java 21 or later.
• The MCP module must be present/enabled in the ArcadeDB distribution. Binaries can be downloaded from official releases; custom builds select the mcp module.
• A database, user, and MCP permission profile are required. Default MCP access and tool inventory depend on server configuration and authenticated user permissions.

Setup steps

1. Install ArcadeDB 26.10.2 from the official release or run the official Docker image. Do not use the older 26.3.1 package listed in the MCP Registry; it predates the fixed release for the MCP authorization advisory.
2. Start the database and open ArcadeDB Studio at the server host and port (the documented local default is http://localhost:2480).
3. In Studio’s Server > MCP panel, enable the endpoint, set the allowed user list, choose the authentication method, and grant only the operations needed. For read-only use, enable reads and leave inserts, updates, deletes, schema changes, and admin operations disabled.
4. Configure the MCP client to use the Streamable HTTP endpoint http://localhost:2480/api/v1/mcp with an Authorization header using the selected Basic Auth credential or bearer API token. Studio’s MCP panel provides copyable client configuration. Keep credentials in the client’s secure local environment/configuration mechanism.
5. Reload the MCP client and confirm initialization and visible tools. The authoritative tool list depends on the installed version, tool profile, and permissions; inspect tools/list after connecting.
6. For Linux/macOS local stdio use, launch the installed distribution’s bin/mcp-stdio.sh. The documented launcher requires ARCADEDB_SETTINGS to include the server root password and starts ArcadeDB as the MCP child process. Do not use the root account for a network-accessible service.

The official reference documents the listed tool families/names but states that the available set is version-, profile-, and permission-dependent. No live tools/list request was performed; this is not an observed complete inventory.

• list_databases

  Lists databases accessible to the authenticated user.

  01
• get_schema

  Retrieves database types, properties, indexes, and inheritance.

  02
• query

  Executes a semantically checked read-only query against a database.

  03
• execute_command

  Runs database commands subject to configured write and schema permissions.

  04
• server_status

  Reports ArcadeDB server status.

  05
• sample_records

  Samples records from a database type.

  06
• vector_search

  Searches configured vector indexes.

  07
• full_text_search

  Searches full-text indexes.

  08
• hybrid_search

  Combines vector and full-text retrieval.

  09
• upsert_entity

  Creates or updates a graph entity.

  10
• upsert_relationship

  Creates or updates a graph relationship.

  11
• profiler_start

  Starts the server query profiler.

  12
• profiler_stop

  Stops the query profiler and returns captured results.

  13
• profiler_status

  Reads profiler state and recent results.

  14
• get_server_settings

  Reads server-level settings.

  15
• set_server_setting

  Changes a server setting; requires admin permission.

  16

This server’s available tools can vary by account, permissions, or configuration. The list shown is not its full runtime catalog.

• Documentation verified only; no MCP initialization, tools/list, or representative tool call was performed.
• The MCP endpoint can expose data writes and server administration if permissions allow. Enable only necessary operations; default the product setup guidance to read-only permissions.
• Do not expose an unauthenticated or broadly privileged MCP endpoint to an untrusted network.
• The MCP Registry server.json package identifier currently lists OCI version 26.3.1, which conflicts with the current official product site release and falls below the 26.8.1 security fix.

• The official MCP Registry manifest lists docker.io/arcadedata/arcadedb:26.3.1, while the current official product site documents 26.10.2 and an official advisory identifies 26.8.1 as the patched version for an MCP authorization issue. Use current 26.10.2 guidance and do not recommend the stale manifest version.

• official vendor documentation

  ArcadeDB MCP tool availability depends on version and tool profile; HTTP/stdio and authentication documented.

• official tool inventory

  Vendor inventory for current release; runtime tools/list remains authoritative.

Documentation checked 2026-10-28T00:00:00Z. Connection has not been runtime tested.