AutomateLab AI SEO Magic Button
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AISEO_MCP_PATH | No | Path to local build of ai-seo-mcp | |
| CITATION_MCP_PATH | No | Path to local build of citation-intelligence-mcp |
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 |
|---|---|
| generate_seo_planA | Crawl a site, run a whole-site AEO/GEO audit (via the ai-seo + citation-intelligence engines), and return a portable, agent-executable plan.json plus a markdown checklist. This produces an actionable PLAN, not direct edits. |
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 1 tool
There is only one tool, so no selection ambiguity is possible. Its purpose (crawl + full-site AEO/GEO audit + generate plan.json and checklist) is stated clearly and distinctly.
The single name `generate_seo_plan` follows a clean verb_noun snake_case convention. With one tool there is no risk of mixed conventions.
One tool for an entire 'SEO Magic Button' server is thin, sitting at the low end of the 3-15 range. It is offset by the tool being substantive (crawl + multi-engine audit + plan generation in one call), but there is still only a single entry point.
The stated purpose of producing an actionable plan is covered, but the surface is a one-shot generator with no follow-up operations such as retrieving/list existing plans, checking audit status, or applying/executing the generated plan. The description explicitly disclaims direct edits, so agents may hit a dead end after planning.