Bento MCP

What Bento MCP MCP server does

Bento MCP is built around a self-hosted creator and customer application. Its public product surface includes link-in-bio pages, a store, email marketing, priority messaging, calendars, communities, post scheduling, social insights, Auto-DMs, earnings, settings, checkout, and customer library flows. The application also includes Content Agent, Brain, discovery, routines, multiple workspaces, knowledge and Telegram integrations, and Instagram Trial Reels support.

The repository describes two MCP-related paths. A hosted Bento remote MCP can authenticate through OAuth, and the repository includes a Cursor plugin for that service. The application also includes page-scoped WebMCP. The available material does not provide a list of individual MCP tool names or their input and output schemas, so tool-level behavior should be verified in the linked plugin or deployment documentation.

How it works

The repository is primarily a local, self-hostable application rather than a turnkey hosted service. Local development uses Bun and a Supabase project controlled by the operator. Database migrations run through a guarded script that supports a preview mode before changes are applied. The app can then be started with the development command and checked locally.

For the hosted MCP path, the Cursor plugin signs in to a Bento account with OAuth. It does not use API keys. Users may install the plugin from the Cursor Marketplace or configure the remote MCP URL manually according to the plugin documentation. A separate Grok Build plugin is included as a marketplace package for the same hosted MCP; it does not alter the application runtime.

Setup and configuration

A local setup requires Bun, the Supabase CLI, and a Supabase project. Copy the example environment file before configuring the instance. The repository specifically calls for an independent random WORKSPACE_COOKIE_SIGNING_KEY with at least 32 bytes, along with core Supabase and URL values such as SUPABASE_PROJECT_ID and SUPABASE_DB_URL. Migration execution also requires MIGRATION_CONFIRMATION in the form MIGRATE:<SUPABASE_PROJECT_ID>.

Use the migration script first in dry-run mode, then apply it only after reviewing the result. Optional integrations remain off until their own configuration is supplied. Cloudflare deployment has a separate guide, and the repository provides a coding-agent skill for configuration and verification while leaving provider approvals and external actions under the operator’s control.

Tools and capabilities

The Bento MCP MCP server is associated with a creator workflow that can cover:

• Link-in-bio pages and digital products
• Email marketing, bookings, and customer checkout
• Social post scheduling and social analytics
• Priority messaging and Auto-DMs
• Communities, earnings, and customer libraries
• Workspace, knowledge, Telegram, and creator-agent features

These capabilities describe the application’s public product coverage, not a guaranteed inventory of exposed MCP functions. Provider-backed features require the instance owner’s credentials and approvals.

Limitations and notes

The release is described as a local setup foundation. The repository does not claim fresh-database, provider, MCP/WebMCP browser, or deployment proof. Local checks therefore demonstrate local behavior only and should not be treated as evidence that external providers or a production deployment work.

The public source boundary excludes corporate marketing pages and Bento-only founder operations. The project is AGPL-3.0-only. If a modified version is made available over a network, the license requires corresponding source to be offered to users interacting with it. The hosted remote MCP and local application should also be evaluated separately: the Cursor plugin authenticates to the hosted service, while local setup involves running the application and connecting it to operator-managed infrastructure.