Neo4j MCP Server

Created By
Tobarrientos2a year ago
A Neo4j MCP server implementation for managing graph database operations through the Model Context Protocol
Overview

what is Neo4j MCP Server?

Neo4j MCP Server is an implementation designed to manage graph database operations through the Model Context Protocol, allowing seamless interaction with Neo4j databases.

how to use Neo4j MCP Server?

To use the Neo4j MCP Server, you can run it directly using npx with your Neo4j connection details or install it globally via npm. Configuration can be done through environment variables or a .env file.

key features of Neo4j MCP Server?

  • Supports both single connection strings and separate environment variables for configuration.
  • Compatible with Cursor and Claude Desktop for enhanced usability.
  • Allows execution of Cypher queries against the Neo4j database.

use cases of Neo4j MCP Server?

  1. Managing and querying graph databases efficiently.
  2. Integrating with development environments like Cursor for streamlined database operations.
  3. Facilitating the setup of Neo4j servers in various applications.

FAQ from Neo4j MCP Server?

  • Can I run Neo4j MCP Server without installing it globally?

Yes! You can run it directly using npx without global installation.

  • What should I do if I encounter issues?

Verify your Neo4j credentials, check for path issues, and ensure the server is running properly.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Tobarrientos2
Star
-
Language
-
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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)

a day ago