# PuppyGraph MCP Server Model Context Protocol (MCP) server for [PuppyGraph](https://puppygraph.com), allowing Claude to query the graph using
Connect PuppyGraph to Claude, Cursor or any other MCP client and it stops being a tab you switch to. # PuppyGraph MCP Server Model Context Protocol (MCP) server for PuppyGraph, allowing Claude to query the graph using Gremlin and Cypher through Claude Desktop. ## Features - Connect to PuppyGraph instances using. The puppygraph mcp server is what makes that connection.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
puppygraph_query — Execute Gremlin or Cypher queries against PuppyGraphpuppygraph_schema — Get schema and structure information about the graphpuppygraph_status — Check PuppyGraph connection statusPUPPYGRAPH_SCHEMA_URL — URL of the PuppyGraph schema endpoint (default: http://localhost:8081/schemajson)PUPPYGRAPH_SCHEMA_USERNAME — Username for PuppyGraph schema API authentication (default: puppygraph)PUPPYGRAPH_SCHEMA_PASSWORD — Password for PuppyGraph schema API authentication (default: puppygraph123)Troubleshooting — You can check connection status using the puppygraph_status tool at any timeConfiguration is passed through the environment: PUPPYGRAPH_URL, PUPPYGRAPH_USERNAME, PUPPYGRAPH_PASSWORD, PUPPYGRAPH_DATABASE, PUPPYGRAPH_GREMLIN_URL, PUPPYGRAPH_GREMLIN_USERNAME, PUPPYGRAPH_GREMLIN_PASSWORD, PUPPYGRAPH_SCHEMA_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.
This sits in the database access group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. PuppyGraph's toolset — puppygraph_query, puppygraph_schema, puppygraph_status and 4 more — is a fair guide to whether it matches your workflow. It is maintained by puppygraph; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against PuppyGraph's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| puppygraph_query | Execute Gremlin or Cypher queries against PuppyGraph |
| puppygraph_schema | Get schema and structure information about the graph |
| puppygraph_status | Check PuppyGraph connection status |
| PUPPYGRAPH_SCHEMA_URL | URL of the PuppyGraph schema endpoint (default: http://localhost:8081/schemajson) |
| PUPPYGRAPH_SCHEMA_USERNAME | Username for PuppyGraph schema API authentication (default: puppygraph) |
| PUPPYGRAPH_SCHEMA_PASSWORD | Password for PuppyGraph schema API authentication (default: puppygraph123) |
| Troubleshooting | You can check connection status using the puppygraph_status tool at any time. |
{
"mcpServers": {
"puppygraph": {
"command": "node",
"args": [
"/path/to/puppygraph-mcp/build/index.js"
],
"env": {
"PUPPYGRAPH_URL": "bolt://your-neo4j-server:7687",
"PUPPYGRAPH_USERNAME": "neo4j",
"PUPPYGRAPH_PASSWORD": "your-password",
"PUPPYGRAPH_DATABASE": "your-database",
"PUPPYGRAPH_GREMLIN_URL": "ws://your-gremlin-server:8182/gremlin",
"PUPPYGRAPH_GREMLIN_USERNAME": "your-username",
"PUPPYGRAPH_GREMLIN_PASSWORD": "your-password"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| PUPPYGRAPH_URL | Endpoint or connection string the server talks to. | Yes |
| PUPPYGRAPH_USERNAME | Configuration value read at startup. | Optional |
| PUPPYGRAPH_PASSWORD | Configuration value read at startup. | Optional |
| PUPPYGRAPH_DATABASE | Configuration value read at startup. | Optional |
| PUPPYGRAPH_GREMLIN_URL | Endpoint or connection string the server talks to. | Yes |
| PUPPYGRAPH_GREMLIN_USERNAME | Configuration value read at startup. | Optional |
| PUPPYGRAPH_GREMLIN_PASSWORD | Configuration value read at startup. | Optional |
| PUPPYGRAPH_SCHEMA_URL | Endpoint or connection string the server talks to. | Yes |
Read-only SQL access to Postgres — let your assistant inspect schemas and answer questions from real data.
Manage your whole Supabase project in conversation — database, auth, storage, Edge Functions and branches.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.
Serverless Postgres with database branching — point your assistant at Neon and let it work on disposable copies.