agentaeo-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENTAEO_API_KEY | Yes | Your AgentAEO API key, available at agentaeo.com/agents. | |
| AGENTAEO_MCP_INLINE_POLL | No | Set to '1' to enable long polling inside the run_aeo_audit tool. Note: This may exceed Claude Desktop's ~60s tool execution limit. | |
| AGENTAEO_MCP_DOWNLOAD_DIR | No | The directory where Content Suite ZIPs should be saved when using the download_aeo_content_suite_zip tool. | |
| AGENTAEO_MCP_INLINE_CONTENT_POLL | No | Set to '1' to enable long polling inside the generate_aeo_content_suite tool. Note: This may exceed Claude Desktop's ~60s tool execution limit. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_aeo_auditA | Start an AEO audit for a URL (async). Returns auditId immediately. Then call check_aeo_audit_status every 10–15s until is_complete or free_preview_ready (free tier stops at step 2). |
| check_aeo_audit_statusA | Check status of an AEO audit. Poll until free_preview_ready (free) or is_complete at full report (paid). If paid_pipeline_pending is true, keep polling. |
| check_aeo_content_suite_statusA | Poll Content Suite generation. After generate_aeo_content_suite returns (HTTP 202), call every 15–30s until status is completed or failed. Same X-API-Key as generate. |
| download_aeo_content_suite_zipA | Download the Content Suite ZIP after status is completed (same AGENTAEO_API_KEY as generate). Saves to cwd or AGENTAEO_MCP_DOWNLOAD_DIR. |
| generate_aeo_content_suiteA | Start Content Suite generation (HTML + JSON-LD + llms.txt) for a completed audit — async (returns in seconds with orderId). Poll check_aeo_content_suite_status every 15–30s until completed (often 5–25+ min). Uses AGENTAEO_API_KEY — no shell/curl. Admin QA without Cashfree: adminContentBypass=true + allowlisted key. Otherwise pass orderId after payment. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool has a distinct, non-overlapping purpose: run_aeo_audit initiates an audit, check_aeo_audit_status monitors it, generate_aeo_content_suite starts content generation, check_aeo_content_suite_status monitors that, and download_aeo_content_suite_zip retrieves the result. The descriptions clearly differentiate these workflows, leaving no ambiguity for an agent to misselect tools.
All tool names follow a consistent snake_case pattern with clear verb_noun structure (e.g., run_aeo_audit, check_aeo_audit_status, generate_aeo_content_suite). The naming is predictable and uniform across all five tools, making them easily readable and systematic.
With 5 tools, this server is well-scoped for managing AEO audits and content suites. Each tool serves a specific role in the workflow, from initiation to monitoring to download, and none appear redundant or unnecessary, fitting the domain appropriately without being too sparse or bloated.
The tool set provides complete coverage for the AEO audit and content suite lifecycle: it includes tools to start audits (run_aeo_audit), monitor their status (check_aeo_audit_status), generate content (generate_aeo_content_suite), monitor that generation (check_aeo_content_suite_status), and download results (download_aeo_content_suite_zip). There are no obvious gaps, enabling agents to handle the entire process from start to finish.