Bagel is a product intelligence platform that turns customer calls, tickets, CRM notes, and surveys into evidence linked to product ideas.
It can be connected to Agen.co two ways, matching the Official / In-house filter in the connector picker:
- Official — Agen.co connects through Bagel's own hosted MCP server. Each user signs in with their Bagel account, and no API token or OAuth app is needed.
- In-house — Agen.co wraps the Bagel REST API through its own integration layer, so agents can read ideas and evidence, export them, and send feedback and call recordings, using one Bagel API token.
Prerequisites
Prerequisites
- A Bagel account for each user who connects. Sign-in happens on Bagel's login page,
login.getbagel.com.
- In the Agen.co portal, go to Connectors → My connectors and click Add connector.
- Search for
Bageland select it. At the top of the Add Bagel panel, keep Official selected. - Fill in the field:
| Field | Required | Description |
|---|---|---|
| Instance Slug | Yes | Namespaces this instance. It prefixes each imported tool as slug__tool, so several instances of the same MCP server can coexist. Use lowercase kebab-case, for example bagel. You can change it later from the connector's settings. |
- Click Connect. You're redirected to Bagel to sign in and approve access. Agen.co registers its own OAuth client with Bagel automatically, so there's no Client ID or Client Secret to enter.
- Back in Agen.co, the panel shows Select the tools to import from Bagel. with a toggle for each tool, all on by default. Turn off any tool you don't want, then click Add. The connector is created and its tools imported only when you click Add, even if the Bagel sign-in page reported success.
The tool list comes from Bagel's MCP server, not from Agen.co. Review it on the tool selection screen before you click Add.
Enabling the Bagel connector isn't enough on its own. Tool calls remain denied until you create a policy that grants access to the specific tools you want to expose.
Integrating Bagel with Frontegg lets your agents read product ideas and customer evidence, export them for a date range, and send new customer feedback and call recordings into Bagel for analysis. The connector authenticates with a single Bagel API token.
Prerequisites
Prerequisites
- A Bagel account with access to the Bagel app and its settings
- Permission in your Bagel account to generate an API token
Go to app.bagel.ai and sign in to the Bagel account you want the connector to use.
Open the app settings and generate a new API token. Copy the token and store it securely.
The token is tied to one Bagel account, and every call the connector makes runs against that account. Bagel tokens carry no scopes, so the same token covers reading ideas and evidence and sending feedback.
Once you have your API token, enter it in the integration configuration page of the Frontegg portal:
- Open the Frontegg portal and navigate to [ENVIRONMENT] → Integrations → Bagel.
- Paste the token into the API Token field. Paste the token only: the connector adds the
Bearerprefix itself. - Click Save.
Keep your credentials secure
Keep your credentials secure
Never share or commit your API token to version control.
- Feedback is filtered without an error. When you send feedback or call recordings, Bagel drops items it can't accept and still reports the request as successful. Check how many items the response says were filtered out, and resend the rejected ones after fixing them. Every item must be tied to a customer account, and every call recording needs a link to the call and at least one participant.
- Evidence review states are inconsistent in Bagel's API. You filter evidence by
inReview,validated,declined, orunassigned, but evidence records can report a different set of states (inReview,assigned,dismissed). Match on the states a record returns, not on the filter names. - Exports return everything at once. An export returns every idea or piece of evidence in the date range in a single response. Keep the range narrow on large accounts.
- Pages are capped. Lists return up to 1,000 items per page (500 by default).
- Idea and evidence IDs have a fixed shape. They are 24-character hexadecimal IDs, and other values are rejected before the request reaches Bagel.