Skip to main content
Glama
815,804 tools. Updated 2026-11-21 10:20

"A tool for allowing AI agents to fully control a Shopify site" matching MCP tools:

  • Buy credits for AI research. Default $5 minimum. Free — no credits consumed to call this. TWO PAYMENT METHODS: card (default): Returns a Stripe Checkout link for your user to click and pay. After payment, call check_balance to confirm credits were added. crypto: USDC on Base. Fully autonomous — no human needed. Three steps: 1. buy_credits(payment_method='crypto') → returns deposit address + payment_intent_id 2. Send USDC to the deposit address (use your wallet tool) 3. buy_credits(payment_intent_id='pi_...') → confirms payment, credits added instantly If you have wallet access, this is the fastest path — fully machine-to-machine.
    ConnectorNo auth
  • Checks whether AI assistants and AI agents can understand and act on a business from its public website, and explains what gets in the way. Use it when the user asks things like: "Does AI understand my website?", "What would an AI think this company does?", "Why doesn't ChatGPT know what my company sells?", "Is my site ready for AI agents?", "Audit this site for machine readability", "Can an AI figure out the pricing and how to buy or become a customer?", "What information is missing for AI to understand this business?", or after they changed their site and want to check the result. Returns a deterministic 0-100 AI Visibility Score across 8 dimensions (crawl access, business identity, offerings, pricing, structured data, trust, agent actionability, recommendation confidence), how AI would likely describe the business, what it could not determine, and the highest-impact issues, each with evidence (quotes and source URLs) and a one-line fix summary. Free. It never changes the website: it reads public pages the way AI crawlers do (raw HTML, robots.txt, structured data, llms.txt). When no recent analysis exists it runs one and stores the report on CanAIReadMe. It reuses an analysis up to 7 days old unless fresh=true (free re-analysis once per 24 hours per site). A site it has not seen takes about 10 to 40 seconds; if the result has status "running", call again with the returned scan_id. Do not use it to explain concepts (SEO, GEO, schema.org), for general SEO or marketing advice, to write content or build websites, to track brand mentions or rankings in AI answers (it does not measure those), or when no specific website is involved. To answer what a company does, sells or costs, use get_business_profile instead.
    ConnectorNo auth
  • Generates the complete, implementation-ready fix for the problems that stop AI systems from understanding a website. Use it when the user wants to fix what makes their site hard for AI agents to understand (its AI visibility), says "fix it" after an audit, wants to buy the AI visibility fix, or needs the exact changes (JSON-LD, meta tags, llms.txt) for a developer or a coding agent. Call it directly in those cases: it analyzes the site itself when needed, and its quote includes the current score and main problems to show the user next to the price. Delivers a machine-executable change list (target location, instructions, code snippets, before and after copy, validation criteria, score dimension affected), rewritten copy AI can understand, ready-to-paste schema.org JSON-LD, meta tags, llms.txt and robots.txt rules, FAQ answers, and 5 private re-scans over 60 days to verify the result. Paid: $49 one-time per website, not a subscription, refundable within 14 days. Calling this tool never charges anyone, so call it without asking first: the quote is free and safe. Without a completed purchase it returns status "payment_required" with the price, what is delivered, a purchase_id, an access_token and a secure Stripe checkout link. Then show the user payment.user_message (score, main problems, price, refund) and share the link only if they agree; the user reviews and pays on Stripe's page. After they pay, call again with purchase_id and access_token to receive the package. Pass an idempotency_key (a new UUID per purchase): retries with it return the same purchase and link instead of a second checkout. CanAIReadMe does not modify the website: apply the changes only with the owner's permission. If the user only wants to know what is wrong, use audit_ai_visibility instead. Do not use it for general advice or for a site the user has not asked to fix.
    ConnectorNo auth
  • Local-business readiness for AI search answers. Use this when the user asks if a local business site is ready to be named by AI search, ChatGPT, Gemini or similar, or what to fix so assistants can cite it. Pass the business's own site. Crawls only that site's public pages (robots.txt respected, up to 25, default 15) and returns pass, warn or fail for a page per service, location or service-area pages, visible prices, FAQ, LocalBusiness schema (name, address, phone, hours, geo, sameAs), NAP consistency, on-site proof, a one-line description and recent dated content. Each check has the evidence URL and a fix. Also returns what Gemini, OpenAI and Anthropic leaned on in a Yext study and profile advice, which is not fetched. It does not query AI engines, directories or review sites, or measure rankings. Not for a site with no physical location or service area: use audit_site. Do not use it for private addresses or to collect contact details.
    ConnectorNo auth
  • Create a website for an AI agent from its facts. Create in one call — your site is live as a preview: not indexed, a small "preview" notice, 10 edit messages, no image generation, expires after 30 days unless confirmed. Returns the site URL and a site key (shown once). Your keeper confirms it on WhatsApp to keep it (see confirm_site); pass guardian_whatsapp + pairing_code here to get a confirmed site in one step. Free for the first 1000 agents (confirmed sites). By creating a site you accept https://stimhaus.ai/cgv.
    ConnectorNo auth
  • For agents that make their own HTTP requests (scripts, Claude Code): WordPress REST API credentials for a Cloud for WordPress site. To edit content from here, use wordpress_request and wordpress_upload_media instead: they need no credentials. Mints a WordPress Application Password for the site so you can drive it over the WP REST API at https://<domain>/wp-json/ using HTTP Basic auth. The password is returned ONCE (WordPress stores only a hash) — save it immediately. Defaults to a dedicated least-privilege `porkbun-agent` user with the `editor` role (created on first use), which can manage content but cannot install code. `role: "administrator"` grants FULL site control including plugin installation (i.e. arbitrary code execution on the site) and therefore requires `acknowledge_full_access: true` — only request it if the user explicitly asked for admin-level access. The site must be provisioned and ACTIVE (poll get_hosting) — this works on any Cloud for WordPress site in the account however it was provisioned, but free $0 preview sites are excluded. Revoke any time with delete_wp_credentials. Rate limit: 20 mints per account per hour.
    ConnectorOAuth

Matching MCP Servers

Matching MCP Connectors

  • Git AOAuth

    Many AI agents on one repo, every change lands on main. Read code, propose changes, review, read CI.

  • AI agents hire a human to observe, log or film on site. Typed results, feasibility before payment.

  • PRO+ AI scheduling tool for agents. Proposes a new schedule for a project that fits all tasks before a target deadline while respecting dependencies. Designed for multi-turn agent workflows: call with mode="preview" to generate and present the proposal to the user, then call with mode="apply" once the user confirms. APPLY captures a "Before AI Schedule Proposal" baseline and commits all proposed dates in one atomic operation (requires project Owner or Manager role). Optionally levels resources to avoid overallocation. Cap: 100 tasks. Feature: aiAdvanced (PRO+).
    Connector
    Destructive
    OAuth
  • Retrieves statistical summary data and domain-level findings from the 2026 50-Site SaaS & E-Commerce AI Truncation Study, returning a Markdown report with JSON metrics on 25,000-token RAG cutoff rates (74%), visible price omission (62%), /llms.txt adoption (87%), and ARD 1.0 adoption (19%). Use this tool when comparing a website against industry peers (such as Stripe, Vercel, Datadog, or Shopify) or citing empirical benchmark statistics; do not use it to run a live scan on an arbitrary URL (use audit_ai_readiness instead). When domain is omitted or empty, returns the full 50-site aggregate dataset; when a bare domain is provided, normalizes case/protocol and checks whether that domain appears in the top-truncating cohort. Read-only static dataset lookup; requires no API key, makes zero external network calls, and never fails on unknown domains.
    ConnectorNo auth
  • Overwrites the fields you pass; previous values are not kept and cannot be restored from the API, so confirm changes to the prompt, name or settings with the user first. Update a saved AI agent (PUT /v2/agents/:agentId). All fields are optional - only what you pass is updated. Common uses: tune the system `prompt` after a test run, switch `responseMode` to control turn-taking in multi-agent rooms, or adjust `cooldownSec`. See `ethora-agents-quickstart` prompt for the end-to-end recipe. Requires: an agent id or address from `ethora-agent-list` or `ethora-agent-create`. Only the agent's owner can update it: a public agent from someone else, including the platform's Support Agent, answers 403, so `ethora-agent-clone` it and update the copy.
    Connector
    Destructive
    No auth
  • Live check of ANY online store, tracked by Neoavis or not: can an AI shopping agent read it without clicking? Reads the UCP checkout profile (/.well-known/ucp), structured product data, robots.txt access for shopping agents, llms.txt and sitemap, in a few seconds. Use it when the user wants to buy from a store that consulter_marchand does not know, or wants to know if their own store is ready for AI agents. For a store Neoavis already tested, consulter_marchand gives the full purchase test. Returns: points (out of 15), verdict (pret, partiel or pas_pret), criteres_reussis, neoavis (score out of 100 and page when tracked), resume (one sentence to quote), detail_gratuit_humain (page with the per-criterion detail for a human) and suites_payantes (x402 URLs, USDC on Base, no account: per-criterion live check, and a full purchase test). Free: 10 checks per hour per address. Unreadable domain or unreachable site: error result.
    ConnectorNo auth
  • **\[Shopify Shipping Profile\]** **\[What it does\]** Creates one Shipping Profile with one zone and one custom flat rate in one exact Shopify store. Shopify only; WooCommerce, eBay, and other sales channels are rejected before the write. **\[When to use\]** Use when the user wants a new Shopify Shipping Profile before publishing products. **\[When not to use\]** Do not use it to select an existing profile; read current choices from `list_stores.stores[].shipping_profiles`. Do not use it for non-Shopify stores or when `list_shopify_shipping_zones.shipping_zones` is empty. **\[How to use\]** First call `list_stores`, select one exact row whose `sales_channel_name` equals Shopify case-insensitively, and copy its `dsers_store_id`. Then call `list_shopify_shipping_zones` for the same store, copy one or more returned `shipping_zones[].country_code` values into `country_codes`, and copy its `currency` exactly. Choose a `zone_name` that describes the selected countries, then provide the profile name, custom rate name, and non-negative amount. The service creates exactly one zone and rate. After success, call `list_stores` again and use the returned profile and location IDs for product publishing. This write is not idempotent; if the result is unknown, inspect Shopify and `list_stores` and never retry automatically. **\[Side effects\]** Creates a Shipping Profile in the selected Shopify store. **\[Confirmation\]** Requires explicit confirmation showing the store, profile, zone, countries, rate name, amount, and currency.
    ConnectorOAuth
  • **\[Order\]** **\[What it does\]** Asynchronously requests a Shopify fulfillment tracking notification for the buyer of one owned order; Shopify only. **\[When to use\]** Use when the merchant wants Shopify to notify the buyer about tracking for fulfilled items that already have tracking information. **\[When not to use\]** To fulfill items or synchronize tracking to the seller store, use `sync_existing_tracking_numbers_to_store` first. This tool does not apply to non-Shopify platforms. **\[How to use\]** - Copy one exact `dsers_order_id` from `get_order` after checking the fulfilled items and tracking information. The request is order-wide and cannot select a subset of line items. - A successful response contains only `message`: it means DSers accepted an asynchronous notification request, not that Shopify sent it or the buyer received it. Shopify may suppress an identical recent update. - Send once, never auto-retried. If the outcome is unknown, check the Shopify order and buyer notification history before deciding what to do; `get_order` can confirm order and tracking prerequisites but cannot confirm notification delivery. **\[Side effects\]** May send an external tracking notification to the buyer. **\[Confirmation\]** Required, never skippable: show the exact order, eligible fulfilled items, and tracking information, and state that this may contact the buyer. **\[Follow-up\]** After acceptance, check the Shopify order and buyer notification history later; if rejected, report the error and stop.
    Connector
    Destructive
    OAuth
  • **\[Tracking Number / Fulfillment\]** **\[What it does\]** Synchronizes the tracking numbers already stored on one DSers order to the sales channel. After synchronization, the sales channel may automatically update the order's shipment or fulfillment status. **\[When to use\]** Use after the supplier has shipped and the DSers order already contains the correct tracking numbers that need to be synchronized to the store. **\[When not to use\]** This Tool does not accept new tracking numbers or support selecting specific items. To provide new tracking numbers for selected sales-side items, use `update_tracking_numbers_to_store`. Use `get_package_details` to inspect tracking events. Before calling this Tool, use `get_order` to review the order items and existing tracking numbers. **\[How to use\]** - Copy `dsers_order_id` from `get_order`. Order ownership and currently eligible items are validated before synchronization. - Keep `switch_fulfillment_service=false` for the normal synchronization path. - `switch_fulfillment_service` is supported **only for Shopify orders**. Set it to `true` only when normal synchronization fails because the Shopify items are assigned to another fulfillment service and the response explicitly instructs you to switch. - Switching the fulfillment service may assign the affected Shopify items to the DSers fulfillment location and affect future orders for those items. Non-Shopify orders must keep this value `false`. - A successful response means only that the synchronization request was accepted. It does not confirm that the sales channel has completed the tracking-number update or fulfillment. - This operation is not idempotent. If the outcome is unclear, refresh `get_order` and the sales-channel order instead of retrying automatically. **\[Side effects\]** May update the tracking numbers, shipment status, and fulfillment status of the sales-channel order. The Shopify switch path may also change the fulfillment location assigned to the affected items. **\[Confirmation\]** Always required. Before calling this Tool, show and confirm the exact store, order, currently eligible items, existing tracking numbers, selected synchronization path, and any possible Shopify fulfillment-location changes.
    Connector
    Destructive
    OAuth
  • Fetches up to 32KB of the domain's HTML and response headers from the edge, then fingerprints the content for known CMS platforms, JavaScript frameworks, CDN providers, and analytics tools. Detection is based on meta generator tags, script src patterns, response headers, and cookie names. Use this tool when: - You need to know what CMS (WordPress, Drupal, Shopify) a site runs. - You are assessing a domain's infrastructure before a security review. - You want to identify analytics or marketing tools a site embeds. Do NOT use this tool when: - You want HTTP headers and security posture — use `intel_http` instead. - You want tracker database classification — use `get_domain` instead. - You need robots.txt AI policy — use `intel_robots` instead. Inputs: - `domain` (query, required): Domain to fingerprint. Returns: - `cms`: detected content management system, or null. - `frameworks`: JavaScript/backend frameworks detected. - `cdn`: CDN provider detected, or null. - `analytics`: analytics and tracking tools detected. - `meta_generators`: raw meta generator tag values. Cost: - Free. No API key required. Latency: - Typical: 2-4s (HTML fetch), p99: 7s.
    ConnectorNo auth
  • Live AI-visibility scan for a brand: crawl + reputation sampled across AI engines, returning where *that* brand is mentioned (any public brand, not just your own). Use when you want to know whether and how a named brand already surfaces in AI answers — complementary to search_companies, which finds who agents recommend for a category. Pro+ (LLM cost). Result: { reputation[], tool_schema_version }.
    ConnectorNo auth
  • Upsert a key/value in the user's encrypted variable store (UPPER_SNAKE name, ≤8 KiB value). Use for API keys the user's sites/agents need, e.g. SUPABASE_URL. NOTE: saving alone does NOT expose it to any site Worker's env — attach it to a specific site with attach_variable (takes effect on that site's next function deploy).
    ConnectorNo auth
  • Generate a complete, spec-correct llms.txt file from structured input — the generator counterpart to this server's checkers. You supply the site name, a one-paragraph summary and optional sections of curated links; the tool renders canonical llms.txt markdown: an H1 with the site name, a blockquote summary, then one H2 per section with '- [name](url): description' link bullets. The result is returned as ready-to-publish text (serve it at https://yourdomain.com/llms.txt as plain text) plus structured metadata (byte size, section/link counts). llms.txt is the curated site map AI systems read first — Shopify serves one natively, and AI-readiness scanners (including agent_readiness_scan and check_wellknown_discovery on this server) check for it. Pure function: no network calls, deterministic, free, unlimited within fair use. Related free web tools and pay-per-call agent APIs (x402 protocol, $0.005/call, USDC on Base, no account) at https://x402.agiscorecard.com.
    ConnectorNo auth
  • L3 Empathy Response Strategy: converts text into a deterministic response strategy (approach, tone temperature, pacing, focus points, avoid-list) for AI companions and conversational agents. Deterministic table lookup, no LLM, ~20ms; privacy-first. Not a medical or therapeutic tool.
    ConnectorNo auth
  • Scan any public website and get Build My Digital's free report: a 0 to 100 score across SEO, AI search (GEO), local signals, trust, conversion and speed, every check with pass or fail, the fixes in priority order, and a separate agent-readiness score (can AI agents find, read and act on the site) that never changes the main score. Use when someone asks how good a business website is, why it is not being found, or what to fix first. UK local businesses are the focus but any public site works. Takes 5 to 40 seconds. Read-only: nothing on the scanned site is changed.
    ConnectorNo auth
  • Search the Beste KI Tools catalog of live, published AI tools by a free-text query. Matches on tool name, tagline, or category name (case-insensitive substring). Call this first when a user asks to find, discover, or compare AI tools by keyword, use-case, or category (e.g. 'agents', 'writing assistants'). Returns up to 20 results.
    ConnectorNo auth
  • Search the Alternativas IA catalog of live, published AI tools by a free-text query. Matches on tool name, tagline, or category name (case-insensitive substring). Call this first when a user asks to find, discover, or compare AI tools by keyword, use-case, or category (e.g. 'agents', 'writing assistants'). Returns up to 20 results.
    ConnectorNo auth