A Gremlin MCP server that allows for fetching status, schema, and querying using Gremlin for any Gremlin-compatible graph database (TypeScript
Gremlin mcp mcp server connects Gremlin MCP to AI assistants that speak the Model Context Protocol. A Gremlin MCP server that allows for fetching status, schema, and querying using Gremlin for any Gremlin-compatible graph database (TypeScript implementation).
An MCP (Model Context Protocol) server that enables AI assistants to interact with any Gremlin-compatible graph database through natural language. Query your data, discover schemas, analyze relationships, and manage graph data using simple conversations.
Once connected, the assistant can call these 2 tools directly:
Architecture — The Architecture tool exposed by this serverContributing — 1. Follow the rules in RULES.md 2. Run npm run validate before committing 3. Add tests for new functionality 4. Update documentation for user-facing changes 5The server is distributed via npm as command, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.
The server reads 5 environment variables: GREMLIN_ENDPOINT, LOG_LEVEL, GREMLIN_USERNAME, GREMLIN_PASSWORD, GREMLIN_USE_SSL. Keep credentials in your client's env block or a secrets manager rather than committing them.
Database servers turn schema archaeology and ad-hoc reporting into conversation, which is why they tend to be the second or third server people install. Gremlin MCP sits in that group, and the shape of its toolset — Architecture, Contributing — tells you what it is really for. Worth comparing against the other databases servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| Tool | What it does |
|---|---|
| Architecture | The Architecture tool exposed by this server. |
| Contributing | 1. Follow the rules in RULES.md 2. Run npm run validate before committing 3. Add tests for new functionality 4. Update documentation for user-facing changes 5. Ensure all tests pass |
{
"mcpServers": {
"gremlin": {
"command": "npx",
"args": ["@kpritam/gremlin-mcp"],
"env": {
"GREMLIN_ENDPOINT": "localhost:8182",
"LOG_LEVEL": "info"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GREMLIN_ENDPOINT | Configuration value read at startup. | Optional |
| LOG_LEVEL | Configuration value read at startup. | Optional |
| GREMLIN_USERNAME | Configuration value read at startup. | Optional |
| GREMLIN_PASSWORD | Configuration value read at startup. | Optional |
| GREMLIN_USE_SSL | Configuration value read at startup. | Optional |
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.