Connect Pubb with MCP.

Connect your assistant

Use a coding assistant that supports remote Streamable HTTP MCP servers and OAuth sign-in. You do not need to install an MCP package or run a local MCP server.

1. Open your application in pubb and go to Integrate → MCP.
2. Add the URL below as a remote MCP server in your assistant’s settings.
3. Follow the sign-in link, sign in to your pubb account and select your application. Complete two-factor authentication if enabled.
4. Review the permissions and allow access. You can optionally allow a fixed public test message when your assistant requests that permission.

https://app.pubb.io/mcp

If your assistant uses a JSON MCP configuration, use this format. Other assistants provide a URL field or their own remote-server settings.

{
  "mcpServers": {
    "pubb": {
      "url": "https://app.pubb.io/mcp"
    }
  }
}

An assistant that supports only local stdio servers cannot connect directly. You can still use the copyable AI integration prompt.

Start the integration

Open your project in your coding assistant and copy the application-specific request from Integrate → MCP. Or start with this prompt:

Integrate pubb realtime messaging into this project using the connected pubb MCP server. Read get_app_config and get_integration_guide first, and confirm the selected application is the one I want to use. Inspect the repository's stack and follow its conventions. Implement the subscriber and trusted backend publisher. Keep the application secret in local server configuration; never ask me to paste it into chat or expose it in client code. Run the project's existing checks and explain how to verify delivery from my backend to a connected subscriber. Publish an MCP test only if I request it.

The assistant reads the selected application’s ID, public key and endpoints, then follows the integration guide for your stack. If it reports a different application, reconnect and select the intended one before making changes.

MCP sign-in does not require your application secret and no MCP tool returns it. Your project’s own backend still needs its publishing credential: add that locally to server configuration, keeping it out of chat and client code.

Permissions and tools

Each connection grants access to one application. Public settings and integration instructions are available after approval; test publishing requires an additional permission that you choose during setup.

The assistant can also read public configuration and guide resources, or use the integrate_pubb prompt. It edits your project through its own coding tools. MCP does not create applications, retrieve secrets or publish arbitrary messages.

Test your integration

1. Connect your subscriber or Live console to the selected application and wait for its notifications subscription to succeed.
2. If you granted test permission, ask the assistant to call publish_test_event. It sends message.sent with {"message":"Hello from pubb MCP!"}.
3. Confirm receipt at the subscriber. A successful acceptance response alone does not prove delivery.
4. Publish an event from your project’s own trusted backend and confirm it reaches the client too.

MCP tests use your workspace quota and do not mark your project integrated. They cannot verify that your backend publisher is configured correctly. The tool uses a UUID idempotency key; reuse the same key for retries within 24 hours, including after a timeout.

Manage access

Open Settings → MCP connections to see the assistants you authorized across your applications and workspaces. Choose Revoke access to stop that connection immediately. You can also manage connections from the application’s Integrate → MCP → Your assistant connections list.

Access is also tied to the dashboard session that approved the connection. Signing out or session expiry stops it; removing workspace access or deleting the application stops it too. Reconnect from your assistant when authorization expires.