Connect Migma to Algolia: Use Search Results in Your Emails

Your Algolia index already holds articles, products, or other content you want to share. Connect that index to Migma, and you can ask Migma to search it while preparing an email.

For a newsletter, find three useful articles, check their titles and links, then ask Migma to turn those results into a branded draft. For a store, use the same approach with an approved product catalog.

The connection uses Algolia Productivity MCP, OAuth, and Migma's custom connectors. MCP lets Migma call Algolia's read-only search tools. We verified a read-only lookup through an authorized Algolia connection on November 2, 2026.

Choose what Migma should search

Start with one existing Algolia index containing content suitable for the email. An index of published articles is a useful first choice.

Check that its records have the fields you need. Article titles, summaries, and destination URLs help Migma choose and describe useful content. For products, check names, product-page links, and the details you want included in the email.

Migma can retrieve only data present in the index. Connecting it does not update old records or fill missing fields. Check your indexing process if an article is absent or a product detail is outdated.

Algolia Productivity MCP provides read-only access through the signed-in user's existing Algolia permissions. Those permissions can cover multiple applications and indices. Choose an account whose access is appropriate for the brand, and review access before approving.

Enable Productivity MCP in Algolia

In the Algolia dashboard, open Generative AI → MCP Servers → Productivity and check that Enabled is selected.

The service URL is https://mcp.algolia.com/mcp. You can enter it directly in Migma; no clipboard operation or Cursor installation link is needed. Sign-in controls access to your Algolia data.

Algolia also offers a separate Public MCP setup for curated indices. This article uses the Productivity path we tested in Migma.

Add Algolia to your Migma brand

Open My Brands in Migma and select the brand that should use this content. You need to own the brand to manage its custom MCP connections.

Choose Connectors, then Browse all under Design tools. Click Add Custom in the connector catalog.

Enter these settings:

Open Advanced settings and enter public in Scope (optional). Leave OAuth Client ID, OAuth Client Secret, Auth URL, and Token URL empty. The scope name public does not mean that private records become public or that access is limited to one index.

Use the shared Productivity endpoint and leave client credentials empty.

Click Add and Test. Sign in to Algolia if prompted and review the account and access. If Migma presents Tool permissions, review the individual choices:

• Set the search tools you need to Needs approval for your first check.
• Choose Always allow only for tools you want Migma to use without asking each time.
• Set unused tools to Never allow.

Some lookup tools may initially show Always allow. The form's Always Ask setting does not override individual tool choices. Check each one, then choose Save and enable when offered.

For connection management and other custom data sources, read External MCP Servers.

Verify a real result before requesting a design

Open an existing email chat for the same brand. Choose Tools and connectors → Connectors in the composer and check that Use connectors is on. Use an existing chat for this check because New Email starts the email creation flow. Replace the application, index, and topic in this request with your own:

Use only Algolia Productivity to search index [index name] in [application name]
for "year in review". Return at most three matches. Use this index only.
Return each article's exact title and destination URL.
Use only information returned by the search tool.
Return the results in chat. Do not create, edit, export, or send an email.
If the tool is unavailable, say so rather than substituting a web search.

Approve the request if Migma asks. Choose a topic you know exists in your index, check the returned titles, and open the links.

A working connection can still return unsuitable content if you selected the wrong index or searched for a topic the records do not cover. If a title or URL is missing, inspect the source record before using it in an email.

Turn the checked results into a newsletter

Once the search results look right, describe the reader and purpose:

Create a new, separate newsletter draft for subscribers interested in practical email design.
Leave the existing emails unchanged.
Use only the articles returned by the search that we just checked.
Write a short introduction for each and use its exact destination URL.
Use this brand's style. Do not invent article claims or send the email.

Review the draft on the canvas. Compare the summaries with the source pages, confirm every link, and adjust the order and design for your audience.

This connection supplies search context. It does not import contacts or establish an automatic newsletter trigger. Sending, scheduling, and exporting remain separate actions after review.

Frequently asked questions

Is Algolia a built-in Migma connector?

Use Add Custom in the brand's connector catalog. This guide connects Algolia Productivity MCP through that existing flow.

Do I need to paste an Algolia Admin API key into Migma?

This Productivity MCP flow uses OAuth2 at https://mcp.algolia.com/mcp, with scope public. Leave the client ID and client secret empty and sign in when prompted. You do not paste an Admin API key into Migma.

Can I use the same source for every brand?

Migma saves this connection on the selected brand. Add it only to brands that should use those records, and review access separately for each.

Start with one index and one newsletter topic. Verify the returned results, then ask Migma to turn the checked material into your first draft.

Frequently Asked Questions