other
Agility CMS is a headless content management system, and its MCP server lets Neotask fetch, manage, and query content, pages, and models without opening the CMS admin panel yourself for every small task. Requests can go through the REST API, the GraphQL API, or the management API depending on what the task calls for, so pulling a list of published pages and editing a content model draw on whichever interface fits best for that particular job rather than forcing everything through one path. This suits teams managing a site's content structure who want a faster way to check what's published, adjust a model's fields, or pull specific content for review before it goes live to visitors. Because Agility CMS separates content from presentation, changes made through the agent update the underlying content store, and whatever front end consumes that content reflects the change on its own schedule, without the agent needing to know anything about how that front end is built or deployed. It's a way to work with a headless CMS conversationally instead of clicking through an admin interface for routine content tasks that would otherwise eat up a few minutes each time they come up during a normal workday. For teams managing several content types across a growing site, that shortcut adds up over a week of small requests, and it removes the friction that often causes a small content fix to sit unaddressed for longer than it should.
| query_content | Retrieves content items using the REST or GraphQL API. Supports filtering down to exactly what's needed. |
| get_pages | Fetches page structures and their associated content. Useful for checking what's currently published. |
| manage_content_models | Creates or updates content models through the management API. Applies immediately to how content of that type is structured. |
| fetch_page_content | Returns the content tied to a specific page. Good for a targeted review rather than a full export. |
A content editor wants to confirm which blog pages are currently published before a review meeting she's running in twenty minutes. She asks Neotask to pull the list, and the agent queries Agility CMS's REST API for published pages. She walks into the meeting with an accurate list instead of guessing from memory or an outdated spreadsheet someone shared weeks ago. Nobody in the room has to double-check the numbers against the CMS itself, which keeps the meeting on schedule and lets the conversation focus on what to publish next instead of what's already live.
A developer realizes a content model needs an extra field partway through a build, and stopping to open the admin panel would break his focus. Instead, he asks Neotask to add the field through Agility CMS's management API. The model updates, and he continues wiring up the front end against the new field without switching tools or losing his place in the code. The change is ready by the time he needs it, rather than sitting as a task for later, and the rest of the afternoon stays uninterrupted.
Whichever fits the request: REST, GraphQL, or the management API are all available through this integration.
Both. Content models can be managed through the management API, not just queried.
Not entirely, but it covers routine tasks like fetching or querying content and pages so you don't need to open the panel as often.
No, it works across content, pages, and models generally, scoped to whatever your request specifies.
That depends on how your front end consumes the content store, but the underlying content, page, or model update happens immediately.
No, you describe what you need and the agent picks the API that fits, whether that's the REST endpoint, the GraphQL schema, or the management API.
Yes, requests can span multiple content types or models in a project rather than being limited to one at a time.
Yes, requests can be scoped to a specific locale where the underlying content and pages support one.
Yes, the management API used here can also remove or adjust fields that are no longer needed, not just add new ones.