01-context

01-context is a cursor rule for Cursor from kpritam/gremlin-mcp. It costs 1,691 tokens per session, scanned A, original, MIT.

A TypeScript MCP server that lets AI agents work with Gremlin-compatible graph databases, which store connected data as items and relationships.

In plain words
What is it for?
Use it to check graph status, view vertex and edge types, inspect relationships, run Gremlin traversal queries, and manage the schema cache.
Why use it?
It gives agents a defined way to inspect the database connection and structure, run graph queries, and refresh cached schema information.

Cursor rule for Cursor

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add rules/kpritam/gremlin-mcp/01-context
Clone the repo
git clone --depth 1 https://github.com/kpritam/gremlin-mcp

Made for: Cursor.

Per session 1,691 This file is loaded in full into every session.
When invoked 1,691 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.01691 $0.01691
Opus 5 $0.00846 $0.00846
Sonnet 5 $0.00338 $0.00338
Haiku 4.5 $0.00169 $0.00169

Measured 3d ago against content hash a538c24a46ab, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

01-context scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.cursor/rules/01-context.mdc · 214 lines

How it starts

The opening of the file, as written. The whole thing — 214 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Project Overview

This is a TypeScript-based MCP (Model Context Protocol) server that enables AI agents to interact with Gremlin-compatible graph databases. The server provides 6 tools and 2 resources for comprehensive graph database operations.

Implementation Status: This project is fully implemented using Effect.ts functional programming patterns throughout.

Architecture

Core Components

  • server.ts - Effect-based MCP server with graceful startup/shutdown using Effect composition
  • gremlin/service.ts - Effect-based Gremlin service with Context.Tag service pattern
  • gremlin/schema-service.ts - Effect-based schema management with dependency injection
  • config.ts - Effect.Config-based configuration validation (no backward compatibility)
  • handlers/ - Effect-based modular MCP request handlers with service injection
  • utils/ - Effect-based utility modules with composable operations

Available Tools

  1. get_graph_status - Check database connection status
  2. get_graph_schema - Get complete schema with vertex/edge labels and relationship patterns
  3. run_gremlin_query - Execute any Gremlin traversal query
  4. refresh_schema_cache - Force immediate refresh of cached schema
  5. import_graph_data - Import data from GraphSON or CSV formats with batch processing
  6. export_subgraph - Export subgraph data to JSON, GraphSON, or CSV formats

Available Resources

  1. gremlin://status - Real-time connection status
  2. gremlin://schema - Cached schema information (JSON format)

Development Rules

MUST Follow RULES.md

Always follow the development rules in RULES.md - these are mandatory for all code changes, testing, security, and architecture decisions.

Code Standards

  • Use TypeScript with strict type checking
  • Follow ESLint and Prettier configurations
  • Use Effect.ts functional programming patterns throughout
  • Use Zod for runtime validation with Effect.Config
  • Implement Effect-based error handling with custom error types
  • Write tests for all new functionality using Effect testing patterns

Read the full file on GitHub · 214 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 3d ago First seen · 214 lines · 1,691 tokens per session scan A a538c24a46ab

Subscribe to this mod's changes

01-context is a cursor rule published in the GitHub repository kpritam/gremlin-mcp (9 stars, last pushed 11mo ago), licensed MIT. It adds 1,691 tokens to every session, about $0.0085 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.