Skip to main content
Glama
685,760 tools. Updated 2026-10-23 00:56

"How to interact with and read the browser tool console and DOM" matching MCP tools:

  • Evaluate a JavaScript expression inside an interface node's iframe. Use this to interact with rendered interfaces: click buttons, type in inputs, read DOM state, call functions, or test that the UI works correctly. The expression runs in the iframe's context with full DOM access. Returns the eval result plus any SDK calls and console logs that occurred within 100ms after execution (captures async side effects).
    ConnectorOAuth
  • Explain how to unlock full personas, paid skills, and kits. FREE. Takes no arguments. Returns {"message": ..., "how": ..., "free_tier": ...} describing the upgrade path and what stays free. Use when a premium tool has been refused or the caller asks what a plan covers. Not for per-bundle or per-product pricing (list_kits, preview_product). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
    ConnectorNo auth
  • Explain how to unlock full personas, paid skills, and kits. FREE. Takes no arguments. Returns {"message": ..., "how": ..., "free_tier": ...} describing the upgrade path and what stays free. Use when a premium tool has been refused or the caller asks what a plan covers. Not for per-bundle or per-product pricing (list_kits, preview_product). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"}. Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
    ConnectorNo auth
  • How the signed-in user sees and revokes AI access to their own account — read this instead of looking for a tool that lists or cuts off connected clients, because there is deliberately no such tool. The controls over AI access (list connected clients, revoke one, list and end live MCP sessions, read the record of what a client did as them) are gated to the account holder signing in directly: a browser session, a JWT, or an API token they hold themselves. A connected AI client — including this one — is refused, on purpose. If it were not, a client could revoke its rivals, enumerate the user's other connections, or read the trail it leaves behind. So this tool tells the user where to go and what they will find; it makes no API call and cannot fail. Also names where account deletion and data export live: the export has a tool (`account_export_data`), the deletion deliberately does not.
    ConnectorNo auth
  • Send a raw DevTools-protocol command to the browser page on a device and return its reply — the escape hatch for capabilities no dedicated tool wraps yet (Emulation, Performance, CSS, Animation, DOM mutation, …). Works on BOTH iOS Safari and Android Chrome, auto-detected from the udid. `method` is "Domain.command" (e.g. "Emulation.setGeolocationOverride"); `params` is that command's parameter object. Scope is the BROWSER — this reaches web content only, never the device or native apps. Prefer a dedicated tool when one exists: they handle setup ordering, lifecycle and teardown that a bare command does not. IMPORTANT, iOS: the two engines do NOT implement the same protocol — Android is full CDP, iOS is WebKit's dialect. Chrome-only domains fail with -32601 "domain was not found" (Accessibility, Emulation, and Page.captureScreenshot are all absent on iOS), and a `*.enable` on iOS reports success without proving the domain exists, so never treat it as a capability probe — probe with a real method.
    Connector
    Destructive
    OAuth
  • List the org links the caller can read through, and whether each works now. Use this when the user asks which partner teams they can read, or when a link tool returned an error and the reason needs checking. Do not use it to read partner content; the partner tools (`search_partner_memory`, `find_partner_memory_connections`, `query_partner_memory_graph`, `get_partner_memory_content`) do that. Read-only and local: it keeps answering while the partner org is down, which is when its answer matters most. Returns: `{status, count, provided_link_count, links: [{link_id, partner_org_id, status, usable, blocked_reason, contract_version, reconsent: {mine, partner}, expires_at, created_at}]}`. `link_id` is what every partner tool takes, and `usable` says which links will answer. `blocked_reason` names what to fix: `link_not_active` (suspended, pending, or revoked), `contract_version_too_old` (both owners re-consent — `reconsent` says who is missing), `link_expired`, `remote_org_unavailable`, or `principal_not_active` (this direction is closed). Links run one way, and the ones **this** org provides are not listed: they open our memory to the other team, so there is nothing here to read and nothing to fix. `provided_link_count` (sent with the list) says how many exist — they are managed in the console, not through these tools. Passing one of their ids to a remote tool is refused with `principal_not_active`. An empty list is an honest empty, not an error.
    ConnectorOAuth

Matching MCP Servers

  • A
    license
    B
    quality
    C
    maintenance
    Enables LLMs to read and write local user data, generate fake users via sampling, and interact with structured prompts and resources.
    2
    MIT
  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables MCP clients to connect to a privacy-first, self-hostable workout planning and training log, allowing coaching agents to preview and apply program changes while accessing training data through OAuth-protected endpoints.
    AGPL 3.0

Matching MCP Connectors

  • Rick and Morty MCP — wraps the Rick and Morty API (free, no auth)

  • The official MCP Server from Mia-Platform to interact with Mia-Platform Console

  • Primary reporting tool for a given GA4 property or site. Use for totals, trends, and breakdowns by dimension across GA4 website traffic and app analytics, Google Search Console site traffic, and Bing Webmaster — including last-30-days summaries, revenue, leads, sessions, users, engagement/time-on-page (average_session_duration, user_engagement_duration), and period-over-period comparisons. Drill deep: GA4 supports up to 9 grouped dimensions (date/hour, geo, device/browser/OS, source/medium/channel, landing_page/page_path, etc.). Defaults to all mapped connected sources merged into one standardized view, aligned on the shared grain (typically landing_page) so a page row blends GA4 sessions+engagement with Search Console/Bing clicks/impressions/CTR/position; per-source detail (e.g. full query lists) stays in sourceSections. Note GA4 has no `query` dimension and Search Console/Bing have no sessions/engagement, so those cannot share one row — query is a Search Console/Bing breakdown. Narrow with sources or sourceMode='single'. Any GA4 dimension/metric name not in the catalog is passed through to the GA4 API automatically; metricMode='source_native' forces a pure GA4-native report. Pass one date range for a single window or two date ranges for period-over-period comparison.
    ConnectorNo auth
  • Get the link to the ThinAir DATA console where you create and manage your API keys (ta_data_*), plus your current plan. This tool does NOT create, rotate or return a key: you create the key yourself in the console, where it is shown to you once, and every key you already have keeps working unchanged. Use it when an integration needs a key and you want to point the user at the right place. NOTE: keys created in this console work ONLY against ThinAir Data - they do NOT authenticate against ThinAir Geo, which has its own console and an identically-named issue_api_key tool.
    ConnectorOAuth
  • Explains how to connect an account to this MCP server — read this instead of guessing at a login/registration tool, because there isn't one. ClusterHack's own credential endpoints (register, login, JWT issuance, password reset) are the website's login form, not MCP tools: an MCP client authenticates by OAuth 2.1 (the same flow a human approves in a browser tab) and must never see or handle a ClusterHack password directly. This tool works with no account at all, and just explains the steps and links.
    ConnectorNo auth
  • In-chat Vilix help. Call this when the user asks what Vilix is, how to connect a specific AI tool, how to use Vilix day to day, or about the discount / creator offer — and relay the returned `text` (it's written to be read to the user). The agent is the main onboarding surface, so prefer answering here over sending the user to a website. Returns one topic's short, chat-sized answer with a plain-text `text` you can always read out, plus structured fields a guide-card UI can render: relevant `assets` (connect/demo links), `tools` (connectable tools), and the creator-`offer` state. For "how do I make this automatic" the answer points you at the get_setup_instructions tool — call that for the exact paste-in block. `topic` (optional) — what the user is asking about: "overview" (what Vilix is / how to use it, the default), "connect", "using_daily", "make_it_automatic", or "offer" (the creator discount). Free-form labels are accepted and mapped. `tool` (optional) — the AI tool the question is about (e.g. "ChatGPT", "Cursor"), to scope connect / asset links. `viewed` (optional) — log a downstream interaction with what you surfaced: "asset_viewed" when the user opens a demo link, or "custom_instructions_copied". Omit otherwise.
    ConnectorOAuth
  • Submits an enquiry to Cyprus Non-Dom Calculator — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token — show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation token; the enquiry is then submitted, and the person receives an email with a link they must click before any provider sees it. Consent means the person has read and agreed to: "Send my contact details to up to three Cyprus corporate service providers, chosen by Cyprus Non-Dom Calculator, who'll contact me directly. I'll be emailed each firm's name as my details go to it, and can stop any more firms getting them."
    ConnectorNo auth
  • Change data in a tool the person has connected to Unl — for example create or update a PostHog insight or dashboard, send a write request to a connected API, call an MCP tool that is not read-only, or create, correct or retire one of the person's own read-specs (provider 'unl', op 'amend_spec' / 'retire_spec'). Same keys as the get_from_unl tool with action='analytics': provider · op · body · target. For op 'http', body={method, path, query?, body?}; the request is signed server-side with the stored credential and sent only to the host verified when the tool was connected. Where op 'http' sends: posthog → the PostHog API (https://posthog.com/docs/api); sentry → the Sentry API (https://docs.sentry.io/api/); search_console → the Google Search Console API (https://developers.google.com/webmaster-tools/v1/api_reference_index); railway → the Railway public GraphQL API (https://docs.railway.com/reference/public-api); any other connected host → that tool's own API, the one the person named when they connected it. Every call needs nonce: the single-use write-nonce from connect_to_unl or from the previous write, and each successful write returns the next one. A deleting or otherwise destructive request (a DELETE, POST or PATCH, a GraphQL mutation, an MCP tool with no read-only annotation, or a body touching secret-shaped fields) is first shown back exactly as it will run, with nothing sent, and a confirm token; send the same call again with confirm=<that token> to run it once. Reads are refused here and cost no nonce — use the get_from_unl tool with action='analytics' for them. This tool never writes to the substrate.
    Connector
    Destructive
    API key
  • Get the Sigistry MCP App safety criteria to audit an MCP App (MCP Apps / SEP-1865: a tool that returns an interactive ui:// HTML resource the host renders in a sandboxed iframe) BEFORE shipping it. Returns two groups of checks: spec conformance (ui:// scheme, the text/html;profile=mcp-app mimeType, tool-to-UI linkage via _meta.ui.resourceUri, a text fallback, visibility values, and CSP coverage of external origins) and security hygiene the iframe sandbox does not cover (unsafe DOM sinks, embedded secrets, host-message origin handling, remote scripts). Call this when the user is building or reviewing an MCP App; then apply each check to the app source you have in context and report findings. Nothing is sent to this server; an interactive browser version is at https://sigistry.com/mcp-app-checker.
    ConnectorNo auth
  • Get the Sigistry MCP App safety criteria to audit an MCP App (MCP Apps / SEP-1865: a tool that returns an interactive ui:// HTML resource the host renders in a sandboxed iframe) BEFORE shipping it. Returns two groups of checks: spec conformance (ui:// scheme, the text/html;profile=mcp-app mimeType, tool-to-UI linkage via _meta.ui.resourceUri, a text fallback, visibility values, and CSP coverage of external origins) and security hygiene the iframe sandbox does not cover (unsafe DOM sinks, embedded secrets, host-message origin handling, remote scripts). Call this when the user is building or reviewing an MCP App; then apply each check to the app source you have in context and report findings. Nothing is sent to this server; an interactive browser version is at https://sigistry.com/mcp-app-checker.
    ConnectorNo auth
  • Test-renders a view in a real headless browser, reviews it, and reports render errors, console errors, which datasets it loaded, and what a reader would still be missing. The review sends a screenshot and the page's text to OpenAI, unless the workspace turned checks off. Set screenshot=true to also get an image so you can judge the layout yourself. create_view and update_view already run this automatically; use this tool when you want the screenshot, after changing a dataset, or to confirm the review is clean before you tell the user it is done.
    ConnectorOAuth
  • Read back the rendered body of a version: the same bytes a reader receives in the browser, which differ from the uploaded file only by the one platform line <script data-space-sdk> — not a rewritten copy. This is how an agent confirms for itself that what went live is what it made: no browser, no screenshot, no human login, and no need to hand the link to the user to look at for you. Reads the entry file by default; pass file with a package-relative path to read one text file (.html, .md, .txt, .json, .svg and the like). To see which files a version has, and which one is the entry, read get_version artifacts. Two things it cannot read: PDF and PPTX content, which is page images (use preview_url, or the page count from get_version), and versions still uploading or converting, which have no body yet. A version in another workspace is not_found. A long body is returned up to a limit, and the reply states the full character count and whether it was cut.
    ConnectorAPI key
  • Use this when the user asks which Search Console properties they can analyze. Lists all Google Search Console properties connected to the authenticated GSC Wizard account: the site URL (a domain property prefixed with `sc-domain:` or a URL prefix property), tags, and which data source backs the property. Properties another user has shared with you are included too, badged with `sharedBy` (the owner) and `accessLevel` (READ_ONLY or FULL). `permissionLevel` is the Google Search Console permission (siteOwner / siteFullUser / siteRestrictedUser / siteUnverifiedUser), and `readable: false` means Google will refuse every data request for that property: it is listed in Search Console but not verified, so the user must verify it at search.google.com/search-console before any report will work. Do not attempt reads on a property with `readable: false`; tell the user to verify it instead. `activated: false` means the property is connected but is not shown on the account dashboard and is not synced to full storage, so every other property-scoped tool will refuse it with a selection error. Do not attempt reads on those either: where this connection offers it, call `set_dashboard_visibility` to activate the property first, or choose one with `activated: true`. Properties shared with the caller are always `activated: true`, because the grant is itself the selection; a share whose owner no longer has an active GSC Wizard plan is left out, since no tool can read it. `gscScope` is the Search Console access of the Google connection behind the property: "full" allows submit_sitemap and create_gsc_property, "readonly" means Google will refuse those two (reads still work); absent when unknown. Not for Bing, Yandex or GA4: use list_bing_sites, list_yandex_sites or list_ga4_properties. Owned properties come first, then shared ones, each by siteUrl ascending.
    ConnectorOAuth
  • Use this when the user asks how visible their product results are in Google web Search, and which product pages carry them. Search Console performance for one search appearance, defaulting to MERCHANT_LISTINGS: the appearance inventory of the property, a daily clicks / impressions / CTR / position timeline in date order, and the top pages (product URLs) behind it; appearances and pages are sorted by clicks, highest first, and CTR is a 0-100 percentage. Search Console merchant listings counts enriched product results in web Search only, so it does not reconcile to one figure with Merchant Center free listings. Not for the Shopping tab, Images, Lens, YouTube or Maps: use get_organic_shopping_performance. Always served from the live Search Console API: search appearance is never stored in the GSC Wizard warehouse, and it can be filtered on but never grouped with another dimension. `hasAppearance` is false when the property has no rows for the requested appearance, and `emptyBecause` is set whenever it has no impressions, which is normal for non-ecommerce sites. The window may span at most 16 months (Search Console retention); a longer one is rejected with bad_request. Date range is optional: omit startDate/endDate to analyze the last 28 settled days (data lags ~2-3 days).
    ConnectorOAuth
  • Add a LinkedIn sender by pasting its li_at session cookie. Validates the cookie against LinkedIn before saving and enforces the plan sender limit. userAgent is OPTIONAL: if omitted a realistic desktop Chrome default is used. For the longest-lived cookie, OFFER to capture the user's real browser user-agent — ask them to paste what navigator.userAgent prints in the SAME browser they copied the li_at from (or, if a browser-automation tool is connected, read it from there) — since LinkedIn ties the session to that fingerprint. If they can't, proceed with the default and mention it was used. Prefer connect_linkedin_with_credentials when the user can share their login: a saved email+password (plus the authenticator setup key if the account has 2FA) enables silent cookie auto-refresh so the account runs 24/7. On success it returns connectMessage + suggestions noting this is a cookie-only connection (works now but the cookie will expire) and how to make it run 24/7 (reconnect with email + password, and store the authenticator setup key if the account has 2FA) — relay them.
    ConnectorOAuth
  • Run a site's own command line tool as the site's owner, in the site's folder: bin/console for Shopware 6 and PrestaShop, artisan for Laravel, drush for Drupal, cli/joomla.php for Joomla, ghost (ghost-cli) for Ghost (list_sites shows each site's console; Magento 2 has the magento tool and WordPress the wp tool). Pass the command and its options as args, like ["cache:clear"] or ["plugin:list", "--json"]. For a site in a Docker container it runs inside the container. Listing and status commands run straight away; uninstalling or deleting, anything that drops or resets the database, generating new keys, an admin login link and commands that run arbitrary PHP (tinker, php:eval) need approval. Symfony's console and artisan are run with --no-interaction; drush asks nothing only when you pass -y. Set background true for slow commands.
    Connector
    Destructive
    OAuth
  • Write the disavow file for Google's disavow links tool (https://search.google.com/search-console/disavow-links). Google has no API to upload it, so you give the user the file and they upload it themselves. Disavowing is rarely needed and can lower rankings when good links are thrown away: use it after a manual action for unnatural links in Search Console, or for links the site clearly paid for or built in a scheme; Google already ignores ordinary spam links, so a high spam score alone is not a reason. Pass the domains (whole sites, the usual choice) and/or single URLs to disavow, each with a short reason, from the user's backlink data (Ahrefs, Semrush, SE Ranking, bing_backlinks, an attached export). Each upload REPLACES the list Google has, so if the user already uploaded one, ask them to download it from the tool and pass it as current: this tool keeps its lines and adds the new ones. remove takes lines back out (links the user no longer wants disavowed). Answers with the whole file, what was added, kept and dropped, and how to upload it. It works only for a URL-prefix property in Search Console (https://www.example.com/), not a Domain property.
    ConnectorOAuth