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 分