Integration · Automate and collaborate

Prismic and Meteor AI agents

Connect Prismic to a Met: search documents, read your site content, prepare changes in a release and send them for review with Prismic's official MCP.

Book a demo See every integration

How does Prismic connect to Meteor?

With the Prismic ready connector, your Met uses Prismic's official MCP server with the account the admin authorizes, and it gets 16 tools. It lists your repositories, content types, locales and releases, searches documents and reads their full content, so it can answer with what your site says. It also creates documents, updates them and uploads images from a link, and all of that is saved in a release to review before it goes out. Publishing a release makes it live, needs the Publisher role and cannot be undone. It lets the owner change a promotion's text on WhatsApp while the team reviews it in Prismic.

What it automates

What a Meteor Met does with Prismic

Answer with what your site says

When a customer asks on WhatsApp about opening hours or a condition, the Met searches the document in Prismic, reads its content and answers with what your team published.

Change a promotion's text

The owner writes the change to the Met. The Met opens the document, creates a release and saves the new version there, so your team reviews it in Prismic before publishing it.

Create a new entry from the model

The Met brings the content type's model, for example a blog post, and creates the document in a release with the fields you dictate.

Upload the campaign image

If the image is at a public link, the Met uploads it to the Prismic library and uses its CDN link in the document.

16 tools

Everything your Met can ask Prismic for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`list_repositories`	Lists the Prismic repositories the connected account can access.
`list_custom_types`	Lists a repository's content types, with their id, label and format.
`list_shared_slices`	Lists a repository's shared slices with their variation names.
`list_locales`	Lists the locales configured in a repository.
`list_releases`	Lists a repository's releases, newest first.
`list_document_versions`	Lists every version of a document, including drafts, published, archived and release versions.
`search_documents`	Searches documents by keyword, with filters for type, locale, status and tags. Returns metadata, not content.
`search_assets`	Searches the asset library by filename, alt text, notes or credits, and returns previews.
`get_document`	Returns a document's metadata and full content, also from a specific version or release.
`get_custom_type`	Returns a content type's field model and an empty template for creating documents.
`get_shared_slice`	Returns a shared slice's full model with all its variations.
`create_release`	Creates an empty release and returns its id to create or update documents inside it.
`create_document`	Creates a document inside a release; missing fields take the model defaults.
`update_document`	Saves a new version of a document inside a release, with the full content.
`upload_asset`	Fetches a file from a URL and uploads it to the repository's library, with its Prismic CDN link.
`publish_release`	Publishes a pending release and makes all its documents live. Needs the Publisher (Manager) role and is irreversible.

The limits

What the Prismic integration does NOT do

We would rather say it here than have you find out during rollout.

It does not publish without the right role. Publishing a release needs the Publisher (Manager) role, makes all its documents live and cannot be undone or unpublished from the chat.
It does not ask you for confirmation in the chat before writing. Creating and updating documents goes into a release; the control is which actions the admin leaves on in Connections.
It does not work if Prismic MCP is off in the repository. An Administrator or Owner turns it on in Settings → Prismic MCP.
It does not publish migration releases. Prismic does not allow publishing them through MCP.
It does not pay your Prismic plan. Usage runs on your account; Meteor does not resell the service.

Before you start

What you need to connect Prismic

1

A Prismic account with access to the repository

The Met only sees the repositories the authorizing account can access. To publish, that account needs the Publisher (Manager) role.
2

Prismic MCP on in the repository

It is on by default in new repositories. If it is off, an Administrator or Owner turns it on in Settings → Prismic MCP; the preparation can take several minutes.
3

Connect it in Met

In Met, open Connections → Prismic → Connect. A Prismic window opens so you sign in and authorize Met. Then you choose which actions stay on.

Frequently asked questions

Questions about Prismic and Meteor

No. Creating and updating documents is saved in a release. It only goes live when someone publishes that release, from Prismic or with the publish action if the admin leaves it on.

Not from the Met. Prismic says the assistant cannot unpublish or undo a publish, so it is best to review the release first.

Wait a few minutes. Prismic is preparing the repository's content for the MCP server; then ask the Met again.

You do, with your own Prismic plan. Meteor does not resell Prismic: the connector uses your company's account.

Step by step