Getting Started with Rampify
Rampify is the SEO intelligence layer for AI tools, whether you're building a site in Cursor or planning content in claude.ai. The same SEO context is right there in the conversation.
You bring the AI tool. Rampify brings the project context: your site's structure, what's indexed, which keywords are pulling weight, what positioning gaps competitors are leaving open. Every Rampify tool the dashboard exposes is also callable from your AI of choice via MCP.
How Rampify Works#
Two surfaces, one project.
The dashboard is the system of record. It pulls signals from the sources that matter for SEO (your site's crawls and technical state, Google Search Console queries and impressions, Discovery research sessions, the keyword clusters you've built), normalizes them, and synthesizes a coherent picture of your project. The visual workspace is for you to review and steer.
The MCP server is the active surface. Every piece of that synthesized picture is queryable from Claude Code, Cursor, VS Code, Claude Desktop, or claude.ai through MCP tools. Your AI gets the same project context you see in the dashboard, in a shape it can reason over.
The choice of AI tool is yours. The choice of surface depends on what you're doing. Drafting content in a long conversation? Use claude.ai or Desktop. Implementing a spec in code? Use Claude Code or Cursor. Same Rampify either way.
Quick Start#
1. Sign up#
Lands you straight in a setup wizard. Under 3 minutes.
2. Walk through the wizard#
The wizard's first question, marketing site or app, sets the path for everything that follows.
The wizard adapts to where you're starting:
| Where you're starting | What the wizard does |
|---|---|
| Just an idea | Opens a long-form brainstorm with Claude in claude.ai or Desktop about positioning, audience, and differentiators. Captures what's solid as the conversation goes. |
| Domain reserved, nothing built | Captures the domain and scaffolds the workspace for what you're about to build. |
| Site is live | Crawls the site, surfaces SEO issues, and files feature specs your AI coding tool (Claude Code, Cursor, VS Code) can implement. |
The wizard ends on a stage-appropriate menu of first actions: Discovery research, keyword planning, content drafting, or a technical audit, depending on what fits your project.
3. Connect Rampify to your AI tool#
The wizard's last step (and every project page) has a one-click install picker. Pick the tool you use; Rampify handles the auth via OAuth on first connect.
↓ Try it. Fully interactive, same picker as in the app.
Connect Rampify
Choose your AI tool
Then run this
Full setup details and the Claude UI walkthrough live in the MCP Server guide.
4. (Optional) Connect Google Search Console#
Once connected, Rampify pulls indexing data and weekly performance signals. The MCP get_search_performance tool gives your AI direct access to query data, top pages, and ranking-opportunity queries. Catch indexing problems early; turn search data into content briefs.
What you can do#
A few common workflows that span both surfaces:
| Workflow | Where it happens | What you get |
|---|---|---|
| Discover positioning gaps and competitor angles | claude.ai, Claude Desktop | A structured research output from a multi-step conversation |
| Cluster keywords into content briefs | claude.ai, Claude Desktop | Content briefs grounded in your business profile |
| Crawl your site for SEO issues | Triggered from any AI tool | Feature specs filed for Cursor or Claude Code to implement |
| Generate meta tags and JSON-LD schema | Any AI tool | Ready-to-paste tags for a page you're shipping |
| Pull GSC insights and content recommendations | Any AI tool | Query-level performance data ready to inform what to write next |
The split isn't rigid. A developer planning content can use claude.ai for the long thinking, then Cursor for the implementation. A marketer drafting a brief can stay in Claude Desktop the whole time. Rampify follows you across surfaces because every tool is exposed via MCP.
Toolkit#
| Tool | What it is |
|---|---|
| Dashboard | Visual workspace at rampify.dev. Site analysis, keyword clusters, feature specs, campaigns, GSC data. |
| MCP server | The active surface. Connects to Claude Code, Cursor, VS Code, Claude Desktop, claude.ai. See the 56 available tools. |
| REST API | For automation in n8n, Zapier, Make, or your own scripts. Reference. |
| VS Code extension | Specialized in-IDE features for spec browsing and MCP setup, if you live in VS Code or Cursor. See the extension docs. |
Keep reading
Introduction to Rampify
The full positioning, who Rampify is for, and how it brings SEO intelligence into your AI tools.
Spec-Driven Development
The philosophy behind grounding AI agents in deterministic project context instead of letting them guess.
Available MCP Tools
Reference for all 56 MCP tools you can call from your AI: get_page_intelligence, crawl_site, generate_meta, start_discovery, and more.