Rxjs Mcp Server

⚠️ This is an unofficial community project, not affiliated with RxJS team.

Execute, debug, and visualize RxJS streams directly from AI assistants like Claude.

- Execute RxJS code and capture emissions
- Timeline visualization with timestamps
- Memory usage tracking
- Support for all major RxJS operators

- Generate ASCII marble diagrams
- Visualize stream behavior over time
- Automatic pattern detection
- Clear legend and explanations

- Analyze operator chains for performance
- Detect potential issues and bottlenecks
- Suggest alternative approaches
- Categorize operators by function

- Get battle-tested RxJS patterns
- Framework-specific implementations
- Common use cases covered:

- HTTP retry with backoff
- Search typeahead
- WebSocket reconnection
- Form validation
- State management
- And more...

# Install globally npm install -g @shuji-bonji/rxjs-mcp # Or use with npx npx @shuji-bonji/rxjs-mcp

Add to~/Library/Application Support/Claude/claude_desktop_config.json:

{ "mcpServers": { "rxjs": { "command": "npx", "args": ["@shuji-bonji/rxjs-mcp"] } } }

{ "mcpServers": { "rxjs": { "command": "npx", "args": ["@shuji-bonji/rxjs-mcp"] } } }

{ "mcpServers": { "rxjs": { "command": "npx", "args": ["@shuji-bonji/rxjs-mcp"] } } }

Execute RxJS code and capture stream emissions with timeline.

The tool accepts either an expression that evaluates to an Observable, or a snippet ending in such an expression —returnis optional.

// ✅ Trailing expression (v0.2.0+): the last expression is returned implicitly interval(100).pipe( take(5), map((x) => x  2), ); // ✅ Declaration + trailing reference const stream$ = interval(100).pipe( take(5), map((x) => x  2), ); stream$; // ✅ Explicit return (always works) return interval(100).pipe( take(5), map((x) => x  2), );

// Input: array of timed events [ { time: 0, value: 'A' }, { time: 50, value: 'B' }, { time: 100, value: 'C' }, ]; // Output: A----B----C--|

// Analyzes chains like: source$.pipe( map((x) => x  2), filter((x) => x > 10), switchMap((x) => fetchData(x)), retry(3), );

Detect potential memory leaks and missing cleanup.

Get production-ready patterns for common use cases.

- http-retry- Resilient HTTP with retry
- search-typeahead- Debounced search
- polling- Smart polling with backoff
- websocket-reconnect- Auto-reconnecting WebSocket
- form-validation- Reactive form validation
- state-management- Simple state store
- cache-refresh- Cache with refresh strategy
- And more...

Lint RxJS code snippets for common issues and best practices. Based oneslint-plugin-rxjs-xrules.

// Parameters: { code: string; // RxJS code to lint config?: 'recommended' | 'strict'; // Rule set (default: recommended) framework?: 'angular' | 'react' | 'vue' | 'none'; // Framework context rules?: string[]; // Specific rules to check (overrides config) }

- recommended— 20 rules covering the most common issues
- strict— All rules including style checks (finnish, no-exposed-subjects, etc.)

User: "Execute this RxJS stream and show me the output" Claude: I'll execute that RxJS stream for you. [Uses execute_stream tool] ## Stream Execution Result ✅ Completed Execution Time: 523ms Values Emitted: 5 ### Emitted Values [0, 2, 4, 6, 8]

User: "Show me how to implement search with RxJS" Claude: I'll show you the search typeahead pattern. [Uses suggest_pattern tool with useCase: 'search-typeahead'] ## Search Typeahead with Debounce [Full implementation with explanation]

Theexecute_streamtool runs user-provided code in anisolated Worker threadto prevent:

- Main process pollution
- Resource leaks from infinite loops or timers
- Access to sensitive Node.js APIs (process, fs, etc.)

Execution is forcefully terminated if it exceeds the configured timeout.

# Clone the repository git clone https://github.com/shuji-bonji/rxjs-mcp-server cd rxjs-mcp-server # Install dependencies npm install # Build npm run build # Run tests npm test # Unit tests (vitest) npm run test:mcp # MCP integration test npm run test:inspector # MCP Inspector (GUI) # Run in development npm run dev

Releases are automated via GitHub Actions and published to npm usingTrusted Publisher (OIDC)— no static tokens are used, and every release carries an npm provenance attestation. SeeRELEASING.mdfor the full workflow (and initial npm setup).

┌─────────────────┐ │ AI Assistant │ │ (Claude, etc) │ └────────┬────────┘ │ MCP Protocol │ ┌────────┴────────┐ │ RxJS MCP Server│ ├─────────────────┤ │ • execute_stream│ │ • generate_marble│ │ • analyze_operators│ │ • detect_memory_leak│ │ • suggest_pattern│ │ • lint_rxjs │ └─────────────────┘

If a guide page does not yet exist for an operator, the field is simply omitted (no broken link). Coverage is tracked by theURL validation CI.

- GitHub Repository
- RxJS Documentation
- Model Context Protocol

Visual Studio extension with 20 Roslyn-powered MCP tools for AI assistants. Semantic code navigation, symbol search, inheritance, call graphs, safe rename, build/test.