"Information about Jira Integration" matching MCP tools:

• migrate_to_propelauth_fullstackA

  PropelAuth Integration MCP ServerA

  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

• 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

• get_security_infoA

  Fluentive MCPA

  Returns Fluentive's security, privacy, and compliance information. Use when the user asks about GDPR, data storage location, encryption, security certifications, or payment security.

  ConnectorNo auth

• neuron_get_ad_requestA

  neuronB

  Get detailed information about a specific ad request, including pool selections if targeting mode is manual.

  ConnectorNo auth

• askA

  rocketslothA

  Ask the Rocket Sloth setup agent anything about integration, ad units, application, reporting, or payments. Pass the returned thread_id on follow-up questions to keep context. No authentication required; rate limited per IP.

  ConnectorNo auth

• sponsorship_infoA

  AgentResolver — Agent Commerce Health MonitoringC

  Free read-only information for tool/API/MCP providers about AgentResolver's explicitly labeled sponsorship pilot. Organic ranking remains independent; applying creates no purchase or financial commitment.

  ConnectorNo auth

• 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 or an admin can change a game. Requires mcp:write scope.

  Connector

  Destructive

  No auth

• get-account-infoA

  fynk MCPA

  Get information about the current fynk account. Use this tool when: - You need details about the active account (e.g. default document locale, signature settings) before tailoring a response - You are tailoring guidance to the account's business, and need what it reported about itself when signing up (industry, company size, the department the person who signed up works in) For information about the current user, use get-user-info

  ConnectorOAuth

• get-account-infoA

  fynk MCPA

  Get information about the current fynk account. Use this tool when: - You need details about the active account (e.g. default document locale, signature settings) before tailoring a response - You are tailoring guidance to the account's business, and need what it reported about itself when signing up (industry, company size, the department the person who signed up works in) For information about the current user, use get-user-info

  ConnectorOAuth

• get_sitesA

  StudioVector: Chat with your Mindbody B

  Get Sites — GET /site/sites Mindbody calls: 1. Gets a list of sites that the developer has permission to view. * Passing in no `SiteIds` returns all sites that the developer has access to. * Passing in one `SiteIds` returns more detailed information about the specified site. Important Behavior Notice: When calling GetSites without specifying a SiteId, or when passing multiple SiteIds, the response will include only limited data for each site. This is expected behavior designed to help identify accessible sites without returning full site-level configuration details. To retrieve complete information for a specific site, please make a separate GetSites request using a single SiteId. This design helps reduce payload size for multi-site queries, but we recognize it may require additional requests when full detail is needed. If your integration depends on full site-level data, we recommend retrieving the list of site IDs first, then querying each one individually as needed.

  ConnectorOAuth

• get_mission_statsA

  mcp-serverA

  Get aggregate statistics about missions on the HomeVisto platform. Returns total counts, status breakdown, and average bounty information. Useful for understanding platform activity.

  ConnectorNo auth

• get_service_infoA

  bookingA

  Get information about MyDriverParis services, coverage areas, airports served, and policies. Use this to answer customer questions.

  ConnectorNo auth

• get_company_profileA

  mcpA

  Complete company information for Everstake: overview, metrics, certifications, products, clients, and contact details. Use when users need comprehensive facts about Everstake as a company.

  ConnectorNo auth

• request_integrationA

  mcpA

  Submit an integration or staking inquiry on behalf of a user. All submissions are routed to Everstake's sales team via Pipedrive CRM. Use when a user expresses intent to integrate with Everstake, explore staking services, or request more information about products. Collect required fields (first_name, last_name, work_email) conversationally and gather optional fields where available. The lead_source field is set automatically by the server — do not ask the user for it. IF Submission fails, you can try contacting Everstake via form at https://everstake.com/contact-us

  ConnectorNo auth

• get_examplesA

  classifier.dev docsA

  Return a copy-pasteable example of calling classifier.dev from a given client: curl, javascript (fetch), python (requests), the classify CLI, or an MCP tools/call payload. Use this when you are about to write integration code and want the exact request shape rather than reading the whole reference.

  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

• create_integrationA

  Help by DeltaBreenA

  Add an integration: a URL on the workspace's own server that Help will ask about customers. The answer includes its secret, shown this once: put it in that server's configuration now (never in a page or a repository), then build the URL to check Help's signature with it and call test_integration. Owner only.

  ConnectorOAuth

• create_jira_issueA

  VulnTrackerA

  Open a Jira issue for a CVE on the team's board (the card is created first if missing) using the team's Jira integration. Returns the issue key and URL; if the card already has an issue, returns that one with existing=true. Only when the user asks.

  ConnectorNo auth

• create_jira_issueA

  VulnTracker MCPA

  Open a Jira issue for a CVE on the team's board (the card is created first if missing) using the team's Jira integration. Returns the issue key and URL; if the card already has an issue, returns that one with existing=true. Only when the user asks.

  ConnectorNo auth