Runs persisted GraphQL queries against a Contentful space to pull structured entries, and fetches a CMA token for management-level calls.
2actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Retrieve a Contentful Management API (CMA) access token.
Each card is one request a support team gets, and the Contentful graphql actions Ayro runs to close it.
Ayro runs a registered GraphQL query with the customer's parameters as variables and reads the fields back, so a question about a policy, a product, or a help article is answered from the entry itself.
With Automatic Persisted Queries, the first call registers the query text against its SHA256 hash and every call after that sends only the hash and the variables, which keeps a query Ayro runs constantly cheap.
Ayro retrieves a Contentful Management API access token on demand, so a call that needs management authorization has a valid credential to work with instead of failing partway through on an expired one.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Contentful graphql actions it has and picks the ones a request needs.
Authorize the Contentful graphql account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Contentful graphql actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeContentful graphql · Ayro
What can you do in Contentful graphql without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Contentful graphql.
Not with these actions. The connected toolkit exposes Get CMA Token and GraphQL Content API Persisted Query, so Ayro reads content and can fetch a management token, but nothing in the toolkit creates, updates, or publishes an entry.
All 2 actions your agent can call on Contentful graphql, straight from the live MCP connection.
Retrieve a Contentful Management API (CMA) access token.
Execute a GraphQL query using Automatic Persisted Queries (APQ).
Same connection, same setup. Pick the next one your team already uses.
Sends documents for signature, tracks where any of them stand, extends missed expiry dates, and manages brand-scoped custom fields.
Adds recipients and fields to a document, sends it for signature, resends when it stalls, and reports where signing stands.
Reports envelope signing status, sends agreements from templates, corrects envelopes already out for signature, and runs bulk sends.
Finds files people describe rather than name, writes documents into the right folder, grants access on request, and keeps folders tidy.
Sends documents in for parsing, explains why one came back stuck, reprocesses a batch after a template change, and routes the parsed data onward.
Sends a document or template out for signature, reports who has signed, chases the ones who have not, and cancels a request that should stop.

Authorize the account and your agent has all 2 actions from the first conversation.
