mcp-server

Get a list of available Agility instances.

Get details for a specific Agility component model by ID or reference name. Model ID is preferred.

Get a list of Agility components for a particular instance.

Gets the list of Agility containers (content lists and single items) for a particular instance.

Retrieve a single content item by ID from Agility CMS. Returns the complete item including contentID, properties (state, versionID, dates, referenceName, definitionName), fields object with all field values (field names are CASE-INSENSITIVE - e.g., 'Title' is the same as 'title'), SEO properties, and scripts.

Retrieve a list of content items from an Agility CMS container. Returns items with standard properties (contentID, versionID, state, dates) and a dynamic 'fields' object based on the container schema. Field names are CASE-INSENSITIVE (e.g., 'Title' is the same as 'title'). By default, all configured fields are returned. You can optionally specify a list of field names to return only specific fields.

Get details for a specific Agility content model by ID or reference name. Model ID is preferred.

Get a list of Agility content models for a particular instance.

Get a list of locales for an Agility instance.

Retrieve a specific page by its ID from Agility CMS. Returns complete page details including content zones, SEO settings, visibility, dynamic configuration, and more.

Get a list of Agility page models for a particular instance and locale.

Retrieve a specific sitemap for an Agility CMS instance. Provide either sitemapName OR sitemapID to get a specific sitemap, or omit both to get the default sitemap. Use get_sitemaps first to see available sitemap names and IDs.

Retrieve a list of all sitemaps for an Agility CMS instance. Returns only the channel IDs and names for quick reference. Use this before calling get_sitemap to see available sitemaps.

Initialize a media asset upload and receive a temporary signed URL. This URL can be used to upload files to Agility CMS through the /api/uploadAsset endpoint. The URL expires in 5 minutes.

Save a new or existing Agility component model. Always check the listing of current component models before creating a new one. Take note of the different field types available, especially the various Linked Content types. Include all appropriate properties on all fields as undefined properties will be interpretted as empty or null values.

Save a new or existing Agility container. Always check the listing of current containers before creating a new one.

Save or update one or more content items in Agility CMS.

BEFORE SAVING: Retrieve the container's content model to understand field types and requirements. Pay special attention to image/attachment fields and linked content fields to ensure correct value formatting.

FOR NEW ITEMS (contentID = -1):

• Provide referenceName and fields object with content data

• For NEW attachments: (1) Call initialize_media_upload to get an uploadUrl, (2) POST file to that URL, (3) Use the returned asset URL in the attachment field

FOR UPDATES (contentID > 0):

• Include ALL fields, not just changed fields

• Include properties.versionID with the current version ID

• Recommended: First call get_content_item to retrieve current field values and versionID

• For EXISTING attachments, use the current URL directly

Returns an array of content IDs representing the saved items.

Save a new or existing Agility content model. Always check the listing of current content models before creating a new one. Take note of the different field types available, especially the various Linked Content types. Include all appropriate properties on all fields as undefined properties will be interpretted as empty or null values.

Save a new page or update an existing page in Agility CMS. This tool supports 4 page types:

1. static - Regular content pages with zones and components

2. dynamic - Pages generated from a content list with dynamic formulas, as well as zones and components

3. folder - Organizational containers with no content

4. link - Redirect pages that point to other URLs

PREREQUISITES - Before creating a page, you MUST gather:

1. Locale - Use get_locales to get valid locale codes for the instance

2. Sitemap/Channel - Use get_sitemaps to list available sitemaps and get their IDs

3. Page Model - Use get_page_models to list available page models and their names. The modelName field is REQUIRED for static and dynamic pages.

4. Parent Page (if applicable) - Use get_sitemap to find the parent page ID by name/path. Do NOT guess parentPageID.

5. Component Models (for static/dynamic pages with zones) - Use get_component_models to list available components, then get_component_model_details to get field definitions for each component you want to add.

CRITICAL - Adding Components to Pages (static/dynamic pages): When adding components to page zones, you can create the content items DIRECTLY in the page JSON - DO NOT call save_content_items first!

For NEW components, embed the full content item in the zones array (do NOT include contentID), and be sure to include the correct componentModelID for the component model:

For EXISTING components (already created separately), just reference by ID:

The save_page tool will create both the page AND all embedded content items in a single operation.