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.
@artur-nohup
Basic information
Remote MCP Neo4j Memory Server with OAuth 2.1 and API Key Authentication - TypeScript implementation using FastMCP
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"mcp-neo4j-remote": {
"command": "docker",
"args": [
"build",
"-t",
"mcp-neo4j-remote",
"."
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
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.
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.
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.
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.
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`.
Tools include `read_graph`, `search_nodes`, `find_nodes`, `open_nodes`, `create_entities`, `delete_entities`, `create_relations`, `delete_relations`, `add_observations`, and `delete_observations`.
Server status is available at the resource URI `mcp-neo4j://status`, and authentication details at `mcp-neo4j://auth-info`.

Verified distributed compute for humans, applications, and agents. Submit Blender, Octane, and video workloads, route them across qualified GPUs, track asynchronous execution, download finished artifacts, and verify FARP
OrangePro local-first CLI + MCP server for behavior mapping, grounded test generation, and dynamic proof.

Agent-Native Terminal

Compliance frameworks delivered to AI agents. Nizh gives your agent read access to your organization's compliance program — SOC 2, ISO 27001, CMMC 2.0, NIST, and more — as MCP tools, so it can check posture, read a contr

Ask Claude or ChatGPT what Shopify theme optimization tasks are pending on your store, a remote MCP server for TaskerArmy Agent accounts.
Comments