8 MCP tools for organizing content into projects, groups, and folders. Create hierarchical structures and move articles between folders.
Content is organized in a four-level hierarchy: Project > Group > Folder > Articles. A project is the top-level container (e.g., a content cluster or campaign). Groups subdivide projects into logical sections. Folders hold individual articles and can be moved between groups.
aeo_list_projects
List all projects for a domain with their nested groups, folders, and article counts. Returns the full organizational tree in a single call.
Create a new top-level content project for a domain. Projects are the highest level of organization - use them for content clusters, campaigns, or major topic areas.
Create a group within an existing project. Groups subdivide projects into logical sections - for example, a content cluster project might have groups for "Eligibility Guides", "How-To Articles", and "FAQ Pages".
Create a folder within a group. Folders are the lowest organizational level and directly contain articles. Each folder typically holds one article and its related assets.
Parameters
Name
Type
Required
Description
group_id
string
Required
Parent group UUID
name
string
Required
Folder name
description
string
Optional
Folder description
icon
string
Optional
Emoji icon for the folder
color
string
Optional
Hex color code
Example
json
aeo_create_folder({
group_id: class="code-string">"grp-def-456",
name: class="code-string">"New York CDPAP",
description: class="code-string">"NY-specific CDPAP eligibility and enrollment",
icon: class="code-string">"📄"
})
Example Response
response
{
class="code-string">"folder_id": class="code-string">"fld-ghi-789",
class="code-string">"group_id": class="code-string">"grp-def-456",
class="code-string">"name": class="code-string">"New York CDPAP"
}
aeo_update_project
Update project metadata. Only provided fields are changed - omitted fields remain unchanged. Set status to archived to hide a completed project from active views.
Move an article to a different folder. Use this to reorganize content across the project hierarchy without re-creating the article. The article retains all its content and metadata - only its folder assignment changes.
{
class="code-string">"message": class="code-string">"Article moved successfully",
class="code-string">"execution_id": class="code-string">"exec-xyz-001",
class="code-string">"folder_id": class="code-string">"fld-ghi-789"
}
Typical workflow: aeo_create_project → aeo_create_group → aeo_create_folder → save articles → use aeo_move_article to reorganize as the cluster evolves. Use aeo_list_projects at any time to see the full tree.
