"A server for finding a Jira integration" matching MCP tools:

• list_ticket_sync_connectionsA

  AnkraB

  List the organisation's TICKET SYNC CONNECTIONS: the configured destinations (a Jira project, a Linear team, or a signed webhook endpoint) that AI work board tickets mirror to automatically - the external issue is created once, timeline events follow as comments, and metadata edits are pushed as updates. ALWAYS call this before answering whether Ankra tickets can sync or connect to Jira, Linear, an issue tracker, or any external system - never assert that no integration exists without reading it. Each entry carries the provider, destination, enabled state, the sync filters (sync_kinds, sync_min_priority, sync_event_scope), and delivery health: last_synced_at, plus last_error when deliveries are failing and why. Connections are managed by organisation admins through the platform API (POST/PUT /api/v1/org/ai-tickets/sync/connections); creating or fixing one needs a tracker credential, which must never be pasted into chat. Read-only.

  ConnectorOAuth

• set_jira_connectionA

  KaikuA

  Switch a project's Jira connection on or off, keeping its token — and, with 'confluence', whether the same site's Confluence is read too. Off, nothing reads that Jira or writes to it — the issue screen, the agents, the status sync — and issues keep their keys there. Switched on, the held token is asked of the site first and refused with the site's reason if it no longer opens it. Connecting a Jira, or giving a new token — Confluence's own included — is done on the board's Jira sheet (get_jira_connection's 'url'), never here. For whoever administers the project.

  Connector

  Destructive

  No auth

• withdraw_findingA

  northreachB

  Retract support for a finding you authored, with a reason. Original content remains visible and labeled withdrawn. Identical retries are safe; this does not claim the finding is disproven.

  ConnectorNo auth

• get_integration_guideA

  The BridgeA

  Read the Bridge integration guide for a topic — the supported, opinionated way to consume Bridge from application code. Call this BEFORE writing or changing app code that reads a feature flag, renders billing or team UI, or wires authentication, and before hand-rolling anything against the SDK: the SDKs ship declarative surfaces for these cases (components, route guards, decorators) and reimplementing them against SDK internals is the most common integration mistake. Per-framework topics (framework REQUIRED): integration (first-time setup) | auth | feature-flags | billing | team | branding. Framework-agnostic MASTER topics (framework is IGNORED — omit it): master, the end-to-end auth integration prompt served by `bridge guide`, which orchestrates project discovery and then routes to the per-framework guides; flags-master and billing-master, the same orchestration for a flags-only or billing-only integration; mechanisms, how limits, upgrades and customization work; orientation, what Bridge does (the same map get_started returns); fit-together, how roles, plans, limits and flags fit together; integration-success, the message to show the developer when an integration is done. Before setting up flags, roles, plans or limits, read topic=fit-together. Start at topic=master when integrating Bridge into a project for the first time. framework: svelte | react | angular | nextjs | nestjs | express — pass the one the target app actually uses; this server cannot detect it. Returns the guide as markdown plus its source URL. Guidance is a default, not a mandate — follow the user's stated preference when it differs.

  ConnectorOAuth

• list_integrationsA

  WebsitePublisher AIA

  List every integration for a project and whether it is configured (vault secrets present, ready to call) or still needs setup. Compact by default: id, name, category and endpoint names. For the input fields of one integration call get_integration_schema — that also returns its usage guidance. Use detail:true only when you really need every endpoint description of every integration (large response). Full catalog of every platform building block, no auth needed: https://www.websitepublisher.ai/integrations.txt.

  ConnectorAPI key

• request_accounting_integrationA

  ExpenseBotA

  Request an exact accounting package only after checking reviewed direct/import-file destinations and finding no match. Do not use this for a listed or Beta destination or general compatibility. A confirmation-gated write: after user approval, creates one deduplicated request bound to the authenticated account and emails ExpenseBot's internal team. Does not create an integration or immediate availability. For accepted/already-recorded requests, say ExpenseBot will email an update within one week.

  ConnectorNo auth

• preview_ticket_exportA

  Meta CouncilB

  Preview the exact owned ticket content, destination, correlation marker and status mapping for Jira or Linear. Supply destination (Jira project key or Linear team key) for an unlinked ticket. Returns expected export hash; no provider request or external write. Requires explicit integrations:write and tickets:write. Review this preview before export; a changed ticket or provider credential needs a fresh preview.

  ConnectorNo auth

• integrations.connection_statusA

  Admin SubstituteA

  Get detailed status for a specific integration connection, including last sync results, error logs, and supported operations. Useful for diagnosing sync failures.

  ConnectorNo auth

• hub_send_call_to_jiraA

  DutifyA

  Push a call's extracted tasks into one or more Jira projects under the same cloud. Hub fans the action items out across the listed projects. Requires recordings:write scope AND a Jira integration on the workspace (see `hub_list_integrations`). IMPORTANT: returns boolean — `true` means Hub ACCEPTED the request, NOT that it actually landed in Jira. The vendor push happens async and silently fails on bad cloudId/project/expired tokens. To confirm landing, call `hub_get_call` again and check that `jiraProjectId` is populated.

  Connector

  Destructive

  No auth

• hub_send_call_to_jiraA

  DutifyA

  Push a call's extracted tasks into one or more Jira projects under the same cloud. Hub fans the action items out across the listed projects. Requires recordings:write scope AND a Jira integration on the workspace (see `hub_list_integrations`). IMPORTANT: returns boolean — `true` means Hub ACCEPTED the request, NOT that it actually landed in Jira. The vendor push happens async and silently fails on bad cloudId/project/expired tokens. To confirm landing, call `hub_get_call` again and check that `jiraProjectId` is populated.

  Connector

  Destructive

  No auth

• get_connection_linkA

  noticedA

  Get the exact noticed connection or management experience for an integration or MCP server. For Wispr Flow use target='integration' and source='wispr-flow'. Present the returned link exactly.

  ConnectorNo auth

• integrations_add_endpointsA

  DialogBrainB

  Add one or more API endpoints to an HTTP-API integration as callable tools, merged additively into the integration for `base_url` (created if none exists). Each endpoint becomes a tool with params + request/response schemas inferred from the samples you pass. When CREATING a new integration, provide auth: either `identity` (saved Browser Identity name/id) for cookie-session APIs, OR an `auth` block for token/header APIs, e.g. {type:'bearer', token:'...'} or {type:'api_key', token:'...', header_name:'X-API-Key'}. Updates keep the existing auth unless a new `auth` is passed. Returns the new tool count and names. Refresh the tools list afterwards to use them.

  ConnectorAPI key

• integrations_add_endpointsA

  dialogbrainB

  Add one or more API endpoints to an HTTP-API integration as callable tools, merged additively into the integration for `base_url` (created if none exists). Each endpoint becomes a tool with params + request/response schemas inferred from the samples you pass. When CREATING a new integration, provide auth: either `identity` (saved Browser Identity name/id) for cookie-session APIs, OR an `auth` block for token/header APIs, e.g. {type:'bearer', token:'...'} or {type:'api_key', token:'...', header_name:'X-API-Key'}. Updates keep the existing auth unless a new `auth` is passed. Returns the new tool count and names. Refresh the tools list afterwards to use them.

  ConnectorAPI key

• integrations_add_endpointsA

  dialogbrainB

  Add one or more API endpoints to an HTTP-API integration as callable tools, merged additively into the integration for `base_url` (created if none exists). Each endpoint becomes a tool with params + request/response schemas inferred from the samples you pass. When CREATING a new integration, provide auth: either `identity` (saved Browser Identity name/id) for cookie-session APIs, OR an `auth` block for token/header APIs, e.g. {type:'bearer', token:'...'} or {type:'api_key', token:'...', header_name:'X-API-Key'}. Updates keep the existing auth unless a new `auth` is passed. Returns the new tool count and names. Refresh the tools list afterwards to use them.

  ConnectorAPI key

• poker.game.task.syncA

  retroA

  Writes the agreed estimate back to the issue tracker — Jira story points, Linear estimate. Works only for tasks imported from a tracker and only when the integration was connected with write permissions; poker.sources.list shows whether it was. Only the team owner can change a game. Requires mcp:write scope.

  Connector

  Destructive

  No auth

• robyn_changelogA

  Robyn — Gasless Cross-Chain for AI AgentsB

  Machine-readable API history. Pass the version your integration was built against as `since` and you get only what has changed after it, with an explicit `breaking` flag on each entry. CHECK `mustAct` FIRST: if true there are breaking changes and an existing integration may ALREADY be failing — read `entries[].action` for each. `breaking:true` means an existing correct integration could stop working; it is a compatibility claim, not a measure of importance.

  ConnectorNo auth

• roki_get_integration_exampleA

  ROKI ConnectA

  Return a complete, runnable integration example for a stack: configuration, API client, checkout flow, webhook handler with signature verification, and polling fallback.

  ConnectorNo auth

• get_solutionsA

  mcpA

  Industry-specific solutions and integration approaches for different client segments: custodians, exchanges, asset managers, banks, and fintech. Use when users need tailored solution guidance for their specific business type or integration scenario.

  ConnectorNo auth

• tm_get_coverage_summaryA

  MCP Server By TestMu AIB

  Test coverage for a project, overall and per folder, computed live from the project's test cases (matches the Test Cases screen). Also answers requirement and traceability coverage: pass jira_id (any Jira issue key, e.g. TE-123: a requirement, user story, epic, ticket or bug) to get that item's test coverage (the test cases linked to it and how many are automated; zero linked cases means uncovered). For a set of requirements, call once per Jira key. A scope with no test cases returns all zeros; a Jira key that does not exist in the connected Jira returns an error.

  ConnectorOAuth

• tm_get_coverage_summaryA

  TestMu AI (formerly LambdaTest)B

  Test coverage for a project, overall and per folder, computed live from the project's test cases (matches the Test Cases screen). Also answers requirement and traceability coverage: pass jira_id (any Jira issue key, e.g. TE-123: a requirement, user story, epic, ticket or bug) to get that item's test coverage (the test cases linked to it and how many are automated; zero linked cases means uncovered). For a set of requirements, call once per Jira key. A scope with no test cases returns all zeros; a Jira key that does not exist in the connected Jira returns an error.

  ConnectorOAuth

• update_integrationA

  PixelFlowA

  Change the settings of an integration connected to a site, such as Stripe or Calendly. Returns the saved settings. Every integration has a label and a fixed value sent with every event. Integrations that report payments also have a product list and a minimum payment amount. When they are set, events are sent only for those products and for payments of at least that amount. Fields left out stay unchanged. null clears a field. A setting the integration does not support is refused. Use it when the user wants to change which events an integration sends or the value sent with them.

  Connector

  Destructive

  OAuth