Install Rampify MCP Server

Get Rampify's MCP server installed and configured in your IDE. See the MCP Server overview to learn what MCP is and why it's useful.

Prerequisites#

• Node.js 18+ installed
• An active Rampify account
• Your Rampify API key (generate one here)

Supported IDEs#

Rampify's MCP server works with any MCP-compatible IDE or AI assistant:

AI-Native IDEs#

Traditional IDEs with MCP Support#

Terminal & Other Clients#

Don't see your IDE? Check its documentation for "MCP server configuration" or "Model Context Protocol setup."

Installation#

Global Installation (Recommended)#

Install the MCP server globally using npm:

npm install -g @rampify/mcp-server

Local Installation#

Alternatively, install it locally in your project:

npm install --save-dev @rampify/mcp-server

Do I Need to Install It?#

All IDE configurations below use npx -y @rampify/mcp-server, which automatically downloads the package if it's not installed. This means explicit installation is optional but recommended for:

• Faster startup - No download delay when IDE starts
• Offline usage - Works without internet connection
• Version control - Lock to a specific version in package.json

If you skip installation, npx will download the latest version on-demand each time your IDE restarts.

IDE Configuration#

Choose your IDE below for specific setup instructions:

Cursor#

Cursor has native MCP support built-in.

Config file: ~/.cursor/config.json

{
  "mcpServers": {
    "rampify": {
      "command": "npx",
      "args": ["-y", "@rampify/mcp-server"],
      "env": {
        "BACKEND_API_URL": "https://www.rampify.dev",
        "API_KEY": "sk_live_your_api_key_here",
        "SEO_CLIENT_DOMAIN": "your-domain.com"
      }
    }
  }
}

After setup:

1. Restart Cursor
2. Open Composer (Cmd+I or Ctrl+I)
3. Ask: "What SEO issues does my site have?"

---

Claude Code#

Claude Code has built-in MCP support from Anthropic.

Config file:

• macOS: ~/Library/Application Support/Claude/config.json
• Linux: ~/.config/Claude/config.json
• Windows: %APPDATA%\Claude\config.json

{
  "mcpServers": {
    "rampify": {
      "command": "npx",
      "args": ["-y", "@rampify/mcp-server"],
      "env": {
        "BACKEND_API_URL": "https://www.rampify.dev",
        "API_KEY": "sk_live_your_api_key_here",
        "SEO_CLIENT_DOMAIN": "your-domain.com"
      }
    }
  }
}

After setup:

1. Restart Claude Code
2. Start a new chat
3. Rampify tools will be available automatically

---

VS Code#

VS Code has native MCP support built-in (as of June 2025).

Config file:

• macOS/Linux: ~/.vscode/mcp-settings.json
• Windows: %APPDATA%\Code\User\mcp-settings.json

{
  "mcpServers": {
    "rampify": {
      "command": "npx",
      "args": ["-y", "@rampify/mcp-server"],
      "env": {
        "BACKEND_API_URL": "https://www.rampify.dev",
        "API_KEY": "sk_live_your_api_key_here",
        "SEO_CLIENT_DOMAIN": "your-domain.com"
      }
    }
  }
}

After setup:

1. Reload VS Code window (Cmd+Shift+P > "Developer: Reload Window")
2. Open Copilot Chat or Command Palette
3. Ask: "What SEO issues does my site have?"

Note: If you're using an older version of VS Code, you may need the Continue.dev extension for MCP support.

---

Windsurf#

Windsurf (by Codeium) has native MCP support.

Config file:

• macOS/Linux: ~/.codeium/windsurf/mcp_server_config.json
• Windows: %APPDATA%\Codeium\windsurf\mcp_server_config.json

{
  "mcpServers": {
    "rampify": {
      "command": "npx",
      "args": ["-y", "@rampify/mcp-server"],
      "env": {
        "BACKEND_API_URL": "https://www.rampify.dev",
        "API_KEY": "sk_live_your_api_key_here",
        "SEO_CLIENT_DOMAIN": "your-domain.com"
      }
    }
  }
}

After setup:

1. Restart Windsurf
2. Open AI chat panel
3. Ask: "What SEO issues does my site have?"

---

Zed#

Zed supports MCP through its settings configuration.

Config file:

• macOS: ~/.config/zed/settings.json
• Linux: ~/.config/zed/settings.json
• Windows: %APPDATA%\Zed\settings.json

Add to your settings.json:

{
  "context_servers": {
    "rampify": {
      "command": "npx",
      "args": ["-y", "@rampify/mcp-server"],
      "env": {
        "BACKEND_API_URL": "https://www.rampify.dev",
        "API_KEY": "sk_live_your_api_key_here",
        "SEO_CLIENT_DOMAIN": "your-domain.com"
      }
    }
  }
}

After setup:

1. Restart Zed
2. Open Assistant panel (Cmd+? or Ctrl+?)
3. Ask: "Check SEO for my site"

---

Other MCP-Compatible IDEs#

Any IDE that supports the Model Context Protocol can use Rampify. The configuration is always similar:

{
  "mcpServers": {
    "rampify": {
      "command": "npx",
      "args": ["-y", "@rampify/mcp-server"],
      "env": {
        "BACKEND_API_URL": "https://www.rampify.dev",
        "API_KEY": "sk_live_your_api_key_here",
        "SEO_CLIENT_DOMAIN": "your-domain.com"
      }
    }
  }
}

Don't see your IDE? Check its documentation for "MCP server configuration" or "Model Context Protocol setup."

---

Environment Variables#

The MCP server uses the following environment variables:

API_KEY (Required)#

Your Rampify API key for authentication.

API_KEY=sk_live_abc123...

Generate your API key in the dashboard settings.

SEO_CLIENT_DOMAIN (Recommended)#

Default domain to use when not specified in tool calls.

SEO_CLIENT_DOMAIN=yoursite.com

This allows you to omit the domain parameter in MCP tool calls.

BACKEND_API_URL (Optional)#

Override the default API endpoint.

BACKEND_API_URL=https://www.rampify.dev

Default: https://www.rampify.dev

---

Advanced Configuration (Optional)#

For power users who need custom behavior.

Configuration File#

Create a .rampify.json file in your project root for additional settings:

{
  "defaultDomain": "example.com",
  "autoScan": false,
  "notifications": {
    "criticalIssues": true,
    "warnings": false
  },
  "tools": {
    "generateMeta": {
      "maxTitleLength": 60,
      "maxDescriptionLength": 155
    }
  }
}

defaultDomain#

Set a default domain to use when none is specified in tool calls.

Type: string | Default: null

autoScan#

Automatically trigger site scans when using get_seo_context() if data is stale (> 24 hours old).

Type: boolean | Default: false

notifications#

Configure which types of notifications to show in your editor.

Type: object

• criticalIssues (boolean) - Show alerts for critical issues
• warnings (boolean) - Show alerts for warnings

tools.generateMeta#

Customize meta tag generation behavior.

Type: object

• maxTitleLength (number) - Maximum title length (default: 60)
• maxDescriptionLength (number) - Maximum description length (default: 155)

Editor-Specific Settings#

Cursor: alwaysAllow#

Tools that don't require user confirmation before execution:

{
  "mcpServers": {
    "rampify": {
      "command": "npx",
      "args": ["-y", "@rampify/mcp-server"],
      "env": {
        "API_KEY": "sk_live_your_key",
        "SEO_CLIENT_DOMAIN": "yoursite.com"
      },
      "disabled": false,
      "alwaysAllow": ["get_page_seo", "crawl_site"]
    }
  }
}

Claude Code: timeout#

Maximum execution time in milliseconds for MCP tool calls:

{
  "mcpServers": {
    "rampify": {
      "timeout": 30000
    }
  }
}

Type: number | Default: 30000 (30 seconds)

Multi-Domain Configuration#

If you manage multiple sites, you can configure domain-specific settings in your .rampify.json:

{
  "domains": {
    "example.com": {
      "priority": "high",
      "autoScan": true
    },
    "staging.example.com": {
      "priority": "low",
      "autoScan": false
    }
  }
}

Verify Installation#

To verify the MCP server is working:

1. Restart your editor (complete restart, not just reload)
2. Open a new AI chat/session (Cursor Composer, Continue sidebar, etc.)
3. Ask your AI assistant:

"What SEO issues does my site have?"
"Check the SEO of this page"
"Is this page indexed in Google?"
"What should I write next based on my GSC data?"

What to expect:

• Your AI will use Rampify MCP tools automatically
• You'll see real-time SEO data in natural language responses
• Data comes from your Rampify account (not hallucinated)
• GSC data included if you've connected Google Search Console

Example response:

Based on your Rampify data:
- 247 URLs found, 230 indexed
- 3 critical issues detected:
  - 2 pages returning 404 errors
  - 1 redirect chain affecting /blog/old-post
- Average site health: 85/100 (Good)

Would you like me to show you how to fix the 404 errors?

Having Issues?#

If you encounter any problems during installation or setup, check our Troubleshooting Guide for detailed solutions.