Ethora MCP Server vs Pubnub MCP Server
A side-by-side look at the Ethora MCP Server and Pubnub MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Ethora MCP Server for communication work as a local process; choose Pubnub MCP Server for communication as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Ethora MCP Server when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: OAuth 2.0.
- You have the keys it needs:
ETHORA_API_URL, ETHORA_APP_JWT, ETHORA_B2B_TOKEN, ETHORA_MCP_AUTH_ISSUER. - You want tools like
ethora-configure, ethora-status, ethora-help.
Choose Pubnub MCP Server when
- You need dedicated capabilities in the Communication domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PUBNUB_API_KEY. - You want tools like
get_sdk_documentation, get_chat_sdk_documentation, get_sdk_migration_guide.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Communication | Communication |
| Quality signal | 67/100 · Great | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | OAuth 2.0 | Not declared |
| Pricing | Free | Not declared |
| Required env vars | ETHORA_API_URLETHORA_APP_JWTETHORA_B2B_TOKENETHORA_MCP_AUTH_ISSUER | PUBNUB_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6 | 33 |
| Directory activity | 5 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 89 | 17 |
| Full listing | View Ethora MCP Server | View Pubnub MCP Server |
Tools & capabilities
Ethora MCP Server tools 89
ethora-configureSet the Ethora API URL and credentials for this MCP session. Stores values in memory only; each call merges with omitted fields kept. Alternative to env vars (ETHORA_API_URL / ETHORA_APP_JWT / ETHORA_APP_TOKEN / ETHORA_B2B_TOKEN). On a hosted server `apiUrl` is fixed and cannot be changed; credentials are per session. Auth: none required — this establishes auth material. Errors: only if a value is structurally invalid. Follow with an `ethora-auth-use-*` tool to pick the active mode.ethora-statusReport the current Ethora MCP session state: configured API URL, active auth mode, which credentials are present (booleans like `hasAppJwt` — values never echoed), the selected appId/agentId, and `hosted`/`sessionId` on the hosted (Streamable HTTP) server. Auth: none required. Errors: effectively none. Related: `ethora-doctor` for an active connectivity check.ethora-helpTask-oriented orientation for this MCP server: explains the three Ethora auth modes (user / app-token / B2B) and recommends next tool calls + recipes based on current session state. Auth: none required — inspects state, no API calls. Errors: effectively none. Related: pass a recommended recipe id to `ethora-run-recipe`.ethora-run-recipeExecute a built-in recipe — an ordered sequence of this server's own tool calls — by id. Recipes capture common flows (B2B bootstrap, broadcast, sources ingest). Use `dryRun: true` to preview resolved steps. Omit `recipeId` to list runnable recipes for a `goal`. Requires: the inputs the chosen recipe lists; call without `recipeId` first to see the recipes and their required inputs. Auth: depends on the recipe's steps — configure those first (see `ethora-help`). Errors: stops at the first failing step and returns the partial log; a missing required `vars` entry fails fast before any step runs.ethora-doctorDiagnose the session: validate the config is internally consistent for the active auth mode and ping the Ethora API (`GET /v1/ping`). Returns `{ state, checks, ping, suggestions }`. Auth: none required; report is tailored to whatever credentials are set. Errors: rarely throws — instead returns `suggestions` and a `ping.ok: false` block when the API is unreachable.ethora-auth-use-appSwitch this session's active auth mode to app-token, so subsequent app-scoped calls authenticate with the configured `appToken`. Auth: requires an `appToken` to already be configured (via `ethora-configure`, ETHORA_APP_TOKEN env, or `ethora-app-select`). Errors: returns an error if no `appToken` is configured. Related: use after `ethora-app-select`.ethora-auth-use-userSwitch this session's active auth mode to user-session, so subsequent calls authenticate as a logged-in Ethora user. Auth: the switch needs nothing, but user-auth tools only work once `ethora-user-login` stores a user token (login also needs a configured `appJwt`). Errors: none on the switch; downstream tools return 401 until login succeeds. Related: follow with `ethora-user-login`.ethora-auth-use-b2bSwitch this session's active auth mode to B2B, so subsequent calls authenticate as a tenant actor via the `x-custom-token` header. Auth: requires a `b2bToken` (JWT with `type=server`) to already be configured (via `ethora-configure` or ETHORA_B2B_TOKEN env). Errors: returns an error if no `b2bToken` is configured. Related: server-side automation — pairs with `ethora-b2b-app-create`, `ethora-users-batch-create-v2`, `ethora-app-tokens-*-v2`.ethora-app-selectSet the current app context for this session so app-scoped tools can omit their `appId` argument. Stores `currentAppId` and, if given, `appToken` (which defaults the auth mode to app-token unless `authMode` overrides). Auth: none required to set the context. Errors: effectively none — a non-existent `appId` is not validated here; the first app-scoped API call surfaces the 404. Related: pairs with `ethora-auth-use-app`.ethora-chats-broadcast-v2Enqueue an asynchronous broadcast job posting a message to one or more chat rooms of an app — returns a `jobId`; messages are not sent synchronously. Targeting is exclusive: `allRooms`, `chatIds`, or `chatNames`, not a mix. Requires: a selected app with at least one room (`ethora-app-create-chat`). Auth: app-token mode OR B2B mode with an explicit `appId`. Errors: 401/403 wrong auth; 400 no target or conflicting targets; 404 unknown `appId` or room. Related: track with `ethora-wait-broadcast-job-v2`.ethora-chats-broadcast-job-v2Fetch the current status and per-room results of a broadcast job by `jobId` (one-shot, no polling). Returns the job object with its `state` (pending/running/completed/failed). Requires: a selected app with at least one room (`ethora-app-create-chat`). Auth: app-token mode OR B2B mode with an explicit `appId` — must match the auth used to enqueue the job. Errors: 401/403 wrong auth; 404 unknown `jobId`. Related: `ethora-wait-broadcast-job-v2` for a blocking wait.ethora-wait-broadcast-job-v2Block until a broadcast job reaches a terminal state (`completed` or `failed`) or until `timeoutMs` — read-only polling wrapper around `ethora-chats-broadcast-job-v2`. Returns `{ done, state, job }`, or `{ done: false, reason: "timeout" }` on timeout. Requires: a `jobId` returned by `ethora-chats-broadcast-job-v2`. Auth: app-token mode OR B2B mode with an explicit `appId` — must match the auth used to enqueue the job. Errors: 401/403 wrong auth; 404 unknown `jobId`.- +77 more on the listing page
Pubnub MCP Server tools 17
get_sdk_documentationRetrieve 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.) - For Python SDK usage always request about sync or asyncio version of langauge. **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.get_chat_sdk_documentationRetrieve 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.get_sdk_migration_guideRetrieve SDK migration guides for upgrading between PubNub SDK versions. **When to use:** - Upgrading a PubNub SDK to a newer major version - Need step-by-step instructions for migrating breaking changes - Refactoring a codebase after a PubNub SDK version bump **Do NOT use for:** - General SDK documentation → use "get_sdk_documentation" - Chat SDK documentation → use "get_chat_sdk_documentation" Returns the migration guide content for the specified language and target version.get_general_migration_guideRetrieve general migration guides for cross-cutting PubNub platform changes. **When to use:** - Migrating to a new encryption standard (e.g. 256-bit encryption) - Upgrading push notification setup (e.g. APNs HTTP/2, FCM v1) - Migrating to new API versions (e.g. Access Manager v3, Objects v2) - Replacing deprecated features (e.g. legacy webhooks) **Do NOT use for:** - SDK version upgrades (e.g. JavaScript v7→v8) → use "get_sdk_migration_guide" - General SDK documentation → use "get_sdk_documentation" Returns the migration guide content for the specified slug.how_toRetrieve 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`write_pubnub_appRetrieve 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.manage_appsManages 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.manage_keysetsManages PubNub keysets with operations: get, list, create, update. - 'get': Get a specific keyset information, including its current config (message persistence, App Context, files, presence including presence rules, etc.). 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. Only provided fields are changed. presence.rules replaces the stored rules entirely: before changing rules, call 'get' and send the full list including the existing rules to keep. If 'get' returns presence.rules as "UNREADABLE", the existing rules cannot be read back; tell the user that sending rules will overwrite them and ask before proceeding.get_usage_metricsFetches 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_transactionsmanage_app_contextManages 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.send_pubnub_messageSend 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.get_pubnub_presenceRetrieves 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.- +5 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Ethora MCP Server
{
"mcpServers": {
"ethora-mcp-server": {
"command": "npx",
"args": [
"-y",
"@ethora/mcp-server"
],
"env": {
"ETHORA_API_URL": "YOUR_ETHORA_API_URL_HERE",
"ETHORA_APP_JWT": "YOUR_ETHORA_APP_JWT_HERE",
"ETHORA_B2B_TOKEN": "YOUR_ETHORA_B2B_TOKEN_HERE",
"ETHORA_MCP_AUTH_ISSUER": "YOUR_ETHORA_MCP_AUTH_ISSUER_HERE"
}
}
}
}
Pubnub MCP Server
{
"mcpServers": {
"mcp-server-152": {
"command": "npx",
"args": [
"-y",
"@pubnub/mcp@latest"
],
"env": {
"PUBNUB_API_KEY": "YOUR_PUBNUB_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Ethora MCP Server is categorized under Communication and uses a local stdio subprocess. Pubnub MCP Server belongs to Communication and uses a local stdio subprocess. Pick Ethora MCP Server for communication work and Pubnub MCP Server for communication.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Ethora MCP Server is listed as free. Auth: oauth 2.0. Pubnub MCP Server has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add ethora-mcp-server and mcp-server-152 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Ethora MCP Server has a quality signal of 67/100 (Great) with 5 views, 0 installs and 6 GitHub stars. Pubnub MCP Server has 65/100 (Great) with 0 views, 0 installs and 33 GitHub stars.