PubNub MCP Server

Retrieve Chat SDK documentation for building chat/messaging applications. **When to use:** - Building ANY chat or messaging application (1:1, group, channels) - Need typing indicators, read receipts, @mentions, unread counts - Want message threads, reactions, pinned messages, moderation - Need user/channel management with chat-specific features - Prefer rapid development with intuitive methods like sendText(), startTyping(), join() **Do NOT use for:** - Non-chat real-time apps (IoT, gaming state, analytics) → use "get_sdk_documentation" - Conceptual guides → use "how_to" **Example features:** - messages-send-receive, messages-threads, messages-reactions - channels-create, channels-join, channels-typing-indicator - users-mentions, users-presence Returns code examples and API references for the specified language/feature.

Fetches historical messages from one or more PubNub channels. Call this tool whenever you need to access past message history. Provide a list of channel names. Returns message content and metadata in JSON format. Supports pagination with start/end timetokens and count limit.

Retrieves real-time presence information. Use 'channels'/'channelGroups' for HereNow (occupancy/users in channel) and/or 'uuid' for WhereNow (channels a user is in). Returns presence data in JSON format. Requires publish and subscribe keys from your PubNub keyset.

Retrieve Core SDK documentation for low-level real-time features. **When to use:** - Building NON-CHAT real-time apps (IoT, gaming state sync, live analytics, notifications) - Need fine-grained control over pub/sub, presence, storage, or access management - Implementing custom real-time patterns - Need API reference for specific SDK methods (publish, subscribe, history, etc.) **Do NOT use for:** - Chat/messaging apps → use "get_chat_sdk_documentation" instead - Conceptual guides → use "how_to" Returns code examples, API references, and implementation guides for the specified language/feature combination.

Fetches usage metrics from the PubNub Admin API for an account, app, or keyset. **Parameters:** - entityType: 'account', 'app', or 'keyset' - entityId: The ID of the entity - from: Start date (inclusive) in YYYY-MM-DD format - to: End date (exclusive) in YYYY-MM-DD format - metrics: Array of metric names to retrieve **Available Metric Categories:** - Core transactions: txn_total, mtd_txn_total, replicated, signals, edge - MAU/UUID: mtd_uuid, uuid, pn_uuid - Messages: msgs_total, publish, subscribe_msgs, history_msgs, files_msgs, push_msgs - Storage: bytes_stored, bytes_stored_messages, bytes_stored_files, etc. - Access Manager: accessmanager_grants_transactions, accessmanager_audits_transactions - Functions: executions, kv_read_transactions, kv_write_transactions - History: history_transactions, history_with_actions_transactions - Message Actions: message_actions_add_transactions, message_actions_get_transactions - Objects/App Context: objects_create_user_transactions, objects_get_user_transactions, etc. - Presence: presence_herenow_transactions, presence_wherenow_transactions - Push Notifications: apns_sent_transactions, gcm_sent_transactions - Subscribe: subscribe_transactions, subscribe_heartbeats_transactions - Publish: publish_transactions, publish_bytes - Signal: signal_transactions - Files: files_publish_transactions, files_get_file_transactions

Retrieve conceptual guides for specific PubNub use cases and integrations. **When to use:** - Learning how to implement a specific use case (gaming, healthcare, IoT) - Need step-by-step integration guide for a platform (Unity, Unreal etc) - Understanding PubNub features in context (presence, push notifications, functions) **Do NOT use for:** - API reference or code samples of a specific PubNub features → use `get_sdk_documentation` or `get_chat_sdk_documentation` - General best practices → use `write_pubnub_app`

Manages PubNub App Context (Objects API) for users, channels, and memberships. Supports CRUD operations including get, set, remove, and getAll. Use this tool to manage user profiles, channel metadata, and membership relationships in your PubNub application.

Manages PubNub apps with operations: list, create, update. - 'list': List all apps on your account. - 'create': Create a new app. User must provide data.name. - 'update': Update an existing app name. User must provide data.id and data.name.

Manages PubNub keysets with operations: get, list, create, update. - 'get': Get a specific keyset information. User needs to provide the keyset id. - 'list': List all keysets for your account or a specific app. - 'create': Create a new keyset. New keyset is created with Message Persistence, App Context, Files, and Presence enabled by default; the user must provide name, production, and config with nested objects (messagePersistence, appContext, files, presence), and if any required parameter is missing, you must ask the user to provide it. - 'update': Update an existing keyset. User needs to provide the keyset id and the config to update.

Send a message or signal to a PubNub channel in real-time. Supports both regular messages and lightweight signals. Plain strings are automatically wrapped in a 'text' field. Requires publish and subscribe keys from your PubNub keyset.

Subscribe to a PubNub channel and receive messages in real-time. Specify the number of messages (default 1) and/or a timeout (default 10s, max 30s) to wait for. Requires publish and subscribe keys from your PubNub keyset.

Retrieve PubNub best practices guide covering: 1) Architecture & project setup (environments, payload sizes), 2) Security (Access Manager tokens, least privilege, PII hygiene), 3) Channel & data modeling (naming conventions, message schemas), 4) Publish/Subscribe patterns, 5) History usage, 6) Client reliability (reconnect, idempotency, ordering), 7) Functions/edge logic, 8) Presence & state, 9) App Context, 10) Mobile specifics (push notifications, caching), 11) Web specifics (tab lifecycle, Service Workers), 12) Observability & ops, 13) Performance & cost optimization. Call this tool when building PubNub applications to ensure robust, scalable, and secure implementations.