Skip to main content
Glama
822,164 tools. Updated 2026-11-22 20:48

"Information about Ansible automation tool" matching MCP tools:

  • 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
  • Maps only stable Tier1 finding identifiers to approved Tier1 services and public resources. Call after a Tier1 score or email-domain check. Do not submit prose, URLs, customer information, or invented identifiers. This tool performs no arbitrary fetching, makes no contact request, changes nothing, and stores nothing.
    ConnectorNo auth
  • List open times on Upforge's calendar for a free consultation (usually 30 minutes), in the person's own timezone. Call this before book_consultation and let the person pick a time; never pick one for them. Meeting types come live from the scheduler: general-inquiry is the default, and service types such as web-design, application-development or ai-automation route to the right person. Bookings need about a day's notice, so the search starts tomorrow.
    ConnectorNo auth
  • Create a new automation DEFINITION for the authenticated user. The new automation is always created INACTIVE (a definition only) — it does NOT run, send, or activate. Use when the user wants to define a new automation by name. Do NOT use to activate, run, or wire the automation's step graph — activation is a separate, later capability and is not available here. Do NOT use to edit an existing automation — use mcp_crm_automations_update. The automation's status cannot be set via this tool. Tenant is bound to the session and cannot be changed via arguments. Automation-level RULES (all optional, and all independent of the step graph — use mcp_crm_automations_set_steps for that): entryConditions / exitConditions / restartConditions are arrays of {type, segmentId, operator, contactFilters, campaignIds, linkUrl} where type is one of added_to_lists, removed_from_lists, contact_in_segment, contact_matches_filters, email_opened, email_clicked, email_unsubscribed; a membership type needs segmentId, contact_matches_filters needs contactFilters, and the email types take optional campaignIds (plus linkUrl on email_clicked). operator is MATCHES or DOES_NOT_MATCH. Pass an EMPTY array to clear a slot; omit the key to leave it unchanged. reentryPolicy is once (a contact runs this automation at most once) or every_time, with reentryWaitMinutes as the cool-down before a contact may re-enter. onDeactivate is continue (in-flight contacts finish) or cancel (in-flight contacts are cancelled when a human deactivates the automation). Returns the created automation projection (id, name, status, rules, version).
    ConnectorOAuth
  • List the public MCP servers whose tools apiwatch checks every 6 hours (tools/list only, no login, no tool calls), with each one's status (answering, needs a login, not reachable), tool count, last check and last observed change. Use it to see which servers mcp_server_changes can answer about. Returns no tool descriptions.
    ConnectorNo auth

Matching MCP Servers

  • A
    license
    A
    quality
    D
    maintenance
    An MCP server that provides information about Utkarsh, including bio, skills, work experience, and portfolio projects, accessible via local stdio or remote HTTP with OAuth.
    6
    MIT
  • A
    license
    A
    quality
    B
    maintenance
    Read-only server that reports what is actually true in a local Ansible checkout: the option specs of installed modules, task-argument validity checks, role interfaces, redacted inventory, play structure, effective config, requirements drift, and which tasks a collection upgrade would break. It lets coding agents verify specs and arguments against the installed collections before writing anything, without running plays, connecting to managed hosts, or supplying vault secrets.
    11
    542 npm
    1
    MIT

Matching MCP Connectors

  • About Bureau, the self-hosted office for AI agents: overview, FAQ search, roadmap, install.

  • Programmatic headless browser sessions: create, interact, browse, and extract - rendered in a real

  • List a Dutify reference-data enum (status types, custom-field types, view types, automation action/condition types, access levels, etc.). Returns the authoritative set of values the backend accepts — call this BEFORE guessing enum strings on a create/update payload to avoid 400s. Categories: - custom-field-types: Custom-field type catalogue: text, number, dropdown, date, money, file, rollup, formula, … Use the `identifier` from each row as the `fieldType` value when creating a custom field via /v1/lists/{id}/custom-fields or pm_create_custom_field. - custom-field-icon-options: Custom-field icon catalogue: supported iconNames, emojiNames, and defaultIconsByFieldType. Use one of these keys as the `emoji` value; keep custom-field names plain. Agent preference: choose a semantically matching emojiNames key when available (severity/urgency=fire, target/goal=direct_hit, launch=rocket, approval/success=white_check_mark, location=pushpin, budget=moneybag); use iconNames for structural/type affordances like CalendarBlank. - resource-view-types: Resource view types: list (1), board (2), table (3), dashboard (4), gantt (5), calendar (6), gallery (7), whiteboard (9). The numeric `typeId` is what /v1/views and view-config endpoints accept. - status-types: Status type enum — ACTIVE, DONE, CLOSED. Used when grouping tasks or filtering for visibility. - activity-types: Activity log event types — status_changed, task_created, comment_added, automation_executed, etc. - automation-action-types: Automation action types — SET_STATUS, SET_PRIORITY, SET_ASSIGNEES, ADD_COMMENT, etc. Use when building an automation rule. - automation-condition-types: Automation condition types (predicate categories) — STATUS, PRIORITY, DUE_DATE, CUSTOM_FIELD, etc. - automation-field-operators: Operators valid in automation condition predicates — equals, not_equals, greater_than, in, is_set, etc. - access-levels: Entity access levels — VIEW, COMMENT, EDIT, FULL — used in user/team access grants. - workspace-access-level-permissions: Workspace role → permission map (OWNER/ADMIN/MEMBER/GUEST). Tells you which capabilities each role grants. Auth: the resources are @PermitAll for anonymous callers, but the ApiKeyScopeFilter still gates API-key requests. The `metadata:read` scope covers custom-field-types / custom-field-icon-options / resource-view-types / status-types / activity-types / access-levels / workspace-access-level-permissions. The three automation-* categories live under /v1/automation/* and require `automations:read` instead. If the API key lacks the required scope the call returns 403 — pick a category your key covers, or have the user mint a key with both `metadata:read` and `automations:read`.
    ConnectorNo auth
  • List a Dutify reference-data enum (status types, custom-field types, view types, automation action/condition types, access levels, etc.). Returns the authoritative set of values the backend accepts — call this BEFORE guessing enum strings on a create/update payload to avoid 400s. Categories: - custom-field-types: Custom-field type catalogue: text, number, dropdown, date, money, file, rollup, formula, … Use the `identifier` from each row as the `fieldType` value when creating a custom field via /v1/lists/{id}/custom-fields or pm_create_custom_field. - custom-field-icon-options: Custom-field icon catalogue: supported iconNames, emojiNames, and defaultIconsByFieldType. Use one of these keys as the `emoji` value; keep custom-field names plain. Agent preference: choose a semantically matching emojiNames key when available (severity/urgency=fire, target/goal=direct_hit, launch=rocket, approval/success=white_check_mark, location=pushpin, budget=moneybag); use iconNames for structural/type affordances like CalendarBlank. - resource-view-types: Resource view types: list (1), board (2), table (3), dashboard (4), gantt (5), calendar (6), gallery (7), whiteboard (9). The numeric `typeId` is what /v1/views and view-config endpoints accept. - status-types: Status type enum — ACTIVE, DONE, CLOSED. Used when grouping tasks or filtering for visibility. - activity-types: Activity log event types — status_changed, task_created, comment_added, automation_executed, etc. - automation-action-types: Automation action types — SET_STATUS, SET_PRIORITY, SET_ASSIGNEES, ADD_COMMENT, etc. Use when building an automation rule. - automation-condition-types: Automation condition types (predicate categories) — STATUS, PRIORITY, DUE_DATE, CUSTOM_FIELD, etc. - automation-field-operators: Operators valid in automation condition predicates — equals, not_equals, greater_than, in, is_set, etc. - access-levels: Entity access levels — VIEW, COMMENT, EDIT, FULL — used in user/team access grants. - workspace-access-level-permissions: Workspace role → permission map (OWNER/ADMIN/MEMBER/GUEST). Tells you which capabilities each role grants. Auth: the resources are @PermitAll for anonymous callers, but the ApiKeyScopeFilter still gates API-key requests. The `metadata:read` scope covers custom-field-types / custom-field-icon-options / resource-view-types / status-types / activity-types / access-levels / workspace-access-level-permissions. The three automation-* categories live under /v1/automation/* and require `automations:read` instead. If the API key lacks the required scope the call returns 403 — pick a category your key covers, or have the user mint a key with both `metadata:read` and `automations:read`.
    ConnectorNo auth
  • Change or pause one of the user's Clarifo automations, only when the user asks. Give only what changes; everything else stays. pause=true switches it off (it can be switched on again with activate_automation after the user approves its settings; this tool never switches one on). Confirm the change with the user first, then say what changed (before and the new settings) and give review_url. Args: automation_id: From automations. idempotency_key: Optional; leave it out. Clarifo recognises a repeated identical request by its content. Give one only to retry this same request. pause: True to switch the automation off. name: New name. instructions: For an instructions (prompt) automation: the new instructions it answers across the watchlist. cadence: For a prompt automation: daily, weekly, monthly, quarterly. language: For a prompt automation: en, fi, sv. scope_value: The watchlist (portfolio id) a prompt automation reads, or the market / sector of a report automation. scope_kind: For a report automation: all, market, watchlist, sector, industry. folder: Folder its documents go to. max_new_per_run: For a report automation: documents per run. run_times: For a report automation: run times, e.g. ["07:00"]. run_days: For a report automation: weekdays 1-7 (Monday = 1). timezone_name: IANA zone for the run times, e.g. "Europe/Helsinki". workspace_id: Optional; the automation's workspace. template: The name (or id) of one of the user's report templates of the automation's kind, or "standard" for Clarifo's standard format. keep_dashboard: true keeps a dashboard updated on every run: a watchlist (portfolio) automation keeps a portfolio dashboard per portfolio, emailed when the user's notification settings send Automate email; a report automation keeps an earnings-review dashboard per company. Returns: {"status": "automation_updated" | "automation_paused", "changed", "before", "automation_id", "name", "enabled", "what", "schedule", "cadence", "review_url"} or {"error", "failure_kind"}.
    Connector
    Destructive
    API key
  • List the tenants (companies) you may query, with their id, name and slug. The only tool that needs no tenant_id — start here when you do not know which tenant to ask about.
    ConnectorOAuth
  • A Site is the address list (link list) of ONE automation: the automation runs once over every address on it. This endpoint creates or updates a Site by id (empty body.id = create; set id = update). Subject to the SITE_MAP plan feature. IMPORTANT: leaving out `id` creates a NEW Site on every call, but a scraper's run (and scrapewise_get_scraper_site) reads only one Site per scraper — a list saved into a second Site may never be scraped. Before saving, read the scraper's Site (scrapewise_get_scraper_site) and send its `id`; omit `id` only when the scraper has no Site yet, and make that first save on its own, not in parallel with another save for the same scraper. For an API (cURL) scraper, send every link together with its `curl` in the same save, unless the Site has `calculateCurlsAutomatically` on. There are two ways to give an automation its addresses: 1. PASTED / UPLOADED list — send `links` (one {url, title} per address). The list REPLACES the stored one. To add addresses, send the full new list. 2. FED list — set `linksSourceScraperId` (another automation of this account), `urlFieldName` / `titleFieldName` (which of its result columns hold the address and the title) and `updateLinksBySourceScraperAutomatically: true`; the list is then refreshed from that automation's rows after every run of it. You do NOT fetch those rows yourself and you never call a `/urls` endpoint — the server copies them. Storing a list turns the automation's list mode on by itself: no follow-up scrapewise_create_scraper call is needed. To create an automation, attach a list and run it in ONE call, use scrapewise_run_scraper_url_list instead. Do NOT create one scraper per address — one automation holds the whole list. Args: - body (SiteDTO, required): the owning scraper (`scraperId`) and either `links` (pasted list) or `linksSourceScraperId` + `urlFieldName` (fed list). Returns: The persisted SiteDTO including assigned id, and `linksDropped` (fed lists only: how many offered addresses this automation cannot read and did not store). Examples: - Use when: "give automation {id} these 50 URLs" → scraperId + links - Use when: "feed automation B from automation A's results" → scraperId (B) + linksSourceScraperId (A) + urlFieldName - Don't use when: you want to create an automation for a list and run it → use scrapewise_run_scraper_url_list (one call) - Don't use when: you want to add links to an existing site → there is no add-links endpoint; re-PUT the full SiteDTO with the whole new list Error Handling: - 402 if customer plan lacks SITE_MAP feature. - 400 if body validation fails. - 400 if a PASTED link (no `linksSourceScraperId`) does not belong to this scraper. A scraper that reads one kind of page runs its whole URL list through that same reader, so every link must be a web address of that kind and must carry everything that kind of read needs (for example the dates a stay lookup needs, the postcode a store lookup needs, the type a trend lookup needs). The message names the offending link and what is wrong with it; nothing is guessed and nothing is silently dropped. - A FED list (`linksSourceScraperId` set) is not refused whole: the links this scraper can read are stored and the rest are DROPPED and COUNTED, on `X-Links-Dropped` and on `linksDropped` in the body. A source column legitimately carries addresses of other kinds, and one of them must not cost the dependent scraper its whole list. 400 only when NOTHING offered is readable — and then the previously stored list is kept untouched. - 401 Unauthorized. [runtime hint] This tool returns JSON-as-text — its response shape is dynamic (per-scraper itemsConfig, file binary, etc.) so the MCP `outputSchema` is omitted. Do not rely on the presence of any specific field in the response; treat the result as a string-or-object blob and parse defensively.
    ConnectorAPI key
  • Use this when the founder asks which automations a project has, what triggers them and whether they are live, or where a particular contact is in one. It returns every automation with its trigger, live status and delivery counters (enrolled, completed, sent, delivered, bounced). Pass a `contact` handle and each automation also reports that contact's own enrollment: state, a human label for the step they are on right now, and when a waiting step resumes. Not for one-off emails to the list (see `list_broadcasts`). Read-only. There is no tool to enroll a contact in an automation: every enrollment traces back to a real event (a signup, a verification, a referral, a stage change, a survey answer), never a direct write.
    ConnectorAPI key
  • Runs a single end-to-end execution of an existing automation, returning success/failure plus the target and duration. Mirrors a real production firing. Behavior: - Sends REAL messages: posts the configured webhook, sends the configured email, posts the Slack message, or writes the HubSpot record. Use override_email (email channels) to redirect delivery to a safe test target. - Insight automations use REAL research conversations, create a normal analysis session and insights, and consume normal analysis-session credits. They do not advance the configured trigger's schedule. - Each call fires another real delivery. - Errors when the perspective or automation is not found, or you do not have access. Webhook automations whose endpoint URL hasn't been set yet (at configure_url) error with a pointer to that page. - Mock conversation defaults: trust score 85, status complete, "Test Participant" / test@example.com. Override participant_name, participant_email, summary, and tags via test_data. HubSpot note and record-update automations find the contact by participant_email, so set it to an existing contact's email. - Returns success: false when the automation skips delivery (e.g., tag/trust filter doesn't match the mock, or no HubSpot record matches the participant email); the message gives the skip reason. The error field is populated only on real delivery failures. When to use this tool: - Verifying a freshly-created automation actually delivers before relying on it (override_email directs email tests to a safe target instead of real recipients). - Reproducing a delivery failure surfaced in automation_list (last_error). When NOT to use this tool: - Listing what's configured — use automation_list. - Changing config — use automation_update. - Removing the automation — use automation_delete.
    Connector
    Destructive
    OAuth
  • Use this after each user message that contains anything worth knowing later, even if the user does not say 'remember this'. Default to saving: a missed memory costs far more than a redundant one, so when in doubt, save. Each of these is a trigger on its own: the user makes a decision, states a preference, gives a fact about a person, project, company, or tool, sets a plan or commitment, makes a correction, or reports progress or an outcome. Save one concise, self-contained memory per call, written so it makes sense on its own later, with the exact wording, numbers, dates, names, and identifiers the user gave; several facts in one message mean several calls. Record what the user actually said, not your inference. There is no update tool: to supersede outdated information, save the corrected fact and say what it replaces. Never save passwords, API keys, tokens or other credentials, payment card numbers, government ID numbers, or protected health information, and never save whole transcripts. Writes one memory to the user's OAuth-selected vault. If the user asks what was saved, answer truthfully from the tool result.
    ConnectorNo auth
  • A platform fee of 5% is charged ONLY if the bounty is awarded, and comes out of the filler payout — you owe the full stated reward. Post a bounty: describe a task, state a USD reward, optionally set a deadline and acceptance criteria. Categories: research (find/verify information, e.g. a literature answer or candidate protein target), data (assemble/clean a dataset), sourcing (find a supplier/tool/citation), price_discovery (find the cheapest verified option), other. You review submissions yourself with review_submission; the first one you accept wins. Prohibited: tasks seeking personal information about individuals, credentials or access, anything illegal. Bounties of $1.00+ need you to be reachable (a verified webhook, or an inbox check in the last 3 days). Every bounty expires: 30 days if you set no deadline, 90 at most, with a warning 3 days before and one extension (extend_bounty). If a submission goes 7 days unreviewed and you named no review_delegate, the bounty is flagged poster_unresponsive. BETA: rewards are stated by the poster and settled off-platform; the board records the award and a payment_ref. On-platform escrow lands with x402/Monetization Gateway support.
    ConnectorNo 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. To see what a shopper at a specific location sees (price, availability, delivery date), pass the inline address fields (zip_code, or city/district/country_code where the domain needs them); no setup is needed. A new location is saved to the account and counts once against the plan's address limit; repeat requests for the same location reuse it. Requests with inline address fields can take up to 45 seconds. Check applied_address in the response: if it does not contain the values you sent, the address was not applied.
    ConnectorNo auth
  • Change an existing automation: its actions, conditions, trigger config or name, or switch it off with isActive false. Fields left out stay as they are; actions and conditions, when given, replace the whole list. Use it to fix an automation instead of creating a second one next to it. Get the id from list_automations. For send_email actions, config.kind is transactional (default) or marketing (Pro plan or higher, verified sender domain, unsubscribe footer) and config.attachments is an array of file column ids on the row; see create_automation.
    ConnectorNo auth
  • Automatically send an approved template to every NEW contact with a tag, e.g. a welcome message whenever a lead tagged "new-lead" is added (by add_or_update_contact, import_contacts, the REST API, or a Zapier/Make integration calling it). Only contacts created AFTER the automation qualify, each at most once: re-importing or tagging existing contacts never triggers it. To message existing contacts, use a broadcast; the response's existing_tagged_contacts says how many already have the tag. Only add contacts who agreed to receive WhatsApp messages. The template must be APPROVED with every {{n}} placeholder mapped (set_template_variables). One automation per tag. delay_minutes (0 to 10080) waits before sending. Returns the automation with live stats and any warnings (e.g. no WhatsApp number connected) that would make sends fail.
    ConnectorOAuth
  • Use to inspect the public IPv4 or IPv6 address observed for the connection making this MCP tool call. Takes an empty object and returns ip and family. This is the MCP client connection: a hosted AI client may observe its own exit address, not the user device address. If the user needs their browser or computer connection, direct them to the web tool or a CLI running on that machine. A VPN or proxy changes the observed path. One call observes one address family; it does not discover private local addresses, an address before a proxy, or both address families. The application does not store or log results, and no firewall rules are changed. Cloudflare Worker subrequests can have platform-specific address semantics; the result is not an identity proof. Operational events record the tool name, success or error, a controlled error code, and a traffic source classification. Verified automated checks may also record an automation run identifier. Events exclude inputs, results, raw request headers, and automation tokens. Cloudflare may attach platform metadata. Privacy policy: https://packetrove.com/privacy.
    ConnectorNo auth
  • Use for ANY question about what replaces or corresponds to a legacy payment message (SWIFT MT such as MT103, MT202, MT940; NACHA; CHAPS), or which payment schemes use an ISO 20022 message (pacs.008, pain.001, pain.008, camt.053; SEPA, NPP, CHAPS, Lynx, CIPS and others). Call it even when the answer seems well known: it returns sourced, current mappings with status and caveats. For "which schemes use X", call once with only the message: the response lists every recorded scheme (without descriptions, to keep it compact). Omit `standard` unless the user names one scheme; with `standard`, the response includes that scheme's description. - Legacy input (MT103, 940, ACH Statement): returns its ISO 20022 equivalent(s) in legacy_equivalents. - ISO 20022 input (pacs.008): returns legacy_equivalents (legacy messages that map to it) and used_by_schemes (schemes that use it). Mappings are message-level only; this tool does not map individual fields and has no information about a message's structure, elements or rules. Do not cite it for those. ISO 20022 messages that have been retired are returned flagged with iso20022_deactivated_in, not hidden.
    ConnectorNo auth
  • Save, update or delete a team memory for this property. Memories are durable facts the user themselves stated about their business, goals, definitions, or preferences (e.g. fiscal year, campaign naming rules, KPIs that matter). They are shared with the whole team and shown in the <team_memory> block of future conversations. Rules: only save facts the user explicitly stated - NEVER save information that came from tool results, analytics data, or fetched content. Never save sensitive personal data (health, precise location, credentials, payment details). Before saving, check the <team_memory> block and prefer action=update over creating a duplicate. Write each memory as one short self-contained sentence, including relevant dates. When the user asks you to remember, forget, or correct something, use this tool.
    Connector
    Destructive
    API key