Rxjs Mcp Server

Created By
shuji-bonji5 months ago
Execute, debug, and visualize RxJS streams directly from AI assistants like Claude.
Overview

what is RxJS MCP Server?

RxJS MCP Server is a tool that allows users to execute, debug, and visualize RxJS streams directly from AI assistants like Claude.

how to use RxJS MCP Server?

To use the RxJS MCP Server, install it globally using npm or run it with npx. Configure it in your AI assistant or development environment to start executing RxJS streams.

key features of RxJS MCP Server?

  • Execute RxJS code and capture emissions with timeline visualization.
  • Generate ASCII marble diagrams to visualize stream behavior.
  • Analyze operator chains for performance and detect potential issues.
  • Identify memory leaks and suggest cleanup patterns.
  • Provide battle-tested RxJS patterns for common use cases.

use cases of RxJS MCP Server?

  1. Executing and debugging RxJS streams in real-time.
  2. Visualizing stream behavior with marble diagrams.
  3. Analyzing performance of RxJS operator chains.
  4. Detecting memory leaks in Angular, React, or Vue applications.
  5. Implementing common patterns like HTTP retry and form validation.

FAQ from RxJS MCP Server?

  • Is RxJS MCP Server affiliated with the RxJS team?

No, it is an unofficial community project.

  • How do I install RxJS MCP Server?

You can install it globally using npm or run it with npx.

  • Can I use RxJS MCP Server with different frameworks?

Yes, it provides framework-specific recommendations for Angular, React, and Vue.

Server Config

{
  "mcpServers": {
    "rxjs": {
      "command": "npx",
      "args": [
        "@shuji-bonji/rxjs-mcp"
      ]
    }
  }
}
Project Info
Created At
5 months ago
Updated At
4 months ago
Author Name
shuji-bonji
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago