Integration · Automate and collaborate

Sanity and Meteor AI agents

Connect Sanity to a WhatsApp Met: query documents with GROQ, edit drafts and publish your site's content through the official MCP server.

Book a demo See every integration

How does Sanity connect to Meteor?

With the Sanity ready connector, your WhatsApp Met uses Sanity's official MCP server with the account the admin authorizes. It queries documents with GROQ, opens one by its ID and reads the schema, so it answers with the hours, the price or the information your site already publishes. If the admin leaves writing on, it also creates and edits documents: changes go to a draft, never straight to published content, and publishing that draft moves the change into the published content your site shows. Publishing arrives switched on; if the admin turns it off, the Met leaves the draft for your team to review and publish from Sanity Studio.

What it automates

What a Meteor Met does with Sanity

Change opening hours or a price from WhatsApp

The owner sends the Met a branch's new opening hours or a product's price. The Met finds the document, edits the field in a draft and publishes it so the site shows the new value.

Answer with what the site already says

When a customer asks about a service, the Met queries your site's documents with GROQ and replies with the published description, price or opening hours.

Prepare a season's changes

The Met creates a release for the season and adds versions of the documents that change. Scheduling or publishing it stays with your team, in Sanity Studio.

Roll back a draft

If a change was not meant to go out, the Met unpublishes a document and moves it back to draft. Discarding a draft while leaving published content intact starts turned off: the admin turns it on if they want it.

22 tools

Everything your Met can ask Sanity 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
`whoami`	Returns the authenticated Sanity account: name, email, provider and authentication method.
`list_organizations`	Lists the Sanity organizations the account can access.
`list_projects`	Lists the Sanity projects linked to the account.
`get_project_studios`	Gets the Studio applications linked to a Sanity project.
`list_datasets`	Lists the datasets in a Sanity project.
`get_schema`	Gets a deployed schema; without a workspace name, it uses the only active one or the default one.
`list_workspace_schemas`	Lists the deployed schemas for a project and dataset, grouped by source.
`query_documents`	Queries documents with GROQ. Results are not truncated, so it is best to ask only for the fields you need.
`get_document`	Gets a full document by its exact ID. It does not search or filter.
`list_embeddings_indices`	Lists the embeddings indices available for a dataset.
`semantic_search`	Runs a semantic search over an embeddings index.
`create_documents`	Creates one or more documents as drafts, or as a release version when one is given.
`patch_documents`	Edits existing documents, up to 25 per call. Changes go to the draft or the release version, never straight to published content.
`publish_documents`	Publishes one or more drafts.
`unpublish_documents`	Unpublishes one or more published documents and moves them back to drafts.
`discard_drafts`	Discards one or more drafts and leaves published content intact. Starts turned off.
`create_version`	Creates a document version inside a release, separate from the draft and the published content.
`version_discard`	Discards one or more document versions from a release. Starts turned off.
`list_releases`	Lists the releases in a dataset; by default, the active and scheduled ones.
`create_release`	Creates a release to group changes. It does not schedule or publish it: that happens in Sanity Studio or through the Actions API.
`search_docs`	Searches Sanity's official documentation.
`read_docs`	Gets a specific article from Sanity's documentation.

The limits

What the Sanity integration does NOT do

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

It does not ask you for confirmation in the chat before editing or publishing. Publishing arrives switched on; if the admin turns it off in Connections, changes stay in draft until someone publishes them.
It does not schedule, publish, archive or delete releases: Sanity states that happens in Sanity Studio or through the Actions API.
It does not upload images or files, and it does not generate or transform images: those tools are not on this page.
It sees no more than the connected account. If a tool fails or is missing, Sanity asks you to check that the account has permissions on that project and dataset.
It does not pay your Sanity plan. Usage runs on your account; Meteor does not resell the service.

Before you start

What you need to connect Sanity

1

A Sanity account with permissions on the project

Your team's Sanity account, with a role that can read, edit and publish in your site's project and dataset. The Met works with that account's permissions.
2

Connect it in Met

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

Frequently asked questions

Questions about Sanity and Meteor

Not when editing: changes go to a draft. They go out when that draft is published, and publishing is an action that arrives switched on and the admin can turn off in Connections.

It reads the project's deployed schema and queries the document with GROQ, so it uses your site's real field names. It helps to write them down in the skill.

It can edit the field back to the previous value and publish again. Discarding a draft that was not published starts turned off until the admin turns it on. Unpublishing, on the other hand, takes the document out of published content. This page has no tool to go back to an earlier version.

You do, with your Sanity account and plan. Meteor does not resell Sanity or charge for the actions your Met takes there.

Step by step