agentleFS
Sign inStart free
shailesh17shailesh17/mcp-httpserver-proxy/CLAUDE.md

mcp-httpserver-proxy

CLAUDE.md2 starsChanged 3 months agoMITView on GitHub

Welcome, Claude! This document details the technical architecture, strict constraints, development workflows, and Pull Request procedures for mcp-httpserver-proxy. [!IMPORTANT] NEVER use console.log() or write arbitrary text to process.stdout! The client (Claude Desktop, Cursor, etc.) parses stdout strictly as JSON-RPC Model Context Protocol messages. Any non-protocol output on stdout will corrupt the transport and crash the client session. All logging, informational messages, and diagnostics MUST be routed to process.stderr via console.error().

The file

We split this CLAUDE.md into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Conventional Commits: All commit messages and PR titles must follow <type>(<scope>): <description> (e.g.

    line 38
  2. Very specific:

    Pre-flight Checks: Always run pnpm test, pnpm run format, and pnpm run check before submitting.

    line 39
  3. Very specific:

    Dependency Management: Use pnpm exclusively. Never introduce npm or yarn lockfiles.

    line 40

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

Claude Code Guidelines for mcp-httpserver-proxy

Welcome, Claude! This document details the technical architecture, strict constraints, development workflows, and Pull Request procedures for mcp-httpserver-proxy.

⚠️ Critical Constraint: Sacred Standard Output (stdout)

[!IMPORTANT] NEVER use console.log() or write arbitrary text to process.stdout! The client (Claude Desktop, Cursor, etc.) parses stdout strictly as JSON-RPC Model Context Protocol messages. Any non-protocol output on stdout will corrupt the transport and crash the client session.

All logging, informational messages, and diagnostics MUST be routed to process.stderr via console.error().

🛠️ Common Commands

  • Build: pnpm run build (tsc)
  • Test: pnpm test (node --test test/**/*.test.ts)
  • Format: pnpm run format (trunk fmt)
  • Lint & Static Analysis: pnpm run check (trunk check)
  • Dev Watch Mode: pnpm run dev

🏗️ Architecture & Transports

  • Transport Bridge: Transparently connects an MCP Client over stdio (StdioServerTransport) to an MCP HTTP Server over Server-Sent Events (SSEClientTransport).
  • Transport Lifecycle Order: Establish and confirm the SSE backend connection (sseTransport.start()) before starting stdioTransport.start().
  • Custom HTTP Headers: Configured via repeated -H / --header flags and MCP_PROXY_HEADERS environment variable.
  • Resilient Connection Retries: Configured via --retries (-r) and --retry-delay (-d) with exponential backoff.

📝 Coding & Commit Standards

  • Conventional Commits: All commit messages and PR titles must follow <type>(<scope>): <description> (e.g. feat(cli): add header flag, docs(claude): add CLAUDE.md).
  • Pre-flight Checks: Always run pnpm test, pnpm run format, and pnpm run check before submitting.
  • Dependency Management: Use pnpm exclusively. Never introduce npm or yarn lockfiles.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free