MCP Server

Rampify hosts a remote MCP server that brings SEO intelligence into your AI coding tools. No packages to install, no API keys to manage. Connect via OAuth, pick your project, and start querying.

What is MCP?#

The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external tools and data sources. When you connect Rampify via MCP, your AI can check SEO status, generate meta tags, analyze search performance, all from natural language prompts in your editor. See all available tools.

Prerequisites#

  • A Rampify account with at least one project

Connect Your IDE#

Choose your editor below. Each setup takes under 2 minutes. You'll authenticate via OAuth and select which project to connect. The connection is scoped to that project automatically.

Claude Code (CLI)#

claude mcp add --transport http rampify https://www.rampify.dev/api/mcp

Claude Code will open an OAuth flow in your browser. Sign in to Rampify and select your project. The connection is configured automatically.


Cursor#

Config file: .cursor/mcp.json (in your project root)

{
  "mcpServers": {
    "rampify": {
      "type": "http",
      "url": "https://www.rampify.dev/api/mcp"
    }
  }
}

On first use, Cursor will prompt you to authenticate via OAuth. Sign in and select your project.


VS Code#

Config file: .vscode/mcp.json (in your project root)

{
  "mcpServers": {
    "rampify": {
      "type": "http",
      "url": "https://www.rampify.dev/api/mcp"
    }
  }
}

On first use, VS Code will prompt you to authenticate via OAuth. Sign in and select your project.


Other MCP Clients#

Any MCP-compatible client can connect using the HTTP transport:

  • Server URL: https://www.rampify.dev/api/mcp
  • Transport: HTTP (Streamable HTTP)
  • Authentication: OAuth (automatic via the MCP protocol)

Multiple Projects#

When you connect via OAuth, you select which project to use. The connection is scoped to that project, so tools only operate on the data you chose.

To switch projects, re-authenticate your MCP connection. The project picker will appear again and you can select a different project.

You can also use the list_projects MCP tool to see which project is currently active:

> Use the list_projects tool to show my projects
VS Code Extension Handles This Automatically

If you use the Rampify VS Code Extension, the MCP setup wizard handles project selection automatically when you run Rampify: Set Up MCP Server.


Connect via Claude Web#

You can use Rampify tools directly in the Claude web interface, no IDE required. This works on both claude.ai and Claude Code on the web.

Setup#

  1. Open claude.ai
  2. Go to Customize > Connectors
  3. Click Plus Sign (+) > Add custom connector and enter the name "Rampify" and the server URL: https://www.rampify.dev/api/mcp and click "Add"
  4. On the main screen click the "Connect" button and sign in to Rampify
  5. Select which project to connect (if you have multiple)

Once connected, Rampify tools are available in any conversation. The connection is scoped to the project you selected.

Great for Content Strategy

The Claude web interface is perfect for content planning sessions where you want to explore GSC data, research keywords, and draft content recommendations without switching to your IDE.


Available Tools#

Rampify provides 27 MCP tools across 6 categories. Tools are always up to date. The remote server gets new tools instantly without version updates.

Account

list_projectsList all projects you have access to and which is active

Site Analysis & Monitoring

crawl_siteTrigger a full site crawl and analysis
scan_pageScan a single page for SEO data and keyword audit
get_page_seoGet comprehensive SEO data for a specific page
get_issuesGet all SEO issues with health score
get_gsc_insightsGoogle Search Console performance and content recommendations

Content Creation & Optimization

generate_metaGenerate optimized meta tags for any page
generate_schemaAuto-generate schema.org JSON-LD markup
optimize_contentScan a page and generate keyword optimization instructions
create_content_specCreate a page-type spec linked to a keyword cluster

Keyword Research & Management

create_keyword_clusterCreate a keyword cluster with grouped keywords
get_keyword_clustersRetrieve clusters with volume data and audit status
lookup_keywordsLook up search volume, competition, and trends
suggest_keywordsGet related keyword suggestions for a seed keyword
manage_keywordsChange tier, move between clusters, or remove keywords

Feature Specs

create_feature_specCreate and save a feature specification
get_feature_specRetrieve a spec with full details and keyword data
list_feature_specsList all specs with status, priority, and progress
update_feature_specUpdate status, complete tasks, or add new tasks
link_commitLink a git commit SHA to a spec and task for traceability
get_commit_messageGenerate a conventional-commits-style message from spec context

Campaign Attribution

list_campaignsList marketing campaigns with tracked links
create_campaignCreate a marketing campaign for attribution tracking
create_tracked_linkGenerate a tracked URL for a campaign
save_campaign_contentSave content created for a campaign
get_top_contentGet top-performing campaign content for reference
get_campaign_performanceGet traffic performance data for a campaign

Troubleshooting#

Tools not appearing#

  1. Restart your editor — completely quit and reopen (not just reload)
  2. Re-authenticate — remove and re-add the MCP connection to trigger a fresh OAuth flow
  3. Verify the URLhttps://www.rampify.dev/api/mcp (no trailing slash)

Authentication errors#

  • Try disconnecting and reconnecting the MCP server in your editor
  • Make sure you're signing in with the correct Rampify account
  • Check that your account has at least one project

Connection timeout#

  • Check you can access https://www.rampify.dev in a browser
  • Check firewall/proxy settings — allow outbound HTTPS to rampify.dev

Editor-specific issues#

Cursor: Requires version 0.40+. Check Settings > Features > Enable MCP. Add "alwaysAllow": ["get_page_seo", "get_issues", "get_gsc_insights"] to skip per-tool confirmations.

VS Code: Requires June 2025+ for native MCP support. Use Cmd+Shift+P > "Developer: Reload Window" after config changes.


Example Workflows#

During development:

  • Write new blog post
  • Ask: "Generate meta tags for this post"
  • Ask: "Check for SEO issues"
  • Fix any warnings
  • Ask: "Safe to deploy?"
  • Deploy with confidence

Content planning:

  • Ask: "What should I write next based on my GSC data?"
  • Ask: "What queries am I ranking for but have low CTR?"
  • Ask: "Generate schema for my new blog post"