MCP setup

Use a client that supports remote MCP over Streamable HTTP and authorization headers. The endpoint is:

https://api.vibeupdate.app/mcp

The connection requires an Agent Token and active access on its owning account. The token can manage all apps and releases in that account, including publishing Required updates.

Configure the connectionCopy Anchor Link

1. Create and securely save a token from Agent tokens in the dashboard.
2. Add the endpoint as a remote Streamable HTTP server in your agent's MCP settings.
3. Configure Bearer authorization through that client's private credential storage.
4. Connect and start with a read-only request to list your apps. Check that you see the expected account's apps before allowing changes.

Some clients use a JSON configuration shaped like this. Adapt it to your client's documented format and keep the real token out of shared files:

{
  "mcpServers": {
    "vibeupdate": {
      "url": "https://api.vibeupdate.app/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_AGENT_TOKEN"
      }
    }
  }
}

YOUR_AGENT_TOKEN is an illustrative placeholder, not a working credential. Protocol version 2025-11-25 is supported. You do not need a local stdio bridge or a legacy HTTP+SSE endpoint.

Keep app identifiers distinctCopy Anchor Link

MCP tools use the internal app id returned by the app list, even when their argument is named appId. The mobile SDK instead uses the public appId. Ask the agent to obtain the app's SDK setup when configuring the mobile integration rather than substituting the internal ID.

A connected agent is not automatically limited to drafts. Review publishing and deletion actions before approving them. Token permissions explain the scope.

If the connection failsCopy Anchor Link

A missing, expired, or revoked token cannot authenticate. An access error can also mean that the owning account lacks active VibeUpdate access; replacing a valid token will not fix that. See Account and access.

A successful HTTP response does not necessarily mean an MCP tool succeeded. Clients must check the tool result for isError and read its message before reporting an operation as complete.