rxjs-mcp-server
The rxjs-mcp-server lets you execute, debug, visualize, and analyze RxJS streams directly from AI assistants via the MCP Protocol.
Execute RxJS code (
execute_stream) — run Observable code in an isolated worker thread, capturing stream emissions, timelines, and performance metrics, with configurable timeout, value limits, and memory tracking.Generate marble diagrams (
generate_marble) — produce ASCII marble diagrams to visually represent stream behavior over time, with customizable time scale and value display.Analyze operators (
analyze_operators) — inspect RxJS operator chains for performance bottlenecks, best-practice violations, and alternative approaches.Detect memory leaks (
detect_memory_leak) — identify unsubscribed subscriptions and missing cleanup patterns, with framework-specific recommendations (Angular, React, Vue).Suggest patterns (
suggest_pattern) — get production-ready RxJS patterns for 15+ common use cases (e.g., HTTP retry, search typeahead, WebSocket reconnection, polling, state management, infinite scroll, auto-save), tailored to a target framework (Angular, React, Vue, or vanilla).
Analyzes RxJS streams within Angular applications to detect memory leaks and provides framework-specific recommendations for proper subscription cleanup.
Coordinates with ESLint to maintain code quality and ensure best practices are followed in RxJS implementations.
Identifies potential RxJS memory leaks in React applications and suggests proper cleanup patterns for reactive streams.
Enables the execution, debugging, and visualization of TypeScript-based RxJS code, including operator chain analysis and marble diagram generation.
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.
Features
🚀 Stream Execution
Execute RxJS code and capture emissions
Timeline visualization with timestamps
Memory usage tracking
Support for all major RxJS operators
📊 Marble Diagrams
Generate ASCII marble diagrams
Visualize stream behavior over time
Automatic pattern detection
Clear legend and explanations
🔍 Operator Analysis
Analyze operator chains for performance
Detect potential issues and bottlenecks
Suggest alternative approaches
Categorize operators by function
🛡️ Memory Leak Detection
Identify unsubscribed subscriptions
Detect missing cleanup patterns
Framework-specific recommendations (Angular, React, Vue)
Provide proper cleanup examples
💡 Pattern Suggestions
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...
Installation
# Install globally
npm install -g @shuji-bonji/rxjs-mcp
# Or use with npx
npx @shuji-bonji/rxjs-mcpConfiguration
Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"rxjs": {
"command": "npx",
"args": ["@shuji-bonji/rxjs-mcp"]
}
}
}VS Code with Continue/Copilot
Add to .vscode/mcp.json:
{
"mcpServers": {
"rxjs": {
"command": "npx",
"args": ["@shuji-bonji/rxjs-mcp"]
}
}
}Cursor
Add to ~/.cursor/mcp.json:
{
"mcpServers": {
"rxjs": {
"command": "npx",
"args": ["@shuji-bonji/rxjs-mcp"]
}
}
}Available Tools
execute_stream
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 — return is 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),
);generate_marble
Generate ASCII marble diagrams from event data.
// Input: array of timed events
[
{ time: 0, value: 'A' },
{ time: 50, value: 'B' },
{ time: 100, value: 'C' },
];
// Output: A----B----C--|analyze_operators
Analyze RxJS operator chains for performance and best practices.
// Analyzes chains like:
source$.pipe(
map((x) => x * 2),
filter((x) => x > 10),
switchMap((x) => fetchData(x)),
retry(3),
);detect_memory_leak
Detect potential memory leaks and missing cleanup.
// Detects issues like:
- Missing unsubscribe
- No takeUntil operator
- Uncompleted Subjects
- Infinite intervalssuggest_pattern
Get production-ready patterns for common use cases.
Available patterns:
http-retry- Resilient HTTP with retrysearch-typeahead- Debounced searchpolling- Smart polling with backoffwebsocket-reconnect- Auto-reconnecting WebSocketform-validation- Reactive form validationstate-management- Simple state storecache-refresh- Cache with refresh strategyAnd more...
Usage Examples
With Claude
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]Debugging Memory Leaks
User: "Check this Angular component for memory leaks"
Claude: I'll analyze your component for potential memory leaks.
[Uses detect_memory_leak tool]
## Memory Leak Analysis
⚠️ Potential leaks detected
1. 🔴 subscription (high severity)
- Found 3 subscribe() calls but only 1 unsubscribe()
- Fix: Use takeUntil pattern with destroy$ subjectGetting Patterns
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]Security
The execute_stream tool runs user-provided code in an isolated Worker thread to 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.
Development
# 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 devRelease
Releases are automated via GitHub Actions and published to npm using Trusted Publisher (OIDC) — no static tokens are used, and every release carries an npm provenance attestation. See RELEASING.md for the full workflow (and initial npm setup).
Integration with Other MCP Servers
RxJS MCP Server works great alongside:
Angular MCP - For Angular project scaffolding
TypeScript MCP - For type checking
ESLint MCP - For code quality
Future Meta-MCP integration will allow seamless coordination between these tools.
Architecture
┌─────────────────┐
│ AI Assistant │
│ (Claude, etc) │
└────────┬────────┘
│
MCP Protocol
│
┌────────┴────────┐
│ RxJS MCP Server│
├─────────────────┤
│ • execute_stream│
│ • generate_marble│
│ • analyze_operators│
│ • detect_memory_leak│
│ • suggest_pattern│
└─────────────────┘Contributing
Contributions are welcome! Please feel free to submit a PR.
License
MIT
Author
Shuji Bonji
Links
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/shuji-bonji/rxjs-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server