Rampify

dev.rampify由 rampify.dev 发布官方发布者v1.1.0更新于 Nov 1, 2026

Turn your coding agent into a marketing agent: search data, specs to build, fixes verified by scan.

已验证Streamable HTTP可网页运行效率与工作流网页搜索与抓取开发者工具

概览

AI 生成的概览

远程 MCP 服务器,把编码智能体接入网站的 SEO 与搜索数据,将发现的问题转成规格,由智能体实施并在下次扫描中验证。

可以做什么
  • 抓取并扫描网站,检查 meta、结构化数据、内容与 Core Web Vitals
  • 读取 Google Search Console 表现与关键词数据,进行关键词研究与聚类
  • 生成标题、meta 描述与 JSON-LD
  • 创建带任务和关联提交的功能规格,并跟踪活动状态
  • 运行研究剧本,检测 AI 助手回答中是否提及你的品牌
适用场景
适合希望让编码智能体端到端处理 SEO 与内容工作的场景:审计页面、研究关键词、编写规格、在代码库中提交修复,并在下次扫描时确认效果。
运行要求
远程服务器,位于 rampify.dev,无需安装。通过 OAuth 登录,无需管理 API 密钥。需要支持 MCP 的客户端,如 Claude Code、Cursor、VS Code 配合 Copilot 或 claude.ai,并需要 Rampify 账号、已连接的站点及 Google Search Console 访问权限。
安装前请注意
登录后会授予服务器访问站点 Search Console 数据并抓取站点的权限。规格与任务会写入你的账号,提交会与规格关联,代码库改动由你的智能体执行。定价为免费起步但存在付费方案,使用前请查看定价页。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Rampify,将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储,绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/dev.rampify%2Frampify-mcp/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

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

README

Rampify MCP Server

Turn your coding agent into a marketing agent. Rampify connects Claude Code, Cursor, GitHub Copilot, or any MCP client to your website's search data. It scans your site, writes what to fix or build as specs your agent ships, and confirms each fix on the next scan, across Google search and AI answers.

Website · Product · Docs · Connect

How it works

  1. Scan. Rampify crawls your site and reads your Google Search Console performance and keyword data.
  2. Spec. Each gap becomes a spec: the pages and files it affects, the tasks, and how to tell it's done.
  3. Ship. Your agent makes the change in your repo and links the commit to the spec.
  4. Verify. The next scan checks the fix and closes the spec, or reopens it if the problem comes back.

Why Rampify

  • Real data, built in. Keyword volumes (via DataForSEO), your Search Console performance, and a live crawl of your own site. No separate data servers to bolt on.
  • Specs, not suggestions. Findings arrive as work your agent can pick up, with the same paper trail as your engineering: tasks, commits, and a status you can trust.
  • Fixes are checked, not assumed. A spec is done when the next scan confirms it, not when someone says so.
  • Find your blind spots. Playbooks like the Category Visibility Check ask AI assistants the questions your buyers ask, show whether they name you, and file a spec for the biggest gap.

Connect

Rampify is a remote server at https://www.rampify.dev/api/mcp. Nothing to install or update, and you sign in with OAuth, so there are no API keys to manage.

Claude Code

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

Cursor (.cursor/mcp.json), or any client that takes a URL

json
{  "mcpServers": {    "rampify": { "url": "https://www.rampify.dev/api/mcp" }  }}

VS Code and GitHub Copilot: install the Rampify extension. It connects Copilot in one click and shows your specs in the sidebar.

claude.ai: add a custom connector with the URL above.

Step-by-step for each client: Connecting guide →

Things to ask once you're connected

  • "Crawl my site and show me which pages are invisible when buyers ask AI assistants about my category."
  • "Research keywords for /pricing, then write the content spec."
  • "Audit the meta and schema on my top pages, and open a PR with the fixes."
  • "What should I work on next?"

What your agent can do

More than 50 tools: crawl and scan pages (meta, schema, content, Core Web Vitals), page-level intelligence, Search Console performance, keyword research and clusters, title, meta and JSON-LD generation, feature specs with tasks and linked commits, research playbooks, and campaign tracking. See the full tool catalog →.

Learn more

About this repo

This repo holds Rampify's public listing metadata: server.json for the official MCP Registry (dev.rampify/rampify-mcp), the Cursor plugin manifest (.cursor-plugin/, mcp.json), and glama.json. The server itself runs at rampify.dev.


Looking for the old @rampify/mcp-server npm package? It is deprecated in favor of the hosted remote server above (zero install, always current). Its source is in this repo's history, last at 9e160f0.

来源:README.md,提交 095f596

工具

0
该服务器需要登录,因此 SourceWeft 无法在没有账号的情况下读取其工具,也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

2
  1. v1.1.0最新Nov 1, 2026
  2. v1.0.0Sep 16, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分