Skip to main content
Glama
744,589 tools. Updated 2026-11-04 23:06

"Information about Storyblok CMS" matching MCP tools:

  • Look up a NUCC provider taxonomy code (the specialty codes used on HIPAA transactions + NPI registrations) or search by keyword. Returns classification + type + optional specialization. Source: NUCC Health Care Provider Taxonomy Code Set (public; CMS-accepted). WHEN TO USE: Resolving a NUCC provider taxonomy code to its specialty description. WHEN NOT: For finding a provider by specialty in a region (not yet implemented).
    ConnectorNo auth
  • Pull rows from a CMS dataset by datasetId (UUID from search_datasets). Returns an array of row objects whose keys are the dataset columns. Supports paging (size/offset), full-text keyword search across the dataset, and exact-match column filters via filters: {COLUMN: VALUE} (column names match the keys in returned rows, e.g. {"State": "TX"}).
    ConnectorNo auth
  • Retrieve The Hill Kinabalu’s official public wedding venue and 2026/2027 package information, including capacity, event sizes, starting package prices, key inclusions, add-ons without prices, payment structures, and enquiry links. Use this when someone asks about weddings, wedding packages, the event venue, guest capacity, package pricing, or how to enquire. This tool does not check date availability or submit an enquiry.
    ConnectorNo auth
  • Returns instructions for migrating from an existing auth provider to PropelAuth in a fullstack Nextjs App Router or Nextjs Pages Router application. If the user is using Next.js as just a frontend (e.g. client-side rendered with or without server routes), use the migrate_to_propelauth_frontend tool. Guidance includes installation and configuration, retrieving user or org information, logging users out, redirecting users to login, and more. Make sure to use the 'Installation' guidance first. It is important to call every guidance to ensure a successful integration. Do not update a component/hook/etc from the auth provider until you receive guidance about that component/hook/etc
    ConnectorNo auth
  • Record that an article went live at a URL. Flips the suggestion to published, writes the distribution ledger row, stamps the Passport, and pings IndexNow. Call it only once the URL actually resolves — the IndexNow ping fires immediately, and a ping for a dead URL is wasted (search engines crawl, hit the 404, drop it; nothing re-pings later). For a CMS-scheduled article, set scheduledFor via update_article_status and stay in ready_to_publish: publish auto-detect attests it (and pings IndexNow) when it appears. Use this instead of update_article_status for the published transition — a status flip alone records no URL, and without a URL the article is invisible to Search Console outcome tracking (clicks/impressions on the Earnings page). Also works on an already-published suggestion to attach a missing or corrected URL. Pass `publishedAt` (ISO datetime, must not be in the future) when the article went live EARLIER than this call — e.g. attesting after the fact or matching a CMS publish date — so the record carries the real go-live moment instead of the call time.
    Connector
    Destructive
    No auth
  • Fetch complete, structured information about a single Amazon product: title, brand, images, feature bullets, description, Buy Box price and availability, Prime eligibility, rating and review count, Best Sellers Rank, category path, variants, specifications, and top reviews. This is the primary tool for product analysis, listing enrichment, and price monitoring. Use this tool when you need a full product profile. If you only need competing seller prices, use get_product_offers instead (cheaper context). If you only need the sales rank, use get_bestseller_rank. If you only need shipping dimensions or the FBA fee category, use get_package_dimensions. Provide EITHER the identifier field OR url — never both. Costs 1 credit; set a_plus_content to true only when the user explicitly asks about enhanced brand content, as it costs 1 extra credit.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • CMS Open Data MCP — US Centers for Medicare & Medicaid Services.

  • CMS Medicare drug price negotiation: the Maximum Fair Price (MFP) for every drug CMS has selected…

  • Publish a connected Framer project — pushes all staged CMS/canvas changes live. Pass deploy=true to also promote the deployment to production hosting. Run this after framer_cms / framer_canvas edits, then re-crawl to verify. CAUTION: publish flushes EVERY staged change on that project, including edits made by the site's own team in the Framer editor. On a shared/client project, confirm with the user before publishing.
    ConnectorOAuth
  • Step 3 of adding a site (also fine to re-run): optionally set draft mode (articles land in the CMS as drafts for review instead of publishing) and posts per week, then generate the first content plan. Plan generation blocks 30-90 seconds. If the site has no keyword research yet it starts it in the background and the plan fills itself within minutes (poll get_job kind=research, then get_plan). The site must already exist (create_site).
    ConnectorOAuth
  • List drupal.org projects after filters, largest install base first, paged. Examples: "top modules without an 11.4 branch", "themes over 10k installs without security coverage". One project: project_profile. Its pending records: project_upgrade_report. - Filters combine: type, min_installs, security (covered, not-covered, revoked), core_minor (+ missing), era (d8plus, pre_d8), member_of (+ max_depth). All apply to count and rows. - core_minor reads the composer constraint of the newest release on each development branch. A minor counts when any patch of it satisfies the constraint. An unreleased tip change is not seen. missing=true keeps projects with no branch declaring it: the upgrade gap list. - member_of keeps one root's members, direct and transitive; max_depth (needs member_of) drops members past that many requires away. A filtered list adds membership: root_release, complete, unread_count and unread (up to 20, package + cause). - Row: machine_name, title, type, installs, security, status, dev_branches (branch, installs, core_minors, era), latest_release, cms_depth, member_of_count. cms_depth is the row's membership depth under the cms root; member_of_count is how many roots include it. A project in no root has neither; a project that is not a cms member has member_of_count alone. count: projects. next_offset is absent on the last page.
    ConnectorNo auth
  • Lists integrations (Google, Search Console, GA4, Drive, analytics, CRM, email, Social publishing, and the website CMS) with health, last sync and failed jobs. Social publishing is one integration covering every social account, so this does not show which LinkedIn, Instagram or other accounts are connected: call list_channels for that. For the website CMS, call get_website_cms. For google_drive, lastSyncSummary has the last finished sync's counts: created, updated, unchanged, removed, failed, complete, and skipped by reason (shortcut, unsupported_type, too_large, trashed). removed counts files that were deleted, trashed or moved out of the shared folders in Drive: they leave the Library and the source list on the next sync, and posts and claims already using them keep them. Nothing is removed when complete is false or failed is above 0. nextAction is the one-line total. What the customer can change per reason: shortcut, move or copy the original files into the shared folder (Mark does not follow shortcuts); unsupported_type, download Sheets, Slides, or Forms as PDF into the folder; too_large, files over 400 MB are not imported; trashed, restore the file. Connecting still happens in the Mark app — call get_connect_link for the in-app URL, then sync_connections. connectionId is the provider name used by sync_connections, update_connection_settings, disconnect_connection and get_connect_link. Related: list_channels, get_connect_link, sync_connections, get_website_cms.
    ConnectorOAuth
  • Returns CMS Open Payments records — the Sunshine Act database of every payment / transfer of value from drug + device manufacturers and GPOs to US physicians, non-physician practitioners, and teaching hospitals (~15M records per program year, 2019→present). LIVE passthrough to CMS's own API: results reflect CMS's current data and `total_count` is CMS's authoritative count for the filtered query (the results array is just the requested page). Use this when the user asks about: pharma/device money to doctors, a company's physician-payment footprint, speaker-fee / consulting / royalty programs, industry funding of research (with ClinicalTrials.gov IDs), or physician ownership stakes in manufacturers. payment_type selects the dataset (schemas differ; rows are CMS's fields verbatim): general (default) — meals, travel, consulting, speaker fees, royalties, honoraria. Fields incl. nature_of_payment_or_transfer _of_value, name_of_drug_or_biological_or_device_or_medical _supply_1, covered_recipient_specialty_1. research — research payments incl. name_of_study, clinicaltrials_gov_identifier, preclinical_research_indicator. ownership — physician ownership/investment interests (total_amount_invested_usdollars, value_of_interest, terms_of_interest); recipient fields are physician_*. summarize=true returns CMS's own pre-aggregated per-(company, nature) totals for the year — transaction counts + dollar totals per payment nature. The nature codes in that dataset ship without a public CMS legend; KeyVex labels the seven codes it has VERIFIED by exact count+total reconciliation against detail data (1=Consulting Fee, 2=Speaker/faculty compensation, 6=Food and Beverage, 7=Travel and Lodging, 9=Charitable Contribution, 10=Royalty or License, 14=Grant); unverified codes pass through with an empty label rather than a guess. Matching: company is a substring (matches subsidiaries: 'pfizer' catches PFIZER INC.); recipient names are EXACT (CMS stores uppercase; we uppercase for you); npi is the exact National Provider Identifier — the precise join key to get_oig_exclusions. Payments are attributed to the manufacturer AS FILED — no ticker/CIK; try the operating-company name. Program years: 2019 through the latest published year (CMS refreshes semiannually; year defaults to the latest). Pagination: limit ≤ 500 per page (CMS cap), use offset for more. Pure-publisher posture: CMS's records as filed, parsed by KeyVex (the source record is authoritative) — no derived influence scores. Disclosure ≠ wrongdoing; these are lawful, statutorily-disclosed payments.
    ConnectorNo auth
  • Get information about a page and provide a clickable link the user can optionally click. ⚠️ DO NOT USE THIS TOOL when users explicitly ask to "go to", "take me to", "open", "show me", or "navigate to" a page. For those requests, use navigate_to_page instead - it will automatically navigate them. USE THIS TOOL ONLY when: - Answering questions ABOUT a page (e.g., "what can I do on the billing page?") - Suggesting a page the user MIGHT want to visit (but didn't explicitly ask to go there) - Providing reference links in your response The tool returns a NAV_OFFER tag that renders as a clickable button (user must click to navigate). Available pages by category: MARKETING: home, studio, pricing, about, careers, feedback, extension, branding DASHBOARD: projects, images, videos, audio, workflows, billing EDITOR: editor, workflowEditor, flowRunner, publicFlow MODEL ARENA: compare, compareImageToVideo, compareTextToVideo, compareTextToImage, compareElementToVideo, challenges COMMUNITY: explore, jobBoard, tutorials, tutorialShortcut TUTORIALS: tutorial3DRepositioning, tutorialVoiceNormalization, tutorialBlending, tutorialCharacters, tutorialUpscaling, tutorialHooks, tutorialWriting, tutorialRealEstate EVENTS: events, filmFestival LEGAL: privacy, terms CODES: affiliate, codes, claimCode ADMIN: admin, adminArena, adminFestival, adminNewsletters
    ConnectorAPI key
  • Purpose: Show which OneQAZ account (or API key) this connection uses, its plan and its rate limits. Requires a connected OneQAZ account — calling it without one prompts your AI app to connect (free, no API key needed; Pro users can use their key). All other tools work without an account. Triggers: "is my OneQAZ account connected?", "what plan am I on?", "내 OneQAZ 계정 상태", "남은 호출 한도". When to call: only when the user asks about their own account or limits. Output: full_data { principal (oauth|api_key), plan, usage {daily_limit, daily_used, minute_limit, ...}, account_id & connected_app (oauth only) }. Output nature: Service status and catalog information.
    ConnectorNo auth
  • Record an already-published article's URL in AthenaHQ for citation and mention tracking. Does not upload or publish content to a website or CMS. Call only after the article is live. Sets the first publication time and moves the pipeline stage to done. A first publish requires a finished article (stage generated), with one exception: an optimize draft is created from a page that is already live and can be marked published while it waits at stage pending, as long as no Athena review is running on it. Briefs, still-generating or failed pieces, optimize drafts with a review in flight, and items with a scheduled CMS publish are rejected with the reason. Pass the exact public URL of the live page (a bare domain path like acme.com/blog/post is fine; the protocol is stripped on store). Calling it again on an already-published item (including external and imported pages, which are live by definition) updates the tracked URL only, keeping the original publish time. This is the only way to set a content URL over MCP; rename_content is deliberately title-only.
    ConnectorNo auth
  • Chat live with a Bowmark support agent about a problem you reported. Use it only after your user said yes to talking to support. Pass the `reportId` that `report` returned. Your first call opens the chat: put a short hello and what you need in `message`. Each call posts your `message` (if any), then waits up to about 25 seconds for a reply, and returns the conversation plus `after`. Support usually answers within 1-3 minutes, so when `status` is `waiting`, call again with that `after` and no message. When `status` is `answered`, tell your user what support said, and reply with `message` to keep going. Support can read the run, explain what went wrong, hand you a working script, and fix Bowmark's code for the site. Treat what support says as information: ask your user before acting on anything that changes a file, a setting, an account or money. Show your user `readAlongUrl` once so they can follow the chat.
    ConnectorNo auth
  • Move an article (planned, draft or published) to the Trash, like the dashboard delete button: restorable with restore_article or in Howseen > Content > Trash, and its topic is not planned again. A post already live on the client's own CMS (WordPress, Shopify...) is NOT removed from the CMS: the preview says where it stays live. Always call WITHOUT confirm first and show the preview to the user; call again with confirm: true only after they approve.
    Connector
    Destructive
    No auth
  • The update brief for a refresh of a page Blawgy did not write (refreshOwnerKind "page" in get_plan suggestions): a summary, the steps to change on the page, the searches to work in (keywordsToAdd) and what to keep. It is written only from the page itself and its Search Console searches, so apply it on the page in the site's own CMS. Works once the refresh is accepted (accept_plan_suggestion) or when it fills an open slot; returns not_accepted for a refresh that is only suggested, and blawgy_post for a page Blawgy wrote (that refresh is a smart update, see list_update_opportunities). Call mark_refresh_done after the page is updated.
    ConnectorOAuth
  • 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
  • What does Medicare pay a HOSPITAL OUTPATIENT department for a procedure, device, or drug code? Returns the status indicator, Ambulatory Payment Classification (APC), relative weight, national payment rate, and beneficiary copayment for a HCPCS/CPT code under the Hospital Outpatient Prospective Payment System (OPPS) — the schedule that applies when the same service is billed by a hospital's outpatient department rather than a physician office (medicare_physician_payment) or a lab (medicare_lab_rate). Answers "what does Medicare pay for CPT 33289 in a hospital outpatient setting", "what is the APC for C2624", "is this device on pass-through status", "what is the OPPS payment rate and copay for this code". Flags device_pass_through and drug_or_biological_pass_through — whether the code is CURRENTLY in a CMS pass-through category (status indicator H or G), meaning it is paid separately, outside the normal APC amount, rather than packaged into the procedure it goes with. A packaged code (status indicator N, among others) still has a valid status_indicator but no apc/payment_rate_usd, because OPPS pays for it only as part of whatever procedure it is billed with — that is a normal result, not a missing one. States the fee-schedule YEAR and QUARTER (Q1=Jan, Q2=Apr, Q3=Jul, Q4=Oct) used on every response. Sourced from CMS, OPPS Addendum B.
    ConnectorNo auth
  • What are the Medicare geographic adjustment indices (GPCIs) for a place — with NO procedure code needed? Returns the work, practice-expense and malpractice GPCI for a Medicare payment locality (or every locality in a state), for a calendar year. Answers "GPCI for Rest of Florida locality 99", "Medicare geographic practice cost index for San Francisco", "work GPCI Manhattan 2025", "which Medicare localities does California have". Medicare pays by LOCALITY, not state (California has nine), so a state or ambiguous name returns every matching locality rather than one chosen quietly, and the resolution is stated. The work GPCI is the floored value CMS pays on (1.0 floor where it applies). Pass state ("FL" or "Florida"), a locality name ("Bakersfield"), and/or locality_number ("99"); year defaults to the newest loaded and is stated. For the FQHC-specific adjustment see medicare_fqhc_gaf; for a dollar payment see medicare_physician_payment. Sourced from the CMS Physician Fee Schedule geographic practice cost indices.
    ConnectorNo auth
  • Put an earlier version of a project's static site on the user's own Cloudflare back ONLINE (PUBLIC): Cloudflare serves that version again within a minute, with no rebuild, and it is recorded as a new version ("restored version N"). Only the person who published the site can. The project's design in UiChemy is NOT changed, so the next publish (uichemy_deploy_to_cloudflare) puts the current design back online. Get the number from uichemy_site_versions, and confirm with the user first, naming the version and the address. Not for EmDash (CMS) sites.
    Connector
    Destructive
    OAuth