mcpbizapps
Book a demo

Content and digital assets · Available

Sanity for Claude, ChatGPT and Copilot

Editors and developers can ask Claude, ChatGPT or Copilot which Sanity documents have unpublished changes, what is in an upcoming release, where a shipping note mentions two-day delivery and which fields a document type requires. Datasets follow each person's role, and anything new is prepared as a draft. Because every Sanity schema is custom, the guided pilot opens with a review of yours.

Start a pilot What it can do
Status
Available
Setup
Guided pilot with your team
AI assistants
Claude, ChatGPT, Copilot Studio
Access
By role, view only or with approvals

Ask in a sentence

What can your team ask Sanity?

Questions from content editor, editorial lead, product marketing manager and others, answered from live Sanity data and only for the people allowed to see them.

Records it works with

  • Documents
  • Document types
  • Datasets
  • Releases
  • Assets
  • Projects
  • Content editor

    “Which article documents in the production dataset have unpublished changes?”

  • Editorial lead

    “Which documents are in the Black Friday release, and which still need review?”

  • Product marketing manager

    “Find every product document whose shipping note mentions two-day delivery.”

  • Web developer

    “Which fields does the author document type require, and which are references?”

  • Localization manager

    “Which documents have Spanish versions that are older than the English ones?”

  • Brand manager

    “Which image assets have an empty alt text field?”

Changes, governed

What the assistant can prepare in Sanity

The assistant never saves on its own. It prepares the change, the person checks the preview and confirms, and anything above your limits waits for an approver.

  1. 1 Prepare The assistant drafts the change from the request.
  2. 2 Preview and confirm The person sees exactly what will change.
  3. 3 Approve Above your limits, a second person decides.
  4. 4 Saved and logged Written to Sanity under a named person.

  • Create a draft document from a brief

    The document stays a draft, and an editor publishes it from Sanity Studio.

  • Add documents to an upcoming release

    The editorial lead confirms which documents join the release.

  • Update a field across a set of drafts

    A field change across more than twenty-five drafts waits for the editorial lead.

Example rules. During the pilot you set the limits, the approvers and which roles may prepare each change.

Why it needs care

Governance built for Sanity

One Sanity dataset can feed product pages, apps and campaigns, and a release sends many changes live together. The assistant only writes drafts. Bulk edits over twenty-five drafts need the editorial lead, who also confirms what joins a release, and developers can be kept to staging. The log ties each draft to the person who asked for it.

Security and data handling

  • Sign-in by work email

    Only people you invite, with a one-time code. No shared logins.

  • Roles per tool

    Each role reaches only the Sanity records it needs.

  • View only, if you prefer

    Admins can keep a connection to lookups with one switch.

  • A preview first

    Every change is shown in full before anything is saved.

  • Approval rules

    Above your limits, a second person approves the change.

  • One audit log

    Every request tied to a named person, ready for review.

Setup

How Sanity gets connected

We connect Sanity for your team in a guided pilot, on the same gateway every app uses. No code on your side.

  1. 01

    Agree the questions

    We list the Sanity questions and changes your team needs, and who may use each.

  2. 02

    Connect with your admin

    Your Sanity administrator creates a dedicated integration user with only that access.

  3. 03

    Test with your people

    A small group tries it in Claude, ChatGPT or Copilot while we tune the tools.

  4. 04

    Roll out with rules

    Roles, approval limits and the audit log are in place before everyone joins.

Then people use it from the assistant they already have

Sanity questions

Does the assistant follow our custom Sanity schema?

Yes. Sanity schemas are designed by each team, so the assistant reads your document types, fields and references and uses those names in its answers. We review the schema together at the start of the pilot.

Can it work with Sanity releases?

It can list the documents in a release, show which still have open changes and prepare adding a document to a release for the editorial lead to confirm. Publishing the release stays with your editors.

Can it read more than one dataset?

Yes, if you include them. Many teams keep a production and a staging dataset, and roles can let developers ask about staging while editors work only with drafts in the production dataset.

Does mcpbizapps keep a copy of our Sanity data?

No. When someone asks a question, mcpbizapps reads the answer live from Sanity through a dedicated integration user and returns it without storing it. The audit log records who asked, which tool ran and the result, with personal fields and free text removed.

Sanity is a trademark of its owner. mcpbizapps is not affiliated with Sanity; the name describes the connection only.

Related

Often connected alongside Sanity

All Content and digital assets apps

Part of Work, content and legal: Projects, knowledge, files, content, contracts and matters.

Start

Bring Sanity into your AI assistant

Tell us how your team uses Sanity, and we will plan a guided pilot around your own questions.

  • We agree the tools and approval rules with you
  • Your admin creates the integration user; no code
  • Business data is read live and not stored

Start a Sanity pilot

We use these details only to reply to you. They are emailed to our team and not stored on this website. See website privacy.

Last updated