Connect your AI: Claude, ChatGPT, Cursor, VS Code and Claude Code

You can connect SEOAsist to the AI app you already use. Once connected, Claude, ChatGPT, Cursor or VS Code can read your sites' data and do work, as far as you allow. The connection uses the remote MCP URL; there's nothing to install.

Remote MCP URL: https://seoasist.com/api/mcp (Streamable HTTP)

Step-by-step guides and one-click links are in the panel: Integrations → Connect your AI assistant.

#Prerequisites

• You need a plan with API access: Pro or Agency. Otherwise the connection returns 403 plan_required.
• The AI app you connect runs on its own subscription. It doesn't use your SEOAsist AI allowance.

#Signing in with OAuth

On first use the AI app opens a SEOAsist sign-in window:

1. Sign in with your SEOAsist account.
2. Choose the organization.
3. Choose the permission: read only or act. With act, the AI can start crawls, open fixes and send articles to review.
4. Confirm. No key copying needed.

The connection is listed under Settings → API keys as OAuth: <app name>.

#Setup per app

#claude.ai and Claude Desktop

1. Open Settings → Connectors.
2. Choose Add custom connector.
3. Paste the URL: https://seoasist.com/api/mcp.
4. Sign in to SEOAsist in the window that opens.

#ChatGPT

1. Turn on developer mode in the settings.
2. Add a new app / connector with the MCP URL: https://seoasist.com/api/mcp.
3. Sign in to SEOAsist.

#Cursor

Add to ~/.cursor/mcp.json:

{"mcpServers":{"seoasist":{"url":"https://seoasist.com/api/mcp"}}}

#VS Code (Copilot)

Add to your user mcp.json:

{"servers":{"seoasist":{"type":"http","url":"https://seoasist.com/api/mcp"}}}

#Claude Code

claude mcp add --transport http seoasist https://seoasist.com/api/mcp

Then type /mcp inside Claude Code and sign in.

#When no sign-in window can open (servers, CI)

Where no browser can open, use an API key instead of OAuth. Create the key under Settings → API keys (REST API), then:

claude mcp add --transport http seoasist https://seoasist.com/api/mcp --header "Authorization: Bearer sa_live_..."

If it should act, the key needs the write scope.

#Ready commands

Once connected, five ready commands appear in the AI app's prompt or slash menu: seo_round, content_from_gap, backlink_outreach, agent_tasks and weekly_report. For what each does, see the MCP reference.

#The Claude Code skill

There's a ready-made SEOAsist skill for Claude Code.

1. Download the file: https://seoasist.com/downloads/seoasist-skill.md.
2. Save it as ~/.claude/skills/seoasist/SKILL.md.
3. In Claude Code, type /seoasist or say "run the seoasist round".

The skill's hard rules:

• It never publishes page rewrites live.
• It starts a crawl only if the last crawl is older than 3 days.
• Per site and run, it opens at most 3 fix PRs and 2 new blog posts.
• It reports in your language.

#One click from the desktop app

The Connect your AI screen in the desktop app sets up the connection in one click:

• Claude Desktop: needs Node.js. It creates a device API key named Desktop: <device>. Remove revokes that key.
• Claude Code: also installs the skill.
• Cursor and VS Code.

Every config file it changes is backed up next to it with the .seoasist-bak extension. Files with invalid JSON are never touched.

#Revoking a connection

1. Open Settings → API keys.
2. Find the OAuth: <app name> row.
3. Revoke it. Revocation is immediate; the AI app loses access on its next request.

#FAQ

#Why does the connection return 403?

Your plan doesn't include API access. Move to Pro or Agency. See Plans and quotas.

#Why can't the AI make changes?

If you chose read only at sign-in, or the key has no write scope, write tools don't work. Revoke the connection and connect again with the act permission.

#Can I connect more than one organization?

Each connection belongs to the one organization you chose at sign-in. Set up a separate connection for another organization.

#Who pays for the AI app?

The AI app runs on your own subscription. On the SEOAsist side you only need your plan.