How to Setup an MCP Server in Cursor: 60 Second Guide (2026)

1. Prerequisites

Before beginning, make sure you have installed the latest version of Cursor IDE (version 0.40 or higher, which includes native Model Context Protocol support). You will also need a verified RankForge account token and about sixty seconds of spare time.

2. Step 1: Create Your Free RankForge Account

RankForge provides a permanent free plan with 10 audits each month with no credit card required. To generate your authentication token:

1. Navigate to rankforgeapp.pages.dev/login.html and sign in with your email or Google account.
2. In your Developer Dashboard, click on the API Keys tab.
3. Click Generate New MCP Token and copy the Bearer string (formatted as rf_live_...). Keep this token secure; it grants access to your audit quota.

3. Step 2: Grab Your Apify Key (BYOK Architecture)

RankForge operates on a Bring Your Own Key (BYOK) model to ensure you never pay inflated markups on live crawling. You connect your Apify account once:

1. Visit apify.com and sign in. Apify automatically provides $5.00 in free compute credits every month to every account.
2. Go to Settings → Integrations → API Tokens and copy your personal API token.
3. In your RankForge Dashboard under Settings → BYOK Providers, paste your Apify token and click Save.

Your free $5 monthly credit easily covers 250 deep website audits. RankForge coordinates the scraping pipelines without adding per-request markups.

4. Step 3: Configure Cursor mcp.json (Copy-Paste JSON)

Cursor stores its MCP server definitions in a simple JSON file. You can configure this globally (applying to all projects) or per-repository:

• Global Path (macOS/Linux): ~/.cursor/mcp.json
• Global Path (Windows): C:\Users\<Username>\.cursor\mcp.json
• Project-Specific Path: .cursor/mcp.json inside your repository root

Open or create the file, and paste the following four-line configuration block:

{
  "mcpServers": {
    "rankforge": {
      "url": "https://rankforgeapp.pages.dev/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_RANKFORGE_TOKEN"
      }
    }
  }
}

Replace YOUR_RANKFORGE_TOKEN with the token you copied in Step 1. Save the file and completely restart Cursor to initialize the protocol connection. Alternatively, you can generate this file automatically with our free MCP Config Generator.

5. Step 4: Test It with Your First Command

Once Cursor reopens, verify the connection by opening the chat panel (Ctrl+L or Cmd+L). Ensure the mode selector is set to Agent Mode.

Enter the following natural language prompt:

Audit https://rankforgeapp.pages.dev for Core Web Vitals, canonical tags, and AEO citation readiness.

Cursor will display a tool call pill labeled rankforge:seo_audit or rankforge:aeo_geo_audit. Within seconds, your agent parses the live result and outputs an actionable summary directly in your chat stream.

6. Troubleshooting 3 Common Setup Issues

If your agent does not immediately detect the RankForge tools, check these three common configuration pitfalls:

1. JSON Syntax Error: Ensure trailing commas are removed if rankforge is the only entry in mcpServers. Invalid JSON syntax will cause Cursor to ignore the file silently.
2. Missing Agent Mode: If Cursor is set to standard "Ask" mode rather than "Agent" mode, it will answer from internal training weights rather than executing external MCP tool calls. Switch the dropdown at the bottom of the chat panel to Agent.
3. Expired or Malformed Bearer Token: Verify that the word Bearer is followed by a single space before your token string. If authentication fails, RankForge returns an HTTP 401 response.

7. Connecting to Other AI Coding Environments

Because RankForge is built on the universal Model Context Protocol standard, you can use the same server URL and token across other editors:

• Claude Code (CLI): Run claude mcp add rankforge -- https://rankforgeapp.pages.dev/mcp?token=YOUR_TOKEN
• Windsurf Editor: Add the exact same JSON snippet to ~/.codeium/windsurf/mcp_config.json
• Cline (VS Code): Open Cline Settings → MCP Servers → Add Server and enter the SSE URL.
• Zed Editor: Add to ~/.config/zed/settings.json under the context_servers key.

8. Summary & Next Steps

You now have an autonomous SEO agency embedded directly inside your code editor. Rather than switching between browser tabs and manually copying issues into tickets, your AI coding agent can audit your web application, identify technical bottlenecks, and apply code patches within a single conversation.

Ready to scale up your audits? Explore our pricing plans or connect additional tools.