get_sdk_documentation and get_chat_sdk_documentation each carry an explicit list of cases to use the other one for, and the two migration tools do the same — so the retrieval half routes itself instead of returning whichever page matched first. The operational half is unusually complete for a server of this kind: publish, a subscribe that actually waits for messages, history with timetoken paging, presence in both directions, and administration reaching all the way into Functions and Illuminate. Keys travel as call arguments rather than configuration, which is what lets one install work across several keysets.
A PubNub server in two halves: documentation retrieval for the SDKs and platform migrations, and live operations against an account, its keysets and its channels.
- Core SDK documentation by feature and language for non-chat real-time work, and Chat SDK documentation for messaging applications — each carrying an explicit list of what to use the other one for
- Migration guides in two forms: per-SDK version upgrades, and cross-cutting platform changes such as encryption standards, push notification setups and API version moves
- how_to for use-case and platform integration guides, and write_pubnub_app returning the best-practice guide covering architecture, Access Manager security, channel and data modelling, publish/subscribe patterns, history, client reliability and edge logic
- Account administration: apps listed, created and renamed, and keysets fetched, listed, created and updated
- Live channel work: a message or a signal published, a subscription that waits for a set number of messages or up to a timeout, historical messages fetched across channels with start and end timetokens, and presence covering both channel occupancy and which channels a user is in
- App Context CRUD for users, channels and memberships
- Usage metrics per account, app or keyset over a date range, and Insights — read-only aggregated analytics scoped the same way
- PubNub Functions v2 across its full resource surface: packages, revisions, deployments, the KV store, secrets, scheduled events, blueprints and account limits
- Illuminate resources — business objects, metrics, queries, decisions and dashboards — with CRUD plus activation, ad-hoc execution and query verification
For the live tools, the publish and subscribe keys from your PubNub keyset, passed as publishKey and subscribeKey arguments on the call. The Functions and Illuminate tools reach admin APIs and take their own keys and resource identifiers. The documentation tools need neither.
One command plus a key — npx @pubnub/mcp@latest, then supply credentials