arango

This MCP server implements the ArangoDB MCP protocol. It exposes tools to interact with an ArangoDB instance running locally (or at the specified URL) via a standardized set of resources and query helpers. The primary tools you’ll use are readQuery for read-only AQL, readWriteQuery for operations that modify data, listDatabases to enumerate databases, and listCollections to enumerate collections within a database. You configure the MCP server by starting the server through npx arango-mcp-server and pointing it at your ArangoDB instance (as shown in the example). Once running, you can access the provided endpoints to perform the supported operations against the target ArangoDB instance.

Prerequisites:\n- Node.js and npm installed on your machine.\n- Access to an ArangoDB server (for example, localhost:8529). Ensure you have credentials with sufficient permissions.\n\nStep-by-step:\n1) Install dependencies and set up the development environment (if you’re running locally):\n\nsh\n# If you’re cloning the repository locally, install dependencies from the project root:\nnpm install\n\n\n2) Start the MCP server using npx (as shown in the README example):\n\nsh\n# Start the server pointing to your ArangoDB instance\nnpx -y arango-mcp-server http://localhost:8529 root root\n\n\n3) Verify the server is running by visiting the provided inspector UI (as per development notes), typically http://localhost:5173/ if the dev setup is used.\n\n4) If you’re contributing or developing locally, follow the project’s development steps (clone, install, setup dev environment, run watcher, etc.).

Notes and tips:\n- The server expects an ArangoDB instance accessible at the provided URL and credentials. Ensure network accessibility and that the credentials are correct.\n- The README mentions a dev UI at http://localhost:5173/; this is part of the development workflow to inspect the MCP server. Adjust routes or ports if your environment differs.\n- If you encounter authentication errors, verify that the username and password (e.g., root/root) are valid for the target ArangoDB.\n- When using npx, the server is installed on demand; for repeated usage, consider installing as a local dev dependency or publishing the npm package.\n- If you change database names or credentials, update the mcp_config command arguments accordingly.\n- The MCP tooling assumes a single ArangoDB instance per server; for multiple databases, you can still list databases and collections as needed using the provided tools.