cursorrules

Coding rules for a TypeScript MCP server that crawls and indexes web documentation. The project searches documentation using both text and meaning, stores metadata and vectors locally, and supports protected sites.

In plain words
What is it for?
Use them when modifying, testing, linting, or formatting the documentation crawler and its search system.
Why use it?
They give an agent consistent project conventions for imports, testing, formatting, embeddings, and strict TypeScript. This makes changes fit the existing codebase.

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/cosmocoder/mcp-web-docs/cursorrules
Clone the repo
git clone --depth 1 https://github.com/cosmocoder/mcp-web-docs

Made for: Cursor.

Per session 842 This file is loaded in full into every session.
When invoked 842 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.00842 $0.00842
Opus 5 $0.00421 $0.00421
Sonnet 5 $0.00168 $0.00168
Haiku 4.5 $0.00084 $0.00084

Measured yesterday against content hash 341b4bb47681, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

cursorrules 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 yesterday.

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.

.cursorrules · 91 lines

How it starts

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

Cursor Rules for MCP Web Docs

This is a TypeScript MCP (Model Context Protocol) server project for crawling and indexing web documentation.

Quick Reference

For comprehensive guidelines, see AGENTS.md in the project root.

Project Overview

MCP Web Docs is a self-hosted MCP server that:

  • Crawls and indexes documentation from any website
  • Provides hybrid search (full-text + semantic/vector)
  • Supports authentication for protected documentation sites
  • Uses local embeddings (FastEmbed) for privacy

Tech Stack

  • Runtime: Node.js >= 24, npm >= 11
  • Language: TypeScript (ES2022, NodeNext modules)
  • Testing: Vitest
  • Storage: SQLite (metadata) + LanceDB (vectors)

Essential Rules

Code Style

  • TypeScript with strict mode enabled
  • Always use .js extensions in imports (ESM requirement)
  • Follow existing patterns in the codebase
  • Run npm run lint and npm run prettier before committing

Testing

  • Tests are co-located: *.test.ts next to source files
  • Use Vitest globals: describe, it, expect, vi
  • Mock embeddings: createMockEmbeddings() from src/__mocks__/embeddings.ts
  • Use vi.hoisted() for mocks configured before imports

Critical Constraints

  • Never log to stdout - MCP servers use stdio for JSON-RPC
  • Use logger from src/util/logger.ts (writes to stderr)
  • Validate inputs with Zod schemas from src/util/security.ts
  • Use validatePublicUrl() for SSRF protection

Key Commands

npm test              # Run tests
npm run build         # Build TypeScript
npm run lint          # Run ESLint
npm run prettier      # Format code
npm run test:coverage # Test with coverage
npm run test:types    # Type check

File Structure

src/
├── index.ts          # CLI bootstrap and signal handling
├── server.ts         # MCP server and tool handlers
├── crawler/          # Web crawling (Playwright/Crawlee)
├── processor/        # Content processing
├── storage/          # SQLite + LanceDB
├── embeddings/       # FastEmbed vectors
├── indexing/         # Workflow, status tracking, queue management
└── util/             # Logger, security, helpers

Read the full file on GitHub · 91 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. yesterday First seen · 91 lines · 842 tokens per session scan A 341b4bb47681

Subscribe to this mod's changes

cursorrules is a cursor rule published in the GitHub repository cosmocoder/mcp-web-docs (1 stars, last pushed 7d ago), licensed MIT. It adds 842 tokens to every session, about $0.0042 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.