Citedy SEO Agent
Server Details
AI marketing: SEO articles, trend scouting, competitor analysis, social media, lead magnets
- Status
- Unhealthy
- OAuth
- Requires browser extension
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- citedy/citedy-seo-agent
- GitHub Stars
- 18
- Server Listing
- SEO Content Autopilot by Citedy
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Changed
shorts.script1 field changed- added
Input schema / properties / favorite_idAdded value: +{ + "description": "Optional favorite (product identity) ID from ai_favorites — use this to scope gaps/KB to a specific product. Added in UGC Strike v2 P1-0; fully backward-compatible (absent → same legacy behaviour).", + "format": "uuid", + "pattern": "^([0-9a-fA-F]{8}-[0-9a-fA-F]{4}-[1-8][0-9a-fA-F]{3}-[89abAB][0-9a-fA-F]{3}-[0-9a-fA-F]{12}|00000000-0000-0000-0000-000000000000|ffffffff-ffff-ffff-ffff-ffffffffffff)$", + "type": "string" +}
1 tool update
- Added
shorts.publish
1 tool update
- Added
gsc.report
4 tool updates
- Added
article.delete - Changed
article.generate1 field changed- added
Input schema / properties / auto_publishAdded value: +{ + "description": "Publish article immediately after generation. When false, article stays as draft (status=generated). Default uses tenant setting.", + "type": "boolean" +}
- Added
article.publish - Added
article.unpublish
2 tool updates
- Changed
article.generate2 fields changed- added
Input schema / properties / wait_for_completionAdded value: +{ + "default": true, + "description": "Wait synchronously for article completion before returning", + "type": "boolean" +} - changed
Input schema / requiredPrevious value: -[ - "language", - "size", - "mode", - "enable_search", - "illustrations", - "audio", - "disable_competition" -]New value: +[ + "language", + "size", + "mode", + "enable_search", + "illustrations", + "audio", + "disable_competition", + "wait_for_completion" +]
- Added
article.get
52 tool updates
- First observed
adapt.generate - First observed
agent.health - First observed
agent.me - First observed
agent.status - First observed
article.generate - First observed
article.list - First observed
brand.scan - First observed
brand.scan.get - First observed
competitors.discover - First observed
competitors.scout - First observed
gaps.generate - First observed
gaps.list - First observed
ingest.batch - First observed
ingest.content.get - First observed
ingest.create - First observed
ingest.get - First observed
leadmagnet.archive - First observed
leadmagnet.generate - First observed
leadmagnet.get - First observed
leadmagnet.publish - First observed
personas.list - First observed
products.create - First observed
products.delete - First observed
products.list - First observed
products.search - First observed
schedule.gaps - First observed
schedule.list - First observed
scout.reddit - First observed
scout.reddit.result - First observed
scout.x - First observed
scout.x.result - First observed
seo.headings.check - First observed
seo.internal_links.plan - First observed
seo.links.analyze - First observed
seo.meta_tags.check - First observed
seo.og_image.generate - First observed
seo.og.preview - First observed
seo.robots.check - First observed
seo.schema.validate - First observed
seo.sitemap.check - First observed
session.create - First observed
settings.get - First observed
shorts.avatar - First observed
shorts.generate - First observed
shorts.get - First observed
shorts.merge - First observed
shorts.script - First observed
social.publish - First observed
webhooks.delete - First observed
webhooks.deliveries - First observed
webhooks.list - First observed
webhooks.register
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
AI marketing — content generation, competitor analysis, social publishing.
AI marketing — content generation, competitor analysis, social publishing, and strategy.
AI-powered SEO and marketing: keyword research, SERP analysis, and content optimization tools.
AI business intelligence: competitor analysis, web scoring, reviews, market research
Related MCP Servers
- AlicenseAqualityBmaintenanceMarketing Analytics AI - MCP server providing AI-powered tools and automation by MEOK AI Labs515MIT

Sociality MCPofficial
AlicenseNot gradedqualityDmaintenanceSocial media analytics, post insights, and competitor benchmarking for AI agents.6MIT- AlicenseAqualityDmaintenanceAI tools for short-form video creators (TikTok, Instagram Reels, YouTube Shorts, Facebook Reels) — viral trend search, video analysis info, content strategy use cases.3551MIT
- FlicenseBqualityDmaintenanceProvides comprehensive SEO analysis by crawling websites and generating AI-powered keyword insights, search volume data, and competitor strategies. It delivers detailed reports on keyword clusters and commercial intent to help optimize digital marketing workflows.11-
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
The tool set has significant ambiguity and overlap, particularly in the polling/status-checking tools (e.g., article.get, brand.scan.get, ingest.get, leadmagnet.get, scout.reddit.result, scout.x.result, shorts.get) which all serve similar purposes but are scattered across different domains. Additionally, tools like 'agent.status' and 'agent.health' have overlapping operational checks, and 'seo.meta_tags.check' vs 'seo.og.preview' could be confused for meta analysis. While some tools are distinct, the overall set is cluttered with redundant patterns.
Naming is mostly consistent with a clear verb_noun pattern (e.g., article.generate, brand.scan, gaps.list) and uses snake_case throughout. However, there are minor deviations like 'agent.me' (which uses a pronoun instead of a verb) and 'shorts.avatar' (noun_noun instead of verb_noun), and some tools have dot-separated prefixes (e.g., seo.schema.validate) that add slight inconsistency. Overall, the naming is predictable and readable.
With 58 tools, the count is excessive for a single server, indicating poor scoping and likely bloat. Many tools could be consolidated (e.g., polling tools into a generic status check) or split into separate servers for distinct domains like SEO analysis, content generation, and social media. This high number makes the tool surface overwhelming and difficult for agents to navigate efficiently.
The tool set covers a broad range of SEO and content marketing operations, including article generation, SEO checks, competitor analysis, social media scouting, and video creation, with good CRUD coverage in areas like articles and webhooks. However, there are minor gaps, such as no direct update tools for articles or settings (only get/delete/publish operations), and some domains like lead magnets lack full lifecycle management (e.g., no update tool). Overall, the surface is largely complete for its intended purpose.