Skip to main content
Glama
796,631 tools. Updated 2026-11-17 15:40

"A server for information about Jenkins (automation server)" matching MCP tools:

  • Change an existing automation by id. action=disable stops it firing (use this to turn off a misbehaving rule); action=enable resumes it; action=delete removes it. To read one, use relm_get_automation. To change a rule's trigger/conditions/actions, delete and recreate.
    Connector
    Destructive
    No auth
  • Manual fallback: returns a node type+operation's config SCHEMA (the fields you can set) — NOT a live node's saved config (use get_node for that). Takes "type:operation" pairs (e.g. ["automation-slack:send_message_to_channel"]). Prefer search_operations(detail_level='full') for intent lookup, or update_workflow(include_configs=true) while building.
    ConnectorOAuth
  • Search 1,000+ vetted AI use cases by keyword, industry, or business workflow (e.g. 'invoice', 'dental', 'customer support'). Use when someone asks how AI can help their business, wants AI ideas for an industry, or looks for automation opportunities. Also use it to find the slug before get_agent_playbook or run_agent. Returns titles, summaries, and links. Public: no sign-in.
    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
  • Shows the history of past recipe runs and their results (recorded by recipe_run), so you can reuse, compare, or debug an automation. Pass `name` for one recipe's runs, or omit for a compact history across all recipes. Pass `run_id` (with `name`) to get that run in full detail. Newest first.
    ConnectorOAuth

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
    B
    quality
    C
    maintenance
    A server that enables interaction with Jenkins CI/CD pipelines from any compatible MCP client (like Claude Desktop), allowing users to manage jobs, builds, coverage reports, and other Jenkins functionality through natural language.
    11
    260 npm
    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

  • Create a scheduled agent — a recurring or one-time automation that runs on a timer in a real Chrome browser. Two modes. WORKFLOW MODE: pass workflowId plus a schedule — the platform copies everything else (prompt, starting URL, output contract, model, proxy, policy, files) from the workflow and bakes your variables into the prompt; results and memory stay centralised on the workflow. STANDALONE MODE: omit workflowId and provide name, prompt (a Goal / Ground rules / Stages / Output browsing runbook — see the prompt field description), and a schedule; the connection's environment is used automatically. Ask the user only what it should do and when it should run, in plain language — pick sensible defaults for everything else and state them; never ask about environments or technical settings. Results are delivered to your connected chat and appear in session history.
    ConnectorNo auth
  • Retrieve the complete markdown of one documentation article by the id returned from `search` (for example `en/claude-code/advanced-techniques/hooks-automation`). The text is returned in full; `metadata.gated` only reports whether the article sits behind the paywall on the web. An unknown id is an error — call `search` first.
    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 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
  • Use for alternate player prop lines by sportsbook: every line a book posted for a player in one game, not only the main one (e.g. 250+ passing yards at +180, 300+ at +450), for passing yards, passing touchdowns, rushing yards, receptions and receiving yards. Pass game_id and market, and player_id (a GSIS id from search_players) for one player. Returns each book's last ladder before kickoff: per line the over price and, where the book posts it, the under. Alternate player props are held for NFL games from the 2023 season on, captured once in the last 75 minutes before kickoff, from 4 to 6 books since 2024. 2023 is partial: 1 or 2 books, passing yards, passing touchdowns and receiving yards for about 217 games, rushing yards and receptions for about 87. A game further out has none yet. For the main line and the opening and closing prices use get_player_props; for how a player did against his main line use get_prop_history. 10 credits. Prices are market information; no tool places, accepts or tracks wagers.
    ConnectorNo auth
  • Returns the append-only change history (most recent first) of a ground: node/edge/api/bug create, update (with a field-level diff {from,to}), delete, and plan_commit. Each event carries the actor ("user:<id>" for humans, "token:<id>" for agents/automation), a summary label, and for updates a diff. Use it to answer "what changed, when, and by whom" — e.g. a bug's status transitions or a node's edits over time. Filter with entityType/entityId to get a single entity's timeline. Note: git commits recorded via record_commit live in a node's metadata.commits, not here.
    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
  • Returns the applications to the Tbilisi Architecture Service for a parcel or a period, newest first: building permits, project approvals, signs, fences, and requests for public information. Give a cadastral code (01.18.04.020.005), a period of at most 31 days, or both. A period of more than 500 applications fails, and Tbilisi registers about 70 each working day, so ask for a week at most. Each application has its number, address, status, category, class, and stages. Read the decision with permits_get_application. Tbilisi only. Texts are in Georgian. Data from TAS.
    ConnectorNo auth
  • 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
  • Create an automation workflow from a trigger, saved as a paused draft. The API's create endpoint only accepts a name and trigger — it has no fields for workflow steps or starting active; configure the step sequence in the MisarMail dashboard's visual builder, and use toggle_automation to activate once reviewed.
    ConnectorNo auth
  • Create a follow-up reminder for a person to get back to a contact. For work the team owes (checking a database, fixing a bug, a refund), use create_task instead. Creates persistent state and is NOT idempotent: calling it twice creates two reminders. Nothing is sent when it comes due — it is a to-do, not an automation; use send_message or a broadcast to actually message someone. It stays open until someone completes it: a reply from the contact does not close a reminder created here (only the automatic "no reply for N days" follow-ups close on a reply). Created with a personal API key it is assigned to that user; with a workspace key it lands unassigned. While leads are on for the workspace, a reminder about a person creates no follow-up: their lead is parked until dueAt instead (made a lead first if needed) and reasonText goes into the lead history; the result says so and has task null.
    ConnectorNo auth