MCP Server for ArangoDB

Created By
ravenwitsa year ago
This is a TypeScript-based MCP server that provides database interaction capabilities through ArangoDB. It implements core database operations and allows seamless integration with ArangoDB through MCP tools. You can use it wih Claude app and also extension for VSCode that works with mcp like Cline!
Overview

What is MCP Server for ArangoDB?

MCP Server for ArangoDB is a TypeScript-based Model Context Protocol server that facilitates database interaction with ArangoDB, allowing for seamless integration and core database operations.

How to use MCP Server for ArangoDB?

To utilize the MCP Server, install the dependencies, build the server, and configure it with environment variables in your application. It can be integrated with tools like Claude and the VSCode extension Cline.

Key features of MCP Server for ArangoDB:

  • Execute AQL queries to interact with the database.
  • Insert, update, and remove documents from collections.
  • List all collections within the database.
  • Agnostic to database structure, supporting any valid ArangoDB document models.

Use cases of MCP Server for ArangoDB:

  1. Automating data manipulation in applications using ArangoDB.
  2. Querying and managing user data in web applications.
  3. Integrating with developer tools like VSCode for efficient data handling.

FAQ from MCP Server for ArangoDB:

  • What does MCP stand for?
    MCP stands for Model Context Protocol, which allows for structured data interaction.
  • Which database systems is this server compatible with?
    The server is specifically designed for use with ArangoDB.
  • Is there any GUI for managing my database?
    No, MCP Server is a backend solution without a graphical interface; interaction is done through AQL queries.
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ravenwits
Star
18
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago