The CData MCP Server for Neo4j defines each connection to Neo4j as a named configuration that Claude can use when sending natural language queries.

You create and manage these configurations using the MCP Configuration Tool, which automatically handles formatting, storage, and registration with Claude Desktop.

Understanding Connection Configurations

Each connection configuration is stored in a .mcp file, located in ~/AppData/Roaming/CData/Neo4j Data Provider/, and includes the details needed to initialize the connector when Claude starts a session. For example, a connection called "MyConnection" is stored at ~/AppData/Roaming/CData/Neo4j Data Provider/MyConnection.mcp.

The .mcp file is a text file containing a line-delimited list of connection properties, plus a timestamp. For example, MyConnection.mcp contains the following text:

#Tue May 20 15:48:40 EDT 2025
AuthScheme=Basic
User=myUser
Password=myPassword
Security Token=myToken

The configuration tool handles these settings automatically. Each saved configuration enables Claude to launch a dedicated MCP Server instance with the correct connector and options — no manual file editing required.

Connecting to Neo4j

HTTP API

To connect to Neo4j instances via the HTTP API, set the following connection properties:

• API: Set this to 'HTTP'.
• Server: The server hosting the Neo4j instance. An HTTP or HTTPS protocol prefix may be optionally prepended to the server name or address.
• Port: The port on which the Neo4j service is running. The provider connects to HTTP (7474) port by default. If connecting over HTTPS, supply the HTTPS port for the Neo4j instance specified in Server.
• User: The username of the user using the Neo4j instance.
• Password: The password of the user using the Neo4j instance.
• Database: The database to target in the Neo4j instance. Defaults to "Neo4j".

Query API

To connect to Neo4j instances via the Query API, set the following connection properties:

• API: Set this to 'Query'.
• Server: The server hosting the Neo4j instance. An HTTP or HTTPS protocol prefix may be optionally prepended to the server name or address.
• Port: The port on which the Neo4j service is running. Self-managed instances have a default port of 7474 for the Query API. If connecting over HTTPS, supply the HTTPS port for the Neo4j instance specified in Server. If connecting to a Neo4J Aura instance, the port should always be 443.
• User: The username of the user using the Neo4j instance.
• Password: The password of the user using the Neo4j instance.
• Database: The database to target in the Neo4j instance. Defaults to "Neo4j".

Neo4J Aura

To connect to Neo4j Aura instances, the required properties will be the same as the Query API configuration above. Notes on finding property values are below.

• API: Set this to 'Query'.
• Server: Found in 'Query API URL' in the 'Inspect' menu of the instance in the Neo4j Aura cloud console. Nothing after "Neo4j.io" should be provided.
• Port: Set this to 443.
• User: The username of the user using the Neo4j instance.
• Password: Provided only once when creating the instance or when a new user is invited.
• Database: Currently, Neo4j Aura deployments do not allow changing the database name from the default value of 'Neo4j'.