Citedy MCP MCP server

Citedy MCP Server provides an endpoint for AI agents to access Citedy's SEO and content marketing tools. It enables autonomous agents to perform competitor analysis, content gap identification, SEO auditing, and content generation using multiple AI providers. The server supports a full workflow from intelligence gathering to auto-publishing and social amplification, allowing agents to execute SEO strategies without manual intervention.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

OAuth sign-inEndpoint checked 2026-10-05Operated by Citedy

MCP endpoint (Streamable HTTP)

https://mcp.citedy.com/mcp

Vendor documentation

What you can do with it

Analyze competitor SEO strategies and identify content gaps
Generate SEO-optimized articles using multiple AI providers
Auto-publish content to custom domains and social media channels
Perform technical SEO audits including robots.txt and schema validation

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http citedy-mcp https://mcp.citedy.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add citedy-mcp --url https://mcp.citedy.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable citedy-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "citedy-mcp": {
      "url": "https://mcp.citedy.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "citedy-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.citedy.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start citedy-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "citedy-mcp": {
      "type": "http",
      "url": "https://mcp.citedy.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http citedy-mcp https://mcp.citedy.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "citedy-mcp": {
      "url": "https://mcp.citedy.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "citedy-mcp": {
      "serverUrl": "https://mcp.citedy.com/mcp"
    }
  }
}

See all 782

Do you run Citedy MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing