Set up AkaiSEO MCP

AkaiSEO MCP lets compatible AI clients call AkaiSEO tools for keyword research, SERP inspection, local business research, competitive search intelligence, domain research, backlink overview, saved keywords, rank tracking, shared project context, and Google Search Console performance and URL inspection.

The hosted MCP server URL is:

https://app.akaiseo.com/mcp

The first connection sends you through AkaiSEO login. After authorization, your MCP client can call AkaiSEO tools with the project context and account scopes you approved. For headless environments and CI, connect with an API key instead.

For the most current setup UI and a copyable endpoint, open AI & MCP in AkaiSEO.

Claude Code

The AkaiSEO plugin is the preferred way to connect Claude Code — one install adds MCP and all nine Agent Skills together. Use the steps below only if you want MCP on its own.

Use user scope to make AkaiSEO available across projects. Use local scope for the current repository.

claude mcp add --transport http --scope user akaiseo https://app.akaiseo.com/mcp

After adding the server, approve the AkaiSEO login when prompted.

Claude Desktop

1. Open Settings -> Connectors.
2. Click Add custom connector.
3. Paste https://app.akaiseo.com/mcp.
4. Approve the AkaiSEO login when prompted.

Claude Desktop custom connectors require a Claude plan that supports custom connectors.

Cursor

1. Open Cursor Settings -> Tools & Integrations -> MCP Tools.
2. Click New MCP Server. Cursor opens mcp.json.
3. Add:

{
  "mcpServers": {
    "akaiseo": {
      "url": "https://app.akaiseo.com/mcp"
    }
  }
}

4. Approve the AkaiSEO login when prompted.

Codex CLI

The AkaiSEO plugin is the preferred way to connect Codex CLI — one install adds MCP and all nine Agent Skills together. Use the steps below only if you want MCP on its own.

Run this in your terminal:

codex mcp add akaiseo --url https://app.akaiseo.com/mcp

Approve the login when prompted.

Codex Desktop

1. Open Settings -> Integrations & MCP.
2. Click Add your own.
3. Paste https://app.akaiseo.com/mcp.
4. Approve the AkaiSEO login when prompted.

Connect with an API key

Use an API key in headless environments, CI, or clients where OAuth is inconvenient. API keys are personal: anything an agent does with your key acts as you in your workspace.

In the AkaiSEO app, open Settings -> API keys, create a key, and copy it when it appears. It won't be shown again.

For Claude Code, run:

claude mcp add --transport http --scope user akaiseo https://app.akaiseo.com/mcp --header "Authorization: Bearer akai_YOUR_KEY"

For Cursor, add headers to the server entry in mcp.json:

{
  "mcpServers": {
    "akaiseo": {
      "url": "https://app.akaiseo.com/mcp",
      "headers": {
        "Authorization": "Bearer akai_YOUR_KEY"
      }
    }
  }
}

For Codex CLI, put the key in an environment variable and reference it:

export AKAISEO_API_KEY=akai_YOUR_KEY
codex mcp add akaiseo --url https://app.akaiseo.com/mcp --bearer-token-env-var AKAISEO_API_KEY

Any other client that supports custom HTTP headers can send Authorization: Bearer akai_YOUR_KEY or x-api-key: akai_YOUR_KEY.

Available tools

AkaiSEO MCP exposes tools for SEO research workflows:

• Research keywords with volume, difficulty, and CPC.
• Fetch live Google organic SERP results for keywords.
• Find exact keyword, page, rank, volume, CPC, intent, and traffic rows for a domain or page.
• Compare SERP competitors across a supplied keyword set.
• Search local businesses near a coordinate, filtering by rating, review count, or claimed status.
• Fetch one Maps or Local Finder SERP, and read Google Business Q&A when needed.
• Audit a Google Business Profile: categories, rating, hours, photos, and claim status.
• Collect Google reviews (including reviews from other sites) and Google Business posts.
• Look up valid Google Business category slugs.
• Check Google Maps rank at each point of a grid around a business.
• Hydrate keywords with search volume, difficulty, intent, CPC, and trends.
• List saved keywords from an AkaiSEO project.
• Save useful keywords back to AkaiSEO.
• Read rank tracker configs and latest keyword positions.
• Summarize a domain's organic footprint.
• Find keywords a domain already ranks for.
• Check backlink and referring-domain overview data.
• Read first-party Google Search Console performance (clicks, impressions, CTR, position).
• Inspect index status, crawl, and canonical for specific URLs (up to 10 per call).
• Read and update a project's shared context: business, goal, positioning, writing preferences, competitors, key pages, and a research log (free, no credits).

What to do after setup

Once AkaiSEO MCP is connected, set up AkaiSEO Agent Skills. MCP gives your agent access to AkaiSEO data. Skills are separate SKILL.md files that tell your agent how to use that data for specific SEO jobs.

Start with one focused workflow instead of asking your agent to "do SEO" broadly.

• Use SEO project setup to save your goals, positioning, competitors, and key pages to your project context, so every other skill reuses them.
• Use SEO coach if you are new to SEO or are not sure which workflow to run first.
• Use keyword research to discover keyword opportunities.
• Use competitive landscape to map a market before choosing competitors or pages.
• Use competitor analysis to study one competitor.
• Use keyword clustering to turn keywords into page groups.
• Use link prospecting to find outreach prospects for a linkable asset.

Troubleshooting

If your client cannot connect, check that the server URL is exactly https://app.akaiseo.com/mcp.

If Codex reports Authorization server response missing required issuer: expected https://app.akaiseo.com, upgrade Codex CLI or the Codex desktop app to 0.147.0 or later. Codex 0.143 through 0.146 drop the issuer from the OAuth callback. You can also connect with an API key instead of OAuth.

If authorization fails, disconnect the AkaiSEO server in your client, add it again, and repeat the login flow.

If your agent cannot find a project, ask it to list AkaiSEO projects first and use the returned project ID in later tool calls.