project-structure

A set of project rules describing how a TypeScript application built with Express should be organised, including its main modules, tools, tests, and usage patterns.

In plain words
What is it for?
Use it when building or modifying an Express application that exposes MCP tools, follows the listed module layout, uses pnpm and Biome, and tests with Vitest.
Why use it?
It gives contributors a shared map of the codebase so new files and changes follow the existing structure.

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/bowen31337/expressjs_mcp/project-structure
Clone the repo
git clone --depth 1 https://github.com/bowen31337/expressjs_mcp

Made for: Cursor.

Per session 391 This file is loaded in full into every session.
When invoked 391 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.00391 $0.00391
Opus 5 $0.00196 $0.00196
Sonnet 5 $0.00078 $0.00078
Haiku 4.5 $0.00039 $0.00039

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

Security

Grade A, and why

project-structure 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.

.cursor/rules/project-structure.mdc · 46 lines

What it actually says

Express MCP Project Structure

This project follows the FastAPI-MCP pattern for TypeScript/Express applications.

Core Architecture

The main entry point is src/index.ts, which exports the ExpressMCP class.

Key Modules:

Usage Patterns

Mount to existing Express app:

const mcp = new ExpressMCP(app, { mountPath: '/mcp' });
await mcp.init();
mcp.mount('/mcp');

Standalone HTTP gateway:

await mcp.startStandalone({ port: 7878 });

Configuration

Testing

Tests are in tests/ directory using Vitest. Example: tests/routeIntrospector.test.ts

Examples

Basic usage example in examples/basic/server.ts

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 · 46 lines · 391 tokens per session scan A 1268d8635bab

Subscribe to this mod's changes

project-structure is a cursor rule published in the GitHub repository bowen31337/expressjs_mcp (1 stars, last pushed 1y ago), licensed MIT. It adds 391 tokens to every session, about $0.0020 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.