PubNub Model Context Protocol (MCP) Server for Cursor IDE

Created By
pubnuba year ago
PubNub MCP Model Context Protocol Server for use in Cursor, Windsurf, Claude Desktop, Claude Code and OpenAI Codex and more!
Overview

What is PubNub MCP Server?

The PubNub Model Context Protocol (MCP) Server is a CLI-based server that enhances LLM-powered tools by exposing PubNub SDK documentation and API resources, facilitating better interaction with PubNub's services.

How to use PubNub MCP Server?

To use the PubNub MCP Server, install it via npx with the command npx -y @pubnub/mcp, and configure it in your Cursor IDE or run it directly using Node.js.

Key features of PubNub MCP Server?

  • Exposes tools for interacting with PubNub via JSON-RPC over STDIN/STDOUT.
  • Retrieves official PubNub SDK documentation in various programming languages.
  • Publishes messages to PubNub channels and fetches historical messages.
  • Provides real-time presence information for channels.
  • Generates step-by-step instructions for creating PubNub applications.

Use cases of PubNub MCP Server?

  1. Building real-time applications like chat or video streaming.
  2. Fetching and displaying live data such as stock prices or weather updates.
  3. Creating collaborative applications with multi-user features.

FAQ from PubNub MCP Server?

  • What is required to run the MCP server?
    You need Node.js (>= 18) and npm installed on your machine.

  • Can I run the MCP server using Docker?
    Yes, you can configure the MCP server to run via Docker with the appropriate environment variables.

  • Is there a way to disable analytics?
    Yes, set the environment variable MCP_SUBSCRIBE_ANALYTICS_DISABLED=true to disable analytics.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
pubnub
Star
3
Language
JavaScript
License
-

Recommend Servers

View All
Crevio

a day ago
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)

19 hours ago