GDS Agent
Neither LLMs nor any existing toolings (MCP Servers) are capable of complex reasoning on graphs at the moment.
This MCP Server includes toolings from Neo4j Graph Data Science (GDS) library, which allows you to run all common graph algorithms.
Once the server is running, you are able to ask any graph questions about your Neo4j graph and get answers. LLMs equipped with GDS agent can decide and accurately execute the appropriate parameterised graph algorithms over the graph you have in your Neo4j database.
Usage guide
If you have uvx installed, add the following config to your claude_desktop_config.json
{
"mcpServers": {
"neo4j-gds": {
"command": "/opt/homebrew/bin/uvx",
"args": [ "gds-agent" ],
"env": {
"NEO4J_URI": "bolt://localhost:7687",
"NEO4J_USERNAME": "neo4j",
"NEO4J_PASSWORD": ""
}
}
}
}
Replace command with your uvx location. Find out by running which uvx in the command line.
Replace NEOJ_URI, NEO4J_USERNAME, NEO4J_PASSWORD with your database login details. You can also optionally specify NEO4J_DATABASE.
Full documentation
For complete documentation and development guidelines, please refer to: https://github.com/neo4j-contrib/gds-agent.
Metadata
Release files for iflow-mcp_neo4j-contrib-gds-agent 0.5.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| iflow_mcp_neo4j_contrib_gds_agent-0.5.1.tar.gz | 101.9 kB | Without provenance | Details for iflow_mcp_neo4j_contrib_gds_agent-0.5.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| iflow_mcp_neo4j_contrib_gds_agent-0.5.1-py3-none-any.whl | Python 3 | none | any | Details for iflow_mcp_neo4j_contrib_gds_agent-0.5.1-py3-none-any.whl |
Total release size: 142.5 kB
Release files / iflow_mcp_neo4j_contrib_gds_agent-0.5.1.tar.gz
| Download URL | iflow_mcp_neo4j_contrib_gds_agent-0.5.1.tar.gz |
|---|---|
| Size | 101.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
51195c7334f608c1ef0d9be49bfe6cf0e1572baa14e229ab87bcaa5f163f1edd
|
|
BLAKE2b-256 checksum How to use checksums |
6e108e5319fbf0c8d92e538102e873ac9f7071514d6619d861ab6a47b04ebd65
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.0 {"installer":{"name":"uv","version":"0.10.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / iflow_mcp_neo4j_contrib_gds_agent-0.5.1-py3-none-any.whl
| Download URL | iflow_mcp_neo4j_contrib_gds_agent-0.5.1-py3-none-any.whl |
|---|---|
| Size | 40.5 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
689b10a01a9162746dfb0e7ae7c0372a1c587032451cc0e47a048b8a40a048a1
|
|
BLAKE2b-256 checksum How to use checksums |
3bd2fa79fb5696292d941543a01decca2dfa28727836dd94b437c78edda2df2b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.0 {"installer":{"name":"uv","version":"0.10.0","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Debian GNU/Linux","version":"13","id":"trixie","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for iflow-mcp_neo4j-contrib-gds-agent 0.5.1
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.