Connect Rampify to Your IDE
Rampify delivers SEO intelligence directly into your development workflow—no context switching required.
All integration mechanisms provide the same SEO data in structured formats. Choose based on your preferred workflow, not our constraints.
Choose Your Integration#
| Mechanism | Best For | Status | Setup Time |
|---|---|---|---|
| MCP Server | IDEs with MCP support (VS Code, Cursor, Claude Code, Windsurf, Zed) | Available | 5 min |
| VS Code Extension | Browse specs, set up MCP, track commits in VS Code/Cursor | Available | 2 min |
| REST API | Custom integrations, CI/CD, scripts | Available | 10 min |
MCP Server#
Best for IDEs with MCP support: VS Code, Cursor, Claude Code, Windsurf, Zed
Natural language interface—ask your AI assistant questions like "What should I write next?" or "Check SEO for this page." Your AI assistant uses Rampify tools automatically.
Features:
- Real-time SEO analysis while you code
- Generate meta tags and schema markup
- Check indexing status before deployment
- Content recommendations from GSC data
Get Started with MCP
MCP Server Overview
Learn how the Model Context Protocol brings SEO intelligence into your IDE.
Installation Guide
Install and configure for Cursor, Claude Code, VS Code, and more.
Available Tools
Explore all 6 MCP tools: get_page_seo(), get_issues(), generate_meta(), and more.
VS Code Extension#
Best for browsing specs, setting up MCP, and tracking commits in VS Code and Cursor
A sidebar panel that brings your Rampify specs directly into your editor. Browse feature specs by status, copy spec references into AI chat with one click, and set up the MCP server with a built-in wizard.
Features:
- Specs sidebar grouped by status (Planned, In Progress, Completed)
- One-click MCP server setup for Claude Code, Cursor, and Windsurf
- Copy spec references for AI context
- Commit tracking linked back to specs
Get Started with the VS Code Extension
REST API#
Best for custom integrations, scripts, CI/CD pipelines
Direct API access for programmatic control. Build custom workflows, automate checks, integrate with your deployment pipeline.
Use cases:
- n8n, Zapier, Make automation workflows
- CI/CD pre-deployment checks
- Custom dashboards and reports
- Batch processing and monitoring
API Documentation
All Mechanisms Provide the Same Data#
Regardless of which integration you choose, you get:
- Site-wide SEO health - Issues, health score, prioritized fixes
- Page-level analysis - Indexing status, performance metrics, GSC data
- Content recommendations - What to write next based on GSC insights
- Meta tag generation - AI-powered titles, descriptions, Open Graph tags
- Schema markup generation - Valid JSON-LD for any page type
- Site crawling - On-demand full site analysis
Choose based on your workflow, not feature availability.
Not Sure Which to Choose?#
If your IDE supports MCP (VS Code, Cursor, Claude Code, Windsurf, Zed): Start with MCP Server. It takes 5 minutes to set up and provides the most seamless experience with real-time SEO queries.
If you use VS Code or Cursor: Install the VS Code Extension for a sidebar panel that lets you browse specs, set up MCP with a wizard, and track commits — all without leaving your editor.
If you're building automation workflows or CI/CD: Use the REST API. It's designed for programmatic access with pre-organized action items.