Server facts
rxjs-mcp-server
Project
- Author
- shuji-bonji
- Repository
- github.com/shuji-bonji/rxjs-mcp-server
- License
- Not specified
- Category
- Developer Tools
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 5
- Last commit
- Data as of
Tags
- rxjs
- rxjs mcp
- stream visualization
Overview
RxJS debugging can move between emitted values, timing diagrams, and code inspection through this unofficial community project, which is not affiliated with the RxJS team. The execute_stream tool runs supplied snippets in a separate worker thread and reports emissions, timeline information, and performance metrics. For a visual account of timed events, generate_marble produces ASCII diagrams. Developers can also use analyze_operators to examine creation functions and operator chains, including performance concerns and possible alternative approaches. Assistant connections use the stdio transport.
Subscription maintenance and implementation guidance have separate tools. detect_memory_leak examines potential cleanup problems while recognizing patterns such as Angular's takeUntilDestroyed, React effect cleanup, and Vue's onUnmounted. lint_rxjs checks snippets for issues including nested subscriptions and deprecated patterns, with framework-specific rules for Angular, React, and Vue. Its analysis uses regular expressions rather than an ESLint runtime; checks needing type information rely on heuristics and may misclassify code. For implementation examples, suggest_pattern covers workflows such as debounced search, HTTP retries, polling, WebSocket reconnection, reactive validation, state storage, and cache refresh.
rxjs-mcp-server setup notes
- rxjs-mcp-server records stdio only; confirm a network transport upstream before planning remote access.
- rxjs-mcp-server has no recorded license; confirm reuse terms in its repository.