Skip to main content
Glama
734,830 tools. Updated 2026-11-02 08:20

"Guide to Deploying a Website on Cloudflare Pages" matching MCP tools:

  • Discover current public pages, including website journeys and AI guide profiles. Categories: all, articles (blog paths), ai_guides, website. Pass content_revision on subsequent pages to detect a changing inventory. Read a page before citing it.
    ConnectorNo auth
  • Create new guides Create one or more new guides based on provided queries. Each guide targets exactly ONE engine and ONE analysis mode, chosen with the optional `source` field (default `google`). How to request each guide type: 1. Google SERP guide (1 credit per guide): omit `source`, or pass `source: "google"`. Example payload: {"queries": ["best crm"], "lang": "en-us"} 1bis. Google AI Overview guide (1 credit per guide). Two modes, like AI engines: `source: "google_ai_overview"` builds the guide from the TEXT of Google's AI answers (AI Overview, completed with AI Mode answers) ; `source: "google_ai_overview_citations"` builds it from the content of the web SOURCES those answers cite (recommended for GEO). Same language/country parameters as a Google SERP guide, 1 credit per guide in both modes. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "google_ai_overview_citations"} 2. LLM ANSWER guide (4 credits per guide): pass the engine name alone, e.g. `source: "chatgpt"`. The guide is built from the answer text the AI generates for the query. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt"} 3. LLM CITATIONS guide (4 credits per guide) [RECOMMENDED AI mode]: pass the engine name with the `_citations` suffix, e.g. `source: "chatgpt_citations"`. The guide is built from the content of the web pages the AI cites in its answer. Example payload: {"queries": ["best crm"], "lang": "en-us", "source": "chatgpt_citations"} Which AI mode to pick? For GEO (getting a page visible in AI answers), prefer `<engine>_citations`: AI engines send traffic by CITING pages as sources, so the winning move is to look like the pages they cite. The answer-text mode (`<engine>` alone) is mostly useful to analyze how the AI phrases its own answer. When in doubt, pick `<engine>_citations`. The same two modes exist for every AI engine (chatgpt, perplexity, claude, gemini, grok, mistral, deepseek). To optimize the same page for several engines or modes (e.g. Google AND ChatGPT answers AND ChatGPT sources), create one guide per source value on the same query. IMPORTANT, HOW TO READ THE RESPONSE OF THIS ENDPOINT, WHICH SPENDS CREDITS. Queries listed in `guidesFailed` are PROVEN not to have produced a guide and their credit was given back (unless the account has unlimited credits, where nothing was reserved): re-sending them is free and correct. Queries listed in `guidesUnknown` have an UNDECIDABLE outcome and their credit is deliberately KEPT, because the guide was most likely written: DO NOT re-send them, you would pay for the same guide twice. Look them up in `GET /api/v1/guides` after a few minutes instead, and contact support if nothing shows up. Finally, a `200` is NOT a promise that every query produced a guide: compare `guides.length` with the number of queries you sent, never read `success` alone, and never re-send a query just because it is missing from `guides`.
    ConnectorNo auth
  • Check whether AI agents can read, understand and act on any website (bots allowed, readable pages, product data, checkout, help). Reads up to 3 public pages; results are kept for 24 hours and public at requstory.com/ai-readiness/<domain>/. Faster and narrower than map_website. If status is "queued" or "running", call again with start=false.
    ConnectorNo auth
  • WebIntel Sitemap Scanner — $0.01 per call (x402 USDC on Base). Discover every page on a website. Give it a domain and get back its list of URLs — found via robots.txt and sitemap.xml, following sitemap indexes, up to 500 pages. Use it to map a site's structure before crawling or to find which pages are worth reading. Pay per call with x402, no account needed.
    ConnectorNo auth
  • Creates a new brand — from a website URL (scans the site for logo, colors, copy tone), guided answers (what you sell, who buys it) if there's no site yet, or connectSocialFirst if there's no website at all and the user wants to start from a connected Facebook/Instagram account instead (no site or guided answers needed). First step for a brand that doesn't exist in Rebbel yet. name is optional when websiteUrl or connectSocialFirst is given — Rebbel derives it from the site (or the connected page) and refines the guess once the scan/connect completes. Guided (no-website) creation still needs a name. For a website URL, the response includes a real summary of what the scan actually found (name, palette, logo, a voice sample) plus next steps — Rebbel writes the brand's first post's caption on its own: call draft_first_post a few seconds later to fetch it and approve_copy to make its photo (or draft_first_post count: 3-5 for a batch in the site's own voice), or generate_brand_guide for the full brand guide/strategy/ongoing campaigns. connectSocialFirst's response hands off a dashboard connect link instead (Claude can't drive the Meta OAuth dialog itself) — once the user connects, call draft_first_post right away for the same fast batch, or generate_brand_guide once the scan finishes for the full brand guide (check list_connections/list_brands if unsure it's done yet).
    ConnectorOAuth
  • Put a project ONLINE on the user's OWN Cloudflare account (a Cloudflare Worker at https://<name>.<their-subdomain>.workers.dev), built as a static site from the same pages as the Astro export. This is PUBLIC: only call it when the user asks to deploy or publish to Cloudflare, and tell them the address. The first time, the account is not connected yet: this returns a link the user must open to approve UiChemy on Cloudflare; after they have, call this again. If their Cloudflare login has several accounts, this lists them: ask which one and pass its `accountId`. Calling it again for a deployed project UPDATES the same site (its pages are replaced with the current design). Every deploy is a numbered version; uichemy_site_versions lists them and uichemy_restore_site_version puts an earlier one back online. Only generated pages are deployed.
    Connector
    Destructive
    OAuth

Matching MCP Servers

  • A
    license
    A
    quality
    C
    maintenance
    Enables AI agents to fetch one or many web pages concurrently and receive clean, LLM-ready Markdown with navigation, ads and boilerplate stripped away, plus extracted metadata such as title, description, author, Open Graph tags and canonical URL. It runs locally over stdio with no API key or account, requiring only a single command.
    3
    MIT

Matching MCP Connectors

  • Turn any webpage into structured JSON with CSS-selector schemas - strings select text, attributes

  • Cloudflare Solver: Scraping API designed to bypass Cloudflare protection.

  • Put a project ONLINE as an Astro site WITH the EmDash CMS on the user's OWN Cloudflare account (a Worker at https://<name>.<their-subdomain>.workers.dev, plus a D1 database and login storage in their account). The site's pages, sections and blog posts become editable content in its admin at /_emdash/admin. This is PUBLIC: only call it when the user asks to publish, deploy or go live with EmDash or a CMS on Cloudflare, and tell them the address. The first time, the account is not connected: this returns a link the user must open to approve UiChemy on Cloudflare; after they have, call this again. If their Cloudflare login has several accounts, this lists them: ask which one and pass its `accountId`. Calling it again for a published project UPDATES the same site and keeps its CMS content and users. After the FIRST publish the CMS is locked behind a one-time setup link: give it to the user. Publishing takes about a minute; this waits up to 40 seconds, then returns a jobId for uichemy_emdash_status. Only generated pages are published. For a plain static site without a CMS use uichemy_deploy_to_cloudflare.
    Connector
    Destructive
    OAuth
  • Use this when you must deploy to Cloudflare (wrangler deploy, upload a website to Cloudflare, publish a Worker with static assets, push a Pages build) and this chat has only the remote Connections MCP, no local tools. When the vault holds the Cloudflare account, NEVER ask the human for a Cloudflare or wrangler sign-in (wrangler login, a browser Allow click, an API token): Connections deploys with the vaulted credential and the chat never sees it. Mints a ONE-TIME deploy ticket bound to one account + one Worker script (or one Pages project): single use, expires in minutes (default 10, at most 15), grants nothing else. Reply: a URL and a curl recipe. Build the site, then POST the JSON bundle (modules, static assets, wrangler.jsonc text, bindings) to that URL with curl; Connections creates or updates the Worker server-side, inherits its existing bindings, and answers with the live workers.dev URL. Find accountId with connections_accounts { service: 'cloudflare' }. About 5 MB of base64 per ticket. With local tools use the local cloudflare_deploy tool instead (one call, reads wrangler.jsonc from disk).
    Connector
    Destructive
    OAuth
  • Fetch the Markdown for a single BANKSapi docs page. Accepts a docs path (e.g., /guide/quickstart) or a full URL; any .md/.html suffix and section index (e.g. /guide) are handled. For the API reference paths /api/banks-connect, /api/ai-connect and /api/pay-connect this returns a compact operation index rendered from the OpenAPI spec. Use when you need specific page content or code samples. Prefer 'search-banksapi-docs' for broader questions. Call 'get-banksapi-overview' first to get a list of available pages.
    ConnectorNo auth
  • Use when someone needs a published Rung occupation, resume-situation, or military-transition guide. Returns public guide facts, source pages, and browser handoffs. Do not use for live jobs, employer search, resume editing, qualification decisions, or private work history; never send personal or resume data.
    ConnectorNo auth
  • Create a new multi-page website in the workspace. The site starts empty: use add_page_to_site to build its pages, starting with the home page (slug "index"). To make a single standalone landing page instead, use create_page — that does not need a site.
    ConnectorOAuth
  • Regenerates one section of a draft brand guide (identity, voice, audiencePersonas = who it's for, offers, doList, or dontList), optionally steered by feedback. Use this instead of generate_brand_guide when the guide exists but the website scan was thin and you have real detail to add — generate_brand_guide only re-runs off the scan and would reproduce the same result. This rewrites the whole section from the website scan; to change specific lines and keep the rest exactly as written, use update_brand_guide instead.
    Connector
    Destructive
    OAuth
  • Use this when the user wants a public website or web page checked for accessibility (WCAG 2.1/2.2 AA, ADA, EAA, Section 508): it loads the live page in a real browser, runs axe-core on it and up to two more same-site pages, and returns a 0-100 score, a letter grade and the failing rules with example elements. Takes 15-40 seconds. Do not use it for pages that need a login, for localhost or private-network addresses, or for pasted HTML.
    ConnectorNo auth
  • Run a deployed workflow once, for real, with an optional JSON payload as its trigger input, and return what happened. A simple workflow answers with its HTTP status, duration and response body. A durable one (with a wait, delay, approval or sub-workflow) starts a run and returns its instanceId and status: follow it with get_run. Use it after deploying to show the user a real result. It runs in the user's Cloudflare account against their real services, so it has real effects, and Nodes2Cloud stores nothing about it. Counts toward this connection's daily limit on workflow calls.
    Connector
    Destructive
    OAuth
  • REST API access for autonomous agents — pricing, quick start, and migration guide. Call this when: building a trading bot, deploying an autonomous agent, hitting the MCP rate limit, or running 24/7 without a human in the loop. The MCP tier (what you're using now) is free via Smithery, rate-limited to 60 calls/minute per IP, and good for testing. The REST API is for production: pay per call in USDC; paid endpoints are rate-limited to 60 calls/minute and 200 calls/hour per wallet. No API key required.
    ConnectorNo auth
  • osirAppDeploy: Deploy an app to Osir (free tier) and get a live HTTPS URL; the app runs isolated in a microVM. Deploying an existing app name redeploys it (new version) and applies any secrets set via osirAppSetSecret. A plain static website (HTML/CSS/JS with no framework or build step) is also supported: it is auto-detected and served directly; pass language 'node' for it. To put the app on the user's OWN VPS, server or production box instead, deploy it here first and then call osirAppDeployToVps - never SSH into the box or write an install script. Once an app is on the user's own VPS, redeploying HERE under the same name is how you update it: the platform re-ships it to the box and keeps its domain. Requires authentication.
    ConnectorNo auth
  • Save a guide on a project. With guide_id it is a new version of that guide; with a name no main guide on the project has yet it starts a new guide (one project can hold many videos); otherwise it is a new version of the newest guide. kind "auth" is the login flow (never recorded, may use {USERNAME}/{PASSWORD}); kind "main" is the walkthrough that becomes the video. Call get_guide_instructions before writing a guide and validate_guide before saving it.
    ConnectorOAuth
  • Searches this account's brands and campaigns by keyword (brand name/website, campaign objective/angle/results), and answers product questions — "how do I connect Instagram", "what can Rebbel do" — from Rebbel's help and setup-guide pages. Returns {results: [{id, title, text}]} (identical campaigns collapsed into one row) and, when nothing matches, a plain note with a dashboard link instead of an empty array. Pass a result's id to fetch for the full record. Not a web search. Powers ChatGPT Deep Research and Claude's research modes.
    ConnectorOAuth
  • Request an Evolize accessibility assessment of a publicly reachable website, then read the result with get_scan_result. By default a completed assessment up to 24 hours old is reused; pass refresh=true to require newly executed work (for example after deploying a fix). This CREATES work: it can start a real browser-based scan whose result is retained and may become a public report under Evolize's existing publication policy. Free public assessments are bounded: a completed result up to 24h old is reused unless refresh=true, at most 3 newly executed assessments per website per 24h, and the platform's own per-IP, per-domain and global scan limits still apply.
    ConnectorNo auth
  • Export a project as an ASTRO website project (source code the user runs or hosts themselves: `npm install && npm run dev`, or deploy it to any static host). Returns a download link to a .zip that works for 15 minutes and up to 5 downloads; give the link to the user right away. Nothing goes online. Only generated pages are exported. Use this when the user asks for the code, an Astro project, a zip, or to host the site themselves. To put the site online on the user's own Cloudflare account instead, use uichemy_deploy_to_cloudflare; for a UiChemy-hosted WordPress site, uichemy_publish_site.
    ConnectorOAuth
  • Get statistics about the Lenny Zeltser's Website search index including total pages indexed, last update time, and available tools.
    ConnectorNo auth