If you’ve ever managed a serious content operation, you know the drill. Google Search Console in one tab. Ahrefs in another. WordPress admin in a third. A spreadsheet tracking your content calendar. Another spreadsheet mapping keyword clusters.<\/p>\n
And somewhere in the chaos, you’re trying to figure out which of the 200 keyword opportunities you identified last week actually deserve a 2,000-word article.<\/p>\n
It’s death by context switching.<\/strong> Every tab is a silo. Every tool speaks its own language. Your actual strategic thinking — deciding what to write, when to publish, and how to outrank the competition<\/em> — gets buried under operational overhead.<\/p>\n What if you could manage all of it from a single conversational interface?<\/p>\n In this guide, we’ll build an MCP server<\/strong> that connects AutoRank’s SEO intelligence directly to Claude Code. By the end, you’ll have a working server that turns natural language commands like “find content gaps against this competitor and queue articles for the top 5 opportunities”<\/em> into real SEO actions.<\/p>\n The Model Context Protocol<\/a> (MCP) is an open standard from Anthropic that defines how AI assistants connect to external tools. Think of it as USB-C for AI<\/strong> — a universal interface that lets any AI assistant plug into any service without custom glue code.<\/p>\n The key insight: MCP separates AI reasoning<\/em> from tool execution<\/em>. Your AI assistant decides what<\/strong> needs to happen. Your MCP server handles the how<\/strong> — calling APIs, transforming data, returning results.<\/p>\n For SEO teams, this is transformative. Instead of bouncing between dashboards, you describe your intent:<\/p>\n The AI orchestrates the right API calls through your MCP server automatically.<\/p>\n Rank Tip:<\/strong> MCP servers run locally on your machine. Your API tokens never leave your environment, and you control exactly which capabilities to expose. Security-conscious teams can audit every line of the bridge code.<\/p><\/blockquote>\n The data flow is simple. Three components, two connections:<\/p>\n Claude Code<\/strong> sends structured requests over STDIO (standard input\/output). Your server receives them, calls the AutoRank API over HTTP, and returns structured responses. The AI never touches the API directly.<\/p>\n This gives you three advantages worth noting:<\/p>\n MCP servers expose Tools<\/strong> (executable functions), Resources<\/strong> (read-only data), and Prompts<\/strong> (reusable templates). For this guide, we’re building three tools that cover the core SEO workflow:<\/p>\n These three tools create a complete loop: research -> prioritize -> execute<\/strong>. That’s the workflow that actually moves rankings.<\/p>\n Rank Tip:<\/strong> The You’ll need Node.js 18+<\/strong> and an AutoRank API token<\/strong> (grab yours from Dashboard > Settings).<\/p>\n Update Your project structure should now look like this:<\/p>\n Create Start with the imports and configuration:<\/p>\n The Rank Tip:<\/strong> The Before wiring up tools, we need a reusable function for authenticated requests to AutoRank. Every tool will call this instead of using This handles authentication, query parameters, JSON serialization, and error reporting in one place. Every tool handler becomes a thin wrapper around this function.<\/p>\n Here’s where MCP gets interesting. The This tool accepts any blog URL and returns a content gap analysis — keyword opportunities, competitive insights, and topics the target site is missing or underserving.<\/p>\n Notice the pattern: call This tool pulls AI-ranked keyword clusters for a domain — sorted by estimated traffic impact, with search volume, difficulty scores, and current positions.<\/p>\n Rank Tip:<\/strong> The This is where research becomes action. This tool queues an article for AI generation — AutoRank handles the outline, draft, SEO optimization, and scheduled WordPress publishing.<\/p>\n That’s all three tools registered. Notice how little code changes between them — the The last piece: wire up STDIO transport so Claude Code can communicate with your server. Add this at the bottom of Now compile and verify:<\/p>\n What you should see:<\/strong> No errors. A Tell Claude Code where to find your server by adding it to Restart Claude Code. You should see the three AutoRank tools ( Rank Tip:<\/strong> Use an absolute path<\/strong> in the Here’s where the payoff hits. Open Claude Code and start talking naturally. The AI maps your intent to tool calls automatically.<\/p>\n Try this prompt:<\/p>\n “Analyze competitor.com for content gaps. Focus on topics where they rank on page 2 — those are the easiest to overtake.”<\/em><\/p><\/blockquote>\n Claude calls “Find keyword opportunities in the product-photography cluster with search volume above 200.”<\/em><\/p><\/blockquote>\n This hits “Queue an article about AI headshots for LinkedIn targeting ‘ai headshot generator for linkedin’. Schedule it for next Monday, professional tone.”<\/em><\/p><\/blockquote>\n The The magic is chaining all three in a single conversation:<\/p>\n “Analyze myblog.com, find the 5 highest-impact keyword gaps in the AI photography space, and queue articles for each one — spread across next week, Monday through Friday.”<\/em><\/p><\/blockquote>\n One prompt. Five articles queued.<\/strong> Each targeted at a validated keyword opportunity, scheduled across the week. That’s content velocity you cannot achieve clicking through dashboards.<\/p>\n Rank Tip:<\/strong> Start with the The three tools we built cover the core research-to-publish loop. But the pattern is identical for any new capability — adding a tool takes about 15 minutes once you have the scaffolding.<\/p>\n Ideas for additional tools:<\/p>\n
\nWhat Is MCP (and Why Should SEOs Care)?<\/h2>\n
\n
\nHow the Architecture Works<\/h2>\n
Claude Code <--MCP\/STDIO--> Your MCP Server <--HTTP--> AutoRank API\n(AI Client) (Bridge Code) (autorank.so)<\/code><\/pre>\n\n
\nThe Three Tools We’re Building<\/h2>\n
\n\n
\n \nTool<\/th>\n What It Does<\/th>\n When to Use It<\/th>\n<\/tr>\n<\/thead>\n \n analyze_blog<\/code><\/td>\nContent gap analysis on any URL<\/td>\n Competitor research, quarterly audits<\/td>\n<\/tr>\n \n get_keyword_opportunities<\/code><\/td>\nAI-ranked keyword clusters for a domain<\/td>\n Deciding what to write next<\/td>\n<\/tr>\n \n generate_article<\/code><\/td>\nQueue an article for AI generation + publishing<\/td>\n Turning research into content<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n analyze_blog<\/code> tool works on any<\/em> public blog — not just your own. Use it to reverse-engineer competitor content strategies before building your own editorial calendar.<\/p><\/blockquote>\n
\nStep 1: Initialize the Project<\/h2>\n
mkdir autorank-mcp-server && cd autorank-mcp-server\nnpm init -y\nnpm install @modelcontextprotocol\/sdk\nnpm install -D typescript @types\/node\nnpx tsc --init<\/code><\/pre>\ntsconfig.json<\/code> for a modern Node runtime:<\/p>\n{\n "compilerOptions": {\n "target": "ES2022",\n "module": "Node16",\n "moduleResolution": "Node16",\n "outDir": ".\/dist",\n "rootDir": ".\/src",\n "strict": true,\n "esModuleInterop": true,\n "skipLibCheck": true\n }\n}<\/code><\/pre>\nautorank-mcp-server\/\n package.json\n tsconfig.json\n src\/ <-- we'll create this next<\/code><\/pre>\n
\nStep 2: Set Up the Server Skeleton<\/h2>\n
src\/index.ts<\/code>. This is where everything lives — the server definition, the API helper, and all three tools.<\/p>\nimport { McpServer } from "@modelcontextprotocol\/sdk\/server\/mcp.js";\nimport { StdioServerTransport } from "@modelcontextprotocol\/sdk\/server\/stdio.js";\nimport { z } from "zod"; \/\/ Built into the MCP SDK for input validation\n\n\/\/ AutoRank API config\nconst API_BASE = "https:\/\/autorank.so\/api";\nconst API_TOKEN = process.env.AUTORANK_API_TOKEN;\n\nif (!API_TOKEN) {\n console.error("AUTORANK_API_TOKEN environment variable is required");\n process.exit(1);\n}\n\n\/\/ Initialize the MCP server\nconst server = new McpServer({\n name: "autorank-seo",\n version: "1.0.0",\n});<\/code><\/pre>\nz<\/code> import is Zod, which the MCP SDK uses for input validation. Every tool you register will define its parameters as a Zod schema — this gives you runtime type checking and auto-generated descriptions for the AI client.<\/p>\nname<\/code> field in your server config is what shows up in Claude Code’s tool list. Pick something descriptive — autorank-seo<\/code> immediately tells you what this server does.<\/p><\/blockquote>\n
\nStep 3: Build the API Helper<\/h2>\n
fetch<\/code> directly.<\/p>\nasync function autorankRequest(\n endpoint: string,\n options: {\n method?: "GET" | "POST";\n body?: Record<string, unknown>;\n params?: Record<string, string>;\n } = {}\n): Promise<unknown> {\n const { method = "GET", body, params } = options;\n\n \/\/ Build the URL with query params\n const url = new URL(`${API_BASE}${endpoint}`);\n if (params) {\n Object.entries(params).forEach(([k, v]) => url.searchParams.set(k, v));\n }\n\n const response = await fetch(url.toString(), {\n method,\n headers: {\n Authorization: `Bearer ${API_TOKEN}`,\n "Content-Type": "application\/json",\n },\n body: body ? JSON.stringify(body) : undefined,\n });\n\n if (!response.ok) {\n const errorText = await response.text();\n throw new Error(`AutoRank API error (${response.status}): ${errorText}`);\n }\n\n return response.json();\n}<\/code><\/pre>\n
\nStep 4: Register the Tools<\/h2>\n
server.tool()<\/code> method takes four arguments:<\/p>\n\n
Tool 1: analyze_blog<\/h3>\n
server.tool(\n "analyze_blog",\n "Analyze a blog URL for content gaps, keyword opportunities, and " +\n "competitive insights. Works on any public blog -- use it for " +\n "competitor research or auditing your own site.",\n {\n url: z.string().url()\n .describe("Blog URL to analyze (e.g. https:\/\/competitor.com\/blog)"),\n include_serp_analysis: z.boolean().optional().default(true)\n .describe("Include SERP competitor analysis for top opportunities"),\n },\n async ({ url, include_serp_analysis }) => {\n try {\n const result = await autorankRequest("\/blog-analyzer\/analyze", {\n method: "POST",\n body: { url, include_serp_analysis },\n });\n return {\n content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }],\n };\n } catch (error) {\n const msg = error instanceof Error ? error.message : String(error);\n return {\n content: [{ type: "text" as const, text: `Analysis failed: ${msg}` }],\n isError: true,\n };\n }\n }\n);<\/code><\/pre>\nautorankRequest<\/code>, return the JSON result as text content, catch errors gracefully. Every tool you build follows this exact same structure.<\/strong> The only things that change are the endpoint, HTTP method, and parameters.<\/p>\nTool 2: get_keyword_opportunities<\/h3>\n
server.tool(\n "get_keyword_opportunities",\n "Retrieve AI-ranked keyword opportunities for a domain. Returns " +\n "clusters sorted by traffic impact with volume and difficulty scores. " +\n "Filter by cluster to focus on a specific topic area.",\n {\n domain: z.string()\n .describe("Domain to analyze (e.g. myblog.com)"),\n cluster: z.string().optional()\n .describe("Filter by cluster name (e.g. 'product-photography')"),\n min_volume: z.number().optional()\n .describe("Minimum monthly search volume threshold"),\n limit: z.number().optional().default(50)\n .describe("Max opportunities to return (default: 50)"),\n },\n async ({ domain, cluster, min_volume, limit }) => {\n try {\n const params: Record<string, string> = { domain, limit: String(limit) };\n if (cluster) params.cluster = cluster;\n if (min_volume) params.min_volume = String(min_volume);\n\n const result = await autorankRequest("\/seo\/opportunities", { params });\n return {\n content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }],\n };\n } catch (error) {\n const msg = error instanceof Error ? error.message : String(error);\n return {\n content: [{ type: "text" as const, text: `Failed to fetch: ${msg}` }],\n isError: true,\n };\n }\n }\n);<\/code><\/pre>\ncluster<\/code> filter is powerful for focused content sprints. Instead of looking at all 200 keyword opportunities, narrow it to one topic cluster and dominate that silo before moving on. Topical authority compounds.<\/p><\/blockquote>\nTool 3: generate_article<\/h3>\n
server.tool(\n "generate_article",\n "Queue an article for AI generation and WordPress publishing. " +\n "AutoRank generates an SEO-optimized draft and publishes it on " +\n "the scheduled date. Returns a job ID for tracking.",\n {\n topic: z.string()\n .describe("Article topic or working title"),\n focus_keyword: z.string()\n .describe("Primary keyword to target (e.g. 'ai product photography')"),\n cluster: z.string().optional()\n .describe("Keyword cluster to assign this article to"),\n scheduled_date: z.string().optional()\n .describe("Publish date in ISO 8601 format (e.g. '2026-04-07')"),\n tone: z.enum(["professional", "conversational", "technical", "casual"])\n .optional().default("professional")\n .describe("Writing tone for the article"),\n word_count_target: z.number().optional().default(2000)\n .describe("Target word count (default: 2000)"),\n },\n async ({ topic, focus_keyword, cluster, scheduled_date, tone, word_count_target }) => {\n try {\n const result = await autorankRequest("\/content\/queue", {\n method: "POST",\n body: { topic, focus_keyword, cluster, scheduled_date, tone, word_count_target },\n });\n return {\n content: [{ type: "text" as const, text: JSON.stringify(result, null, 2) }],\n };\n } catch (error) {\n const msg = error instanceof Error ? error.message : String(error);\n return {\n content: [{ type: "text" as const, text: `Failed to queue: ${msg}` }],\n isError: true,\n };\n }\n }\n);<\/code><\/pre>\nautorankRequest<\/code> helper does the heavy lifting, and each handler is just configuration.<\/p>\n
\nStep 5: Connect the Transport and Start the Server<\/h2>\n
src\/index.ts<\/code>:<\/p>\nasync function main() {\n const transport = new StdioServerTransport();\n await server.connect(transport);\n console.error("AutoRank MCP server running on STDIO");\n}\n\nmain().catch((error) => {\n console.error("Fatal error:", error);\n process.exit(1);\n});<\/code><\/pre>\nnpx tsc<\/code><\/pre>\ndist\/index.js<\/code> file appears in your project directory. If TypeScript reports errors, double-check that your imports match the SDK version — the @modelcontextprotocol\/sdk<\/code> package includes Zod as a dependency.<\/p>\n
\nStep 6: Configure Claude Code<\/h2>\n
~\/.claude\/mcp.json<\/code>:<\/p>\n{\n "mcpServers": {\n "autorank": {\n "command": "node",\n "args": ["\/absolute\/path\/to\/autorank-mcp-server\/dist\/index.js"],\n "env": {\n "AUTORANK_API_TOKEN": "your-api-token-here"\n }\n }\n }\n}<\/code><\/pre>\nanalyze_blog<\/code>, get_keyword_opportunities<\/code>, generate_article<\/code>) listed when you check available tools.<\/p>\nargs<\/code> field — relative paths break depending on where you launch Claude Code from. On macOS, that’s something like \/Users\/yourname\/projects\/autorank-mcp-server\/dist\/index.js<\/code>.<\/p><\/blockquote>\n
\nTesting It: From Analysis to Published Content in One Conversation<\/h2>\n
Competitive Research<\/h3>\n
analyze_blog<\/code>, receives the gap analysis, and synthesizes it into prioritized recommendations. It might surface that the competitor has thin content on “AI product photography pricing”<\/em> or is missing coverage on “bulk background removal for ecommerce”<\/em> entirely.<\/p>\nKeyword Prioritization<\/h3>\n
get_keyword_opportunities<\/code> with the cluster filter. The response comes back as ranked keyword groups — each with volume, difficulty, and your current position. The AI recommends which ones to target based on the opportunity score.<\/p>\nContent Scheduling<\/h3>\n
generate_article<\/code> tool queues the job. AutoRank handles outline generation, drafting, SEO optimization, and WordPress publishing. You get a job ID back for tracking.<\/p>\nThe Real Power: Chaining Operations<\/h3>\n
analyze_blog<\/code> -> get_keyword_opportunities<\/code> -> generate_article<\/code> chain as your weekly content workflow. Run it every Monday morning. In 10 minutes, you’ll have a data-backed editorial calendar for the entire week.<\/p><\/blockquote>\n
\nExtending Your Server<\/h2>\n