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.
git clone --depth 1 https://github.com/bowen31337/expressjs_mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/rules/bowen31337/expressjs_mcp/project-structure)<a href="https://agentmods.dev/rules/bowen31337/expressjs_mcp/project-structure"><img src="https://agentmods.dev/badge/rules/bowen31337/expressjs_mcp/project-structure/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/rules/bowen31337/expressjs_mcp/project-structure"><img src="https://agentmods.dev/badge/rules/bowen31337/expressjs_mcp/project-structure.svg" alt="Reviewed on agentmods" width="80" height="20"></a>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.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00391 | $0.00391 |
| Opus 5.5 | $0.00156 | $0.00156 |
| Sonnet 5.5 | $0.00078 | $0.00078 |
| Haiku 4.5 | $0.00039 | $0.00039 |
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 1mo 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.
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:
- src/routeIntrospector.ts - Discovers routes from Express app's
_router.stack - src/inMemoryDispatcher.ts - Executes synthetic requests through middleware chain
- src/schemaResolver.ts - Builds tool schemas from OpenAPI/annotations
- src/mcpServer.ts - HTTP gateway for MCP tools at
/mcp/toolsand/mcp/invoke
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
- Use package.json with pnpm as package manager
- TypeScript config in tsconfig.json
- Biome for linting/formatting via biome.json
- Vitest for testing via vitest.config.ts
Testing
Tests are in tests/ directory using Vitest. Example: tests/routeIntrospector.test.ts
Examples
Basic usage example in examples/basic/server.ts
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.
- 1mo ago First seen · 46 lines · 391 tokens per session scan A 1268d8635bab
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.0016 per session on Opus 5.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.
Other cursor rules, from other repositories
django-python
Rules for writing Python services at PostHog (Python servers powered by the Django framework).
python--typescript-guide-cursorrules-prompt-file
Cursor rules for Python development with TypeScript guide integration.
typescript-patterns
Cursor rule "typescript-patterns" from fmflurry/settings-opencode, covering typescript/javascript patterns, api response format, custom hooks pattern and repository pattern.
standard-nestjs-module-hierarchy
Establish a consistent NestJS module structure in the API application where each resource is encapsulated in its own module with proper hierarchical organization to enhance maintainability, scalabilit... .
nestjs-best-practices
../../.claude/rules/nestjs-best-practices.md.
nestjs
This guide provides opinionated, actionable best practices for building robust, scalable, and maintainable NestJS applications using TypeScript, emphasizing modern patterns and common pitfalls.