Skip to main content
Glama
671,704 tools. Updated 2026-10-18 02:26

"Socket.io" matching MCP tools:

  • Retrieve unread messages and highlighted conversations. Use as a lightweight alternative to full listing when Socket.IO is unavailable.
    -
  • Start a background OctoBot historical data collection job for a specified exchange and symbols, returning a job ID immediately. Poll job status to monitor progress and retrieve the resulting data files.
    MIT
  • Opens an Overleaf project to join its real-time session and cache the file tree. This prerequisite step enables subsequent file operations like list_files, read_file, and edit_file.
    AGPL 3.0
  • Cancel a queued or running backtest job, or retrieve its existing status when already finished. Provides a safe, idempotent way to stop jobs without data loss.
    MIT
  • Capture WebSocket frames from browser tabs to analyze real-time API communications, GraphQL subscriptions, and custom protocols for debugging and reverse engineering.
    MIT

Matching MCP Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    MCP server for live collaborative drawing on ExcaliDash, enabling diagram creation and editing with instant browser updates via Socket.IO.
    19 npm
    MIT
  • -
    license
    Not graded
    quality
    Not graded
    maintenance
    A persistent server using Unix sockets that provides file operations and real-time communication capabilities through both SSE and Socket.IO interfaces.
    -

Matching MCP Connectors

  • Every match, not the top 10. Searches your documents and returns each relevant one, with quotes.

  • Check the factual claims in a draft or an answer: a quick verdict, or a deep check with sources.

  • Edits Overleaf documents in real time by computing a minimal diff and sending it as an OT operation, with optional tracked changes for review.
    AGPL 3.0
  • Connect to RedAlert Socket.IO server and receive real-time emergency alerts. Filter by alert types or enable test mode for simulated alerts.
    MIT
  • Manage bounded Socket.IO sessions for RomM: catalog, open, send, listen, and close realtime events; sending requires write and task permissions.
    MIT
    Destructive
  • Warm up a browser profile by sequentially visiting URLs and saving all resulting cookies. Requires paid plan and desktop app.
    -
  • Join an Overleaf project's real-time session and cache its file tree to enable file operations. Required before listing, reading, or editing files.
    -
  • Update Overleaf documents by sending a minimal diff that takes effect live, with edits appearing as tracked suggestions unless direct write is requested.
    -
  • Generate a WebSocket client for browser, Node, or React Native with auto-reconnect, event handling, and message queuing. Choose socket.io-client, ws, or native library and authenticate via API key.
    MIT
  • Establish a Socket.io connection for real-time event streaming, enabling instant retrieval of new messages and typing indicators. Returns a connection ID for event subscription.
    -
  • Write WHOLE files DIRECTLY — YOUR model generates the code, Kleap stores, builds and deploys it as-is. To change something in a file that ALREADY EXISTS, use edit_files instead (read_files → edit_files): it replaces just the lines you name, while write_files makes you retype the entire file and silently drops whatever you leave out — on a 30KB shared layout that is how headers and footers get wiped. No Kleap-AI step, so what ships is byte-for-byte what you wrote — the right choice when a phrase, a URL or a schema must be exact. Publishing still audits the result (see publish_app). Best for scaffolding exact pages/components — e.g. programmatic-SEO routes. Astro paths (src/pages/*.astro, src/data/*.json, src/components/*.astro, public/*). Overwrites by path. NPM PACKAGES: do not write package.json (the build replaces it) — the build installs whatever your code IMPORTS, so `import { jsPDF } from "jspdf";` is all it takes. Supported on import: @tiptap/*, jspdf, pdf-lib, html2canvas, papaparse, file-saver, jszip, @ffmpeg/*, howler, wavesurfer.js, browser-image-compression, react-dropzone, recharts, chart.js, d3, @tanstack/*, react-hook-form, three, @react-three/*, leaflet, maplibre-gl, gsap, framer-motion, zustand, date-fns, react-markdown, axios, socket.io-client, radix-ui/*, next-themes, lucide-react, @tabler/*, openai, @ai-sdk/*; anything else is refused at build with a message naming it. A client-side router is never the answer — a route is a FILE (src/pages/about.astro → /about). IMAGES AND BINARIES: set encoding:"base64" on the file and send the bytes — that is how you put a logo, a photo, an OG image, a favicon or a font on the site (png/jpg/webp/svg/ico/mp4/woff2/pdf, 512KB max each decoded). Without it you can only write text, and a site with no images looks unfinished. To ADD an image from a text prompt WITHOUT sending any bytes (a real photo's base64 is too big to emit reliably), use generate_image — Kleap generates it and stores it for you. To REMOVE a page or asset, use delete_files — overwriting it with empty content leaves a URL that answers 200 with nothing, which is worse than a 404. DATA & ACCOUNTS: write_files only STORES files — it cannot provision the Kleap Database, so DB or auth code pushed here has no backend and silently does nothing. Stand the feature up with modify_app first, then edit those pages here. After writing, call publish_app to build & go live.
    Connector
    Destructive
    OAuth
  • Write WHOLE files DIRECTLY — YOUR model generates the code, Kleap stores, builds and deploys it as-is. To change something in a file that ALREADY EXISTS, use edit_files instead (read_files → edit_files): it replaces just the lines you name, while write_files makes you retype the entire file and silently drops whatever you leave out — on a 30KB shared layout that is how headers and footers get wiped. No Kleap-AI step, so what ships is byte-for-byte what you wrote — the right choice when a phrase, a URL or a schema must be exact. Publishing still audits the result (see publish_app). Best for scaffolding exact pages/components — e.g. programmatic-SEO routes. Astro paths (src/pages/*.astro, src/data/*.json, src/components/*.astro, public/*). Overwrites by path. NPM PACKAGES: do not write package.json (the build replaces it) — the build installs whatever your code IMPORTS, so `import { jsPDF } from "jspdf";` is all it takes. Supported on import: @tiptap/*, jspdf, pdf-lib, html2canvas, papaparse, file-saver, jszip, @ffmpeg/*, howler, wavesurfer.js, browser-image-compression, react-dropzone, recharts, chart.js, d3, @tanstack/*, react-hook-form, three, @react-three/*, leaflet, maplibre-gl, gsap, framer-motion, zustand, date-fns, react-markdown, axios, socket.io-client, radix-ui/*, next-themes, lucide-react, @tabler/*, openai, @ai-sdk/*; anything else is refused at build with a message naming it. A client-side router is never the answer — a route is a FILE (src/pages/about.astro → /about). IMAGES AND BINARIES: set encoding:"base64" on the file and send the bytes — that is how you put a logo, a photo, an OG image, a favicon or a font on the site (png/jpg/webp/svg/ico/mp4/woff2/pdf, 512KB max each decoded). Without it you can only write text, and a site with no images looks unfinished. To ADD an image from a text prompt WITHOUT sending any bytes (a real photo's base64 is too big to emit reliably), use generate_image — Kleap generates it and stores it for you. To REMOVE a page or asset, use delete_files — overwriting it with empty content leaves a URL that answers 200 with nothing, which is worse than a 404. DATA & ACCOUNTS: write_files only STORES files — it cannot provision the Kleap Database, so DB or auth code pushed here has no backend and silently does nothing. Stand the feature up with modify_app first, then edit those pages here. After writing, call publish_app to build & go live.
    Connector
    Destructive
    No auth
  • Remove endpoints (tools) from an HTTP-API integration — e.g. junk paths like static assets, /socket.io, or SPA routes that aren't real API calls. Identify the integration by `integration_id` or `base_url`, and the endpoints to drop by `operation_ids` (e.g. getSocketIo) and/or `paths` (e.g. /socket.io/). Re-registers the catalog so the removed tools disappear. Returns removed + remaining counts.
    ConnectorAPI key
  • Remove endpoints (tools) from an HTTP-API integration — e.g. junk paths like static assets, /socket.io, or SPA routes that aren't real API calls. Identify the integration by `integration_id` or `base_url`, and the endpoints to drop by `operation_ids` (e.g. getSocketIo) and/or `paths` (e.g. /socket.io/). Re-registers the catalog so the removed tools disappear. Returns removed + remaining counts.
    ConnectorAPI key
  • Remove endpoints (tools) from an HTTP-API integration — e.g. junk paths like static assets, /socket.io, or SPA routes that aren't real API calls. Identify the integration by `integration_id` or `base_url`, and the endpoints to drop by `operation_ids` (e.g. getSocketIo) and/or `paths` (e.g. /socket.io/). Re-registers the catalog so the removed tools disappear. Returns removed + remaining counts.
    ConnectorAPI key