MCP Neo4j Remote Server
About
Remote MCP Neo4j Memory Server with OAuth 2.1 and API Key Authentication - TypeScript implementation using FastMCP
Explore
- Remote Access: HTTP-based MCP server that can be accessed over the network
- Dual Authentication:
- OAuth 2.1 via Descope (for users/applications that support OAuth)
- API Key authentication (for clients that only support API keys)
- Neo4j Integration: Persistent graph-based memory storage
- Docker Support: Containerized deployment with Docker Compose
- Health Monitoring: Built-in health checks and monitoring endpoints
- TypeScript: Full TypeScript implementation with type safety
Setting up with Highlight
This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:
- Download and install Highlight from highlightai.com/download
- Navigate to the plugins tab and select "Add Custom Plugin"
-
Configure the plugin with the settings below
Plugin Name
MCP Neo4j Remote ServerCommand (node, npx, python, etc.)Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.
- Enable "Start Automatically" if you want the plugin to start when Highlight launches
From the repository
2. Configuration
Copy .env.example to .env and configure:
cp .env.example .env
Edit .env with your settings:
```env
The server provides the same tools as the original Python implementation:
Claude Desktop / Cursor
Paste into your MCP client config file to install this server.
{
"mcpServers": {
"mcp neo4j remote server": {
"mcp-neo4j-remote": {
"command": "docker",
"args": [
"build",
"-t",
"mcp-neo4j-remote",
"."
]
}
}
}
}McpServers
{
"mcp-neo4j-remote": {
"command": "docker",
"args": [
"build",
"-t",
"mcp-neo4j-remote",
"."
]
}
}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.
Features
- Remote Access: HTTP-based MCP server that can be accessed over the network
- Dual Authentication:
- OAuth 2.1 via Descope (for users/applications that support OAuth)
- API Key authentication (for clients that only support API keys)
- Neo4j Integration: Persistent graph-based memory storage
- Docker Support: Containerized deployment with Docker Compose
- Health Monitoring: Built-in health checks and monitoring endpoints
- TypeScript: Full TypeScript implementation with type safety
Architecture
The server converts the original Python Neo4j MCP implementation to TypeScript using the FastMCP framework, enabling remote access with robust authentication.
Authentication Methods
1. OAuth 2.1 (via Descope):
- Use Authorization: Bearer <token> header
- Supports multiple OAuth providers (Google, GitHub, Microsoft, etc.)
- Full user session management
2. API Key:
- Use Authorization: ApiKey <key> header
- Or x-api-key: <key> header
- Or ?api_key=<key> query parameter
Quick Start
1. Installation
cd /workspace/mcp-neo4j-remote
npm install
2. Configuration
Copy .env.example to .env and configure:
cp .env.example .env
Edit .env with your settings:
```env
Sign in to leave a review
Use Google, GitHub, or an email account so ratings stay tied to real people.
No reviews posted yet.
