MCP Neo4j Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is MCP Neo4j Server?

MCP Neo4j Server is an integration tool that connects the Neo4j graph database with Claude Desktop, allowing users to perform graph database operations using natural language commands.

how to use MCP Neo4j Server?

To use the MCP Neo4j Server, you can run it directly using npx or configure it within your Claude Desktop setup by specifying the necessary environment variables for Neo4j connection.

key features of MCP Neo4j Server?

  • Execute Cypher queries through natural language.
  • Create nodes and relationships in the Neo4j database.
  • Supports complex queries and operations with user-friendly commands.

use cases of MCP Neo4j Server?

  1. Querying employee data in a company.
  2. Adding new products or entities to the graph database.
  3. Establishing relationships between different nodes in the database.

FAQ from MCP Neo4j Server?

  • Can I use natural language for all types of queries?

Yes! The server is designed to interpret natural language commands for various database operations.

  • Is there a limit to the complexity of queries?

While the server can handle complex queries, the performance may vary based on the query's complexity and the database size.

  • How do I install the MCP Neo4j Server?

You can install it via npx or through the Smithery CLI for automatic setup.

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

Recommend Servers

View All
Payai X402 Tools

8 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago