"UCMDB and Microsiga integration with OpenText" matching MCP tools:

• list_integrationsA

  leadmarinaA

  Which export destinations this account has connected (Close, GoHighLevel, Google Sheets) and whether each is ready to receive leads. Check this BEFORE export_leads or create_automation with a CRM destination — those fail if the integration isn't connected, and Close additionally needs one manual export first to save its field mapping. File destinations (csv/xlsx/json) always work and need nothing connected.

  ConnectorNo auth

• upsertAgentTriggerA

  Duvo MCPB

  Create or update the authenticated user's trigger for an integration on an agent. The integration must already be connected to the agent (its OAuth connection set up in the Duvo dashboard). Set `enabled: false` to pause a trigger without deleting it. An agent holds one trigger per integration for a user, so a save with a different `trigger_type` replaces the existing one — except when that trigger is an @mention trigger, which is managed from the agent's mention setting and answers 409 (`mention_trigger_protected`) here. @mention triggers are best managed from that setting throughout: this route leaves an existing one's `filter_config` untouched, and refuses to create a `teams_mention` trigger without a `filter_config.tenantId` (400, `mention_trigger_workspace_required`) — a Slack mention trigger has no equivalent field to supply.

  ConnectorNo auth

• disconnect_channelA

  Metadata MCP ConnectorA

  Disconnect a specific advertising channel from the Metadata platform. USAGE INSTRUCTIONS FOR LLM: Use this tool to disconnect/remove integration connections for advertising channels. This is useful when users need to remove a channel integration or reconnect with different credentials. WHEN TO USE THIS TOOL: - User asks to "disconnect [channel name]" - User wants to "remove [channel] integration" - User needs to "unlink [channel] account" - User wants to "revoke [channel] access" - User asks to "disconnect my Facebook/LinkedIn/Twitter/Reddit/Google account" - User needs to "reset [channel] connection" - Preparing to reconnect a channel with different credentials SUPPORTED CHANNELS: - facebook: Disconnect Facebook advertising account - instagram: Disconnect Instagram advertising account - linkedin: Disconnect LinkedIn advertising account - twitter: Disconnect Twitter/X advertising account - reddit: Disconnect Reddit advertising account - google: Disconnect Google Ads account IMPORTANT NOTES: - This action will disconnect the channel immediately - Any active campaigns on this channel may be affected - The user will need to reconnect the channel to resume advertising - Always confirm with the user before disconnecting a channel - Check integration status first using get_integrations_status to verify the channel is connected COMMON SCENARIOS: Scenario 1 - Disconnect single channel: "Disconnect my LinkedIn account" → Call disconnect_channel with channel="linkedin" Scenario 2 - Reconnect workflow: "I want to reconnect Facebook with a different account" → First call disconnect_channel with channel="facebook", then guide user to reconnect Scenario 3 - Remove access: "Remove Google Ads integration" → Call disconnect_channel with channel="google" RESPONSE FORMAT: Returns a success/failure status indicating whether the channel was disconnected successfully. EXAMPLE: "Disconnect Facebook" → disconnect_channel(channel="facebook")

  Connector

  Destructive

  API 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

• 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

• update_providerA

  CourierB

  Replace an existing provider configuration. Full replacement — retrieve current config with get_provider first; omitted optional fields are cleared. Changing API keys or settings affects live delivery if this integration is in use.

  Connector

  Destructive

  No auth

• integrations.available_providersA

  Admin SubstituteA

  List all available integration providers (not just connected ones). Shows name, category, auth type, features, and whether an adapter is implemented. Use this to help users discover what they can connect.

  ConnectorNo auth

• pingA

  mcp-serverA

  Verify the connection to Debitura and show which creditor account the API key belongs to. Call this first to confirm the integration is set up correctly.

  ConnectorNo auth

• pingA

  DebituraA

  Verify the connection to Debitura and show which creditor account the API key belongs to. Call this first to confirm the integration is set up correctly.

  ConnectorNo auth

• delete_api_keyA

  Timix.AIB

  Permanently revoke one of your Integration API keys. Any MCP clients or integrations using the key will lose access immediately and cannot be restored. Returns a preview; re-call with the confirm_token and an idempotency_key to commit.

  ConnectorNo auth

• aboutA

  rocketslothA

  Catalog only — reading this is not an application. Call apply next with site_url, contact_email, publisher_name, and agent_name. Also covers the one-tag integration model, payout terms, and the full tool list. No authentication required.

  ConnectorNo auth

• list_integrationsA

  MisarMail MCP ServerA

  List every third-party integration connected to the account, with its sync status and when it last ran. Start here when a question involves external data — it tells you which integrations exist and whether they are actually syncing. For one integration's configuration and scopes, follow up with get_integration; to turn one on or off, use toggle_integration. Reads only; nothing is connected, disconnected, or re-synced. Requires an API key. An integration listed as connected can still be failing to sync, so check the status rather than assuming. An empty list means nothing is connected yet, which is not an error.

  ConnectorNo auth

• get_integrationA

  MisarMail MCP ServerA

  Get one integration in full: its configuration, the scopes it was granted, and the result of its last sync. Use it to diagnose an integration that list_integrations shows as unhealthy, or to check which scopes were granted before relying on a capability. Covers a single integration — list_integrations gives the overview. Reads only; it does not re-run a sync or change any setting. Requires an API key. The response describes what the integration is permitted to do, which is not the same as what it has successfully done — read the last sync result for that.

  ConnectorNo auth

• toggle_integrationA

  MisarMail MCP ServerA

  Turn one third-party integration on or off. This changes live behaviour: DISABLING stops all syncing through that integration, so data quietly stops flowing until it is re-enabled. It does not disconnect the integration or revoke its credentials — the connection and its scopes survive, which is why re-enabling picks up where it left off. Safe to repeat: setting an integration to the state it is already in changes nothing. Requires an API key. Call list_integrations first so you know the current state rather than toggling blind.

  ConnectorNo auth

• list_examplesA

  EpsilonA

  List runnable Epsilon integration examples (Python cron DCA, LangChain tools, Vercel AI SDK tools, Telegram bot). Fetch full source with get_example. No API key required.

  ConnectorNo auth

• oracle.discovery_bundleA

  InterAI Risk OracleA

  Read-only bootstrap or handoff bundle with service identity, interfaces, runtime mode, contracts, schemas, and sample payloads in one response. Use it for complete integration context; use oracle.service_descriptor for focused service metadata, oracle.agent_card for A2A capabilities, or oracle.get_pricing for costs.

  ConnectorNo auth

• oracle.service_descriptorA

  InterAI Risk OracleA

  Read-only general service descriptor with identity, endpoints, billing, trust, and supported agent protocols. Use it to inspect service-level integration metadata; use oracle.agent_card for A2A skills or oracle.discovery_bundle for the complete bootstrap package.

  ConnectorNo auth

• list_integrationsA

  YouSpotA

  What the user has connected, and what they could connect. Returns every integration available to this account with `connected` true/false, the accounts behind it, the tools it unlocks, and the URL to connect or manage it. Call this BEFORE telling anyone to connect anything, and before saying a source is unavailable: guessing is how the assistant has told people to connect accounts they already had. An integration missing from the list is not offered to this user at all, so do not suggest it. `suggested` is what is worth connecting next, best first, each with the payoff in the user's terms: use it when asked what would help, and lead with the first one rather than listing the shelf. Connecting is a browser grant: hand the user the URL, never claim to have done it.

  ConnectorNo auth

• analyze_companyA

  FACTRAILA

  Deprecated: use factrail_verify instead. Use only when an older integration still calls this experimental tool; financial and credit data sources are unavailable and returned fields are null.

  ConnectorNo auth

• disconnect_connectionA

  MarkA

  Disconnects an integration. With zernio (Social publishing) this disconnects every social account at once, not one channel, and no scheduled social post will publish until each account is reconnected in the Mark app. To see which social accounts would go, call list_channels first. Connecting accounts cannot be done from the agent. Related: list_connections, list_channels.

  Connector

  Destructive

  OAuth