MCP.so
Sign In

MCP Neo4j Remote Server

@artur-nohup

Repository

About MCP Neo4j Remote Server

Remote MCP Neo4j Memory Server with OAuth 2.1 and API Key Authentication - TypeScript implementation using FastMCP

#mcp-neo4j#neo4j#remote-server

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-neo4j-remote": {
      "command": "docker",
      "args": [
        "build",
        "-t",
        "mcp-neo4j-remote",
        "."
      ]
    }
  }
}

Tools

No tools detected

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is MCP Neo4j Remote Server?

A remote Model Context Protocol (MCP) server that provides persistent memory capabilities through Neo4j graph database integration with OAuth 2.1 and API Key authentication.

How to use MCP Neo4j Remote Server?

Install with npm install, copy .env.example to .env, configure Neo4j credentials and authentication keys, then start with npm run dev or deploy via Docker Compose. The server exposes an MCP endpoint at /stream and provides tools such as read_graph, search_nodes, create_entities, create_relations, and more.

Key features of MCP Neo4j Remote Server

  • Remote HTTP access with dual authentication (OAuth 2.1 via Descope and API Key)
  • Persistent graph-based memory storage using Neo4j
  • Docker support with containerized deployment
  • Health monitoring and built-in endpoints
  • Full TypeScript implementation with type safety

Use cases of MCP Neo4j Remote Server

  • Persistent memory storage for AI agents using knowledge graphs
  • Query and manage large graph databases remotely
  • Create, update, and delete entities and relationships
  • Add and manage observations on existing entities
  • Integrate with MCP-compatible clients for graph-based operations

FAQ from MCP Neo4j Remote Server

How do I authenticate with the server?

Use an API Key via the x-api-key header, Authorization: ApiKey <key>, or the ?api_key= query parameter. For OAuth 2.1, use Authorization: Bearer <token> with a Descope-issued token.

What dependencies does the server require?

You need a running Neo4j database and Node.js (or Docker). Environment variables for Neo4j URI, username, and password are required; API keys and Descope credentials are optional.

How do I deploy the server?

You can run it locally with npm run dev, build for production with npm run build then npm start, or use Docker Compose with docker-compose up --build.

What tools are available for managing the graph?

Tools include read_graph, search_nodes, find_nodes, open_nodes, create_entities, delete_entities, create_relations, delete_relations, add_observations, and delete_observations.

Where can I find server status and authentication information?

Server status is available at the resource URI mcp-neo4j://status, and authentication details at mcp-neo4j://auth-info.

Frequently asked questions

How do I authenticate with the server?

Use an API Key via the `x-api-key` header, `Authorization: ApiKey <key>`, or the `?api_key=` query parameter. For OAuth 2.1, use `Authorization: Bearer <token>` with a Descope-issued token.

What dependencies does the server require?

You need a running Neo4j database and Node.js (or Docker). Environment variables for Neo4j URI, username, and password are required; API keys and Descope credentials are optional.

How do I deploy the server?

You can run it locally with `npm run dev`, build for production with `npm run build` then `npm start`, or use Docker Compose with `docker-compose up --build`.

What tools are available for managing the graph?

Tools include `read_graph`, `search_nodes`, `find_nodes`, `open_nodes`, `create_entities`, `delete_entities`, `create_relations`, `delete_relations`, `add_observations`, and `delete_observations`.

Where can I find server status and authentication information?

Server status is available at the resource URI `mcp-neo4j://status`, and authentication details at `mcp-neo4j://auth-info`.

Comments

Basic information

Category

Developer Tools

Transports

stdio

Author

artur-nohup

More Developer Tools MCP servers

ZeroBeacon — 1000-Tool Collision-Proof Commerce Router

DavidFox998

ZeroBeacon.ai — Collision-proof commerce router for AI agents. 1000 MCP tools: commerce, trust, billing, sovereign ID + everyday tools. LIVE.

Meticulous

Meticulous

MCP server and skills to connect to the Meticulous UI testing platform.

SSH MCP Server

hypnosis

SSH MCP server for AI agents: remote commands, file transfer, log search and server audits through OpenSSH.

1

ship.page

Bitgate

Throw HTML at an API, get an unguessable URL back. Zero-config remote MCP server — your agent deploys pages, sites and CI reports in one call. Free, no signup needed.

LocalCan

LocalCan

Gives AI agents public URLs (tunnels) for localhost, live HTTP traffic inspection, snapshot publishing, and access control. Part of LocalCan, the ngrok alternative for Mac, Windows and Linux. Free plan.

82