Rampify MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | Your API key from Rampify dashboard (starts with sk_live_...) | |
| CACHE_TTL | No | Cache duration in seconds | 3600 |
| LOG_LEVEL | No | Logging level: debug, info, warn, or error | info |
| BACKEND_API_URL | No | Rampify API endpoint - always use https://www.rampify.dev | https://www.rampify.dev |
| SEO_CLIENT_DOMAIN | No | Default domain for this project (e.g., yoursite.com or localhost:3000) |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_page_seoB | Get comprehensive SEO data and insights for a specific page. Returns performance metrics from Google Search Console, detected issues, optimization opportunities, and actionable recommendations. |
| get_issuesB | Get SEO issues for entire site with health score. Returns health score (0-100), categorized issues by severity, and prioritized recommendations for fixes. |
| crawl_siteA | Trigger a fresh site crawl and analysis. Use this after deploying changes to refresh SEO data. Crawls the entire site, checks all URLs, detects issues, and updates the database with current SEO status. |
| generate_schemaA | Auto-generate structured data (schema.org JSON-LD) for any page. Detects page type (Article, Product, FAQ, etc.) and generates appropriate schema with validation. Returns ready-to-use code snippets. |
| generate_metaC | Generate optimized meta tags (title, description, OG tags) for a page. Analyzes page content and provides recommendations for SEO-optimized meta tags based on actual content, headings, and topics. |
| get_gsc_insightsC | Get Google Search Console performance insights with AI-powered content recommendations. Returns top performing pages, query opportunities (improve CTR, rankings, keyword gaps), and actionable recommendations for what content to write next. |
| create_feature_specA | Create and save a feature specification to Rampify. IMPORTANT: Before calling this tool, YOU (Claude) must generate the complete structured spec from the user's description and your codebase context. Do not pass raw natural language — populate all fields:
|
| get_feature_specA | Retrieve a feature specification from Rampify. Use this when starting work on a feature to understand what to build, which files to touch, and what the acceptance criteria are. Two lookup modes:
|
| update_feature_specA | Update a feature spec to reflect actual progress. Mark tasks and criteria as complete, update spec status, and advance next_action. Use this after completing work described in a spec task. Returns a suggested_commit message string. Examples:
|
| list_feature_specsA | Browse and filter all feature specifications for a project. Returns an overview of specs with status, priority, and task progress. Use this to answer questions like "what's in progress?", "what's planned?", or "show me all high-priority specs". For full spec details (criteria, tasks, affected files), follow up with get_feature_spec using a spec_id from the results. |
| link_commitA | Link a git commit SHA to a feature spec and optionally a task. Creates full traceability: code -> commit -> task -> spec. Deterministic workflow for AI agents:
The commit is recorded in the spec's related_commits array and commit_count is incremented. If task_id is provided, the commit is also linked to the task with a last_commit_at timestamp. |
| get_commit_messageA | Generate a conventional-commits-style message from spec/task context. No external AI call — derived from structured spec data already in the database. Returns a ready-to-use commit message string with type(scope): subject, spec/task references, file list, and co-authorship attribution. Use this before committing to get a well-formatted message. |
| create_keyword_clusterA | Create a strategic keyword cluster with its keywords in a single call. Each cluster groups related keywords sharing search intent and serves as a content brief with: strategic rationale, competitive landscape, target content type, and keyword assignments. Always include the keywords array — keywords that don't exist yet are auto-created as target keywords. Returns keywords_assigned and keywords_created counts to confirm what was added. Use this during keyword research conversations to organize findings into actionable clusters. Each cluster maps to one page and guides content creation. |
| get_keyword_clustersA | Retrieve keyword clusters with keywords, volume data, GSC performance, and audit status. Supports filtering by target_url (exact match), name (partial match), or cluster_id. Use target_url to find the cluster for a specific page (e.g., target_url: "/" for the homepage cluster). Without filters, returns all clusters. |
| create_content_specA | Create a page-type feature spec linked to a keyword cluster. The spec carries the content strategy (outline, goals, voice, inspiration); keyword data is resolved dynamically from the cluster at read time. Use this after creating keyword clusters to generate actionable content briefs. Each cluster maps to one page — the spec tells an AI agent exactly what to build. The spec auto-creates tasks: write content, optimize for keywords, add schema/meta. The response includes the spec_id. Use get_feature_spec with that ID to retrieve the full spec with live keyword data, volumes, and GSC performance. |
| lookup_keywordsA | Look up search volume, competition, CPC, and monthly trends for a list of keywords using DataForSEO. Results are cached for 30 days — repeated lookups for the same keywords are free. IMPORTANT: This calls a paid API. The response includes meta.from_cache and meta.from_api counts so you can see what hit the paid API vs cache. Always tell the user before calling this tool and how many keywords you're looking up. Use this to validate keyword demand during research conversations, before creating clusters. |
| suggest_keywordsA | Get related keyword suggestions for a seed keyword using DataForSEO. Returns up to 50 related keywords with search volume and competition data. IMPORTANT: This calls a paid API. Always tell the user before calling this tool and what seed keyword you're using. Use this to expand keyword research — find related terms, long-tail variations, and new cluster candidates. |
| optimize_contentA | Generate specific optimization instructions for a page based on its keyword audit results. Runs the content audit, then for each failing check produces actionable fix instructions: add keyword to title, increase density by N occurrences, add internal/external links, vary keyword formatting. Use this after reviewing a page with get_page_seo to get step-by-step instructions for improving keyword optimization. The AI agent reads these instructions and modifies the source files. Constraint: instructions preserve content structure (headings, sections, flow). Only text, formatting, and links are modified. |
| get_security_contextB | Get security analysis for a site (homepage scan only). Returns security score, detected issues (headers, SSL, exposed files, third-party scripts), and actionable remediation steps. PRIVATE BETA. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/rampify-dev/rampify-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server