Pubnub MCP Server

PubNub Model Context Protocol MCP Server for Cursor and Claude. That is what the pubnub mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

A hosted Model Context Protocol (MCP) server that exposes PubNub SDK documentation and PubNub API resources to LLM-powered tools. This improves the LLM AI Agent's ability to understand and interact with PubNub's SDKs and APIs. Uses HTTP transport with OAuth authentication.

• 📚 Comprehensive SDK Documentation — - Access detailed documentation, code examples, and implementation guides for 20+ programming languages including JavaScript, Python, Java, Swift, Kotlin, C#, Ruby, Go, and more
• 🏗️ Application & Keyset Management — - Create, configure, and manage PubNub applications and keysets with features like message persistence, file sharing, presence tracking, and app context
• 💬 Real-time Communication — - Send and receive messages across channels, implement live chat, notifications, and real-time updates with support for both messages and lightweight signals
• 📍 Presence & Activity Tracking — - Monitor real-time user presence, see who's online in channels, and track user activity across your application
• 📊 Real-time Decisioning & Analytics — - Trigger the right action when it matters, measure its impact, and adjust as conditions change -- all in real-time. Requires Illuminate
• 🔍 Usage & Monitoring — — Track billable usage across apps and keysets, review current and historical consumption, and export reports to understand cost drivers

The tools it exposes

The server publishes 8 tools. What each one is for:

• Cursor — Click the button above, then select Open Cursor. In Cursor, click Install, select the organization you want to authorize, and click **Allow
• Codex — Then run codex mcp login pubnub to authenticate, select the organization you want to authorize, and click Allow access. [Learn more in Codex
• OpenCode — Then run opencode mcp auth pubnub to authenticate. Learn more in OpenCode documentation
• Prerequisites — The Prerequisites tool exposed by this server
• Testing — The Testing tool exposed by this server
• Tools — The Tools tool exposed by this server
• Prompts — The Prompts tool exposed by this server
• Resources — The Resources tool exposed by this server

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

What it needs from you

Configuration is passed through the environment: PUBNUB_API_KEY, OAUTH_CLIENT_ID, OAUTH_CLIENT_SECRET, ADMIN_API_RESOURCE_URL, MCP_RESOURCE_URL, ADMIN_API_V2_URL, SDK_DOCS_API_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

• Node.js >= 20.0.0

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Pubnub's toolset — Cursor, Codex, OpenCode and 5 more — is a fair guide to whether it matches your workflow. It is maintained by pubnub; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Pubnub's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.