MCP server (Claude & Cursor)
Use SEOforGPT from Claude or Cursor as tools: brand visibility tests, reports, prompt suggestions, competitor comparison, and content generation.
Overview
The MCP (Model Context Protocol) server exposes SEOforGPT as tools that Claude, Cursor, and other MCP clients can call. You install the server once, add it to your app’s MCP config with your email and password, and then use natural language to run visibility tests, fetch reports, or generate blog, LinkedIn, or X.com content.
Same backend as the API
The MCP uses the same quotas and limits as the Public API. Use the MCP for chat-based workflows; use the API for scripts and CI.
Requirements
- Node.js 22 or newer
- An SEOforGPT account (sign up at seoforgpt.io)
- Your account email and password (used only to obtain a token; not stored)
Install & build
Clone the repo (or use a release), then from the project root:
cd mcp npm install npm run build
The server runs as node dist/index.js. You must set SEOFORGPT_EMAIL and SEOFORGPT_PASSWORD (see config examples below).
Use with Claude
- Build the server and note the full path to
mcp/dist/index.js. - Open your Claude MCP config:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json
- macOS:
- Add the SEOforGPT server (replace the path and credentials):
{
"mcpServers": {
"seoforgpt": {
"command": "node",
"args": ["/absolute/path/to/seoforgpt.io/mcp/dist/index.js"],
"env": {
"SEOFORGPT_EMAIL": "you@example.com",
"SEOFORGPT_PASSWORD": "your-password"
}
}
}
}Restart Claude completely. In a new conversation, Claude will have access to the SEOforGPT tools.
Use with Cursor
In your project or Cursor settings, add the MCP server. Example .cursor/mcp.json:
{
"mcpServers": {
"seoforgpt": {
"command": "node",
"args": ["/absolute/path/to/seoforgpt.io/mcp/dist/index.js"],
"env": {
"SEOFORGPT_EMAIL": "you@example.com",
"SEOFORGPT_PASSWORD": "your-password"
}
}
}
}Tools reference
All tools are scoped to your account and use your plan quotas.
check_brand_visibility
Run a brand visibility test. Params: projectId or testId, brand, prompts or crawlRecordId, optional competitors.
get_visibility_report
Fetch the latest visibility report. Params: testId or projectId.
suggest_prompts
Generate prompt suggestions from a crawl. Params: crawlRecordId (required), optional projectId, brand, competitors.
compare_competitors
Summarize competitor performance from test results. Params: testId or projectId.
generate_content
Generate blog, LinkedIn, or X.com content. Params: projectId, platform (blog | linkedin | thread), topic; optional metadata. Consumes content quota.
Billing & quotas
Visibility: check_brand_visibility uses your visibility quota. Content: generate_content uses your content quota. Limits are the same as the Public API; denials return an error to the tool.