The IDMC Troubleshooting server enables AI agents to investigate and resolve operational issues by providing real-time visibility into IDMC schedules, assets, mappings, connections, jobs, Secure Agents, and Data Ingestion and Replication tasks.
This MCP Server enables AI agents to inspect, diagnose, and monitor operational health across IDMC. It exposes read-first tools for analyzing platform schedules, asset dependencies, mapping logic, connections, activity and session logs, running jobs, Secure Agent health, and Data Ingestion and Replication tasks. By consolidating platform endpoints into a single interface, agents can investigate root causes, evaluate failure impact, and verify runtime health without manual UI navigation.
Note:
Effective in the July 2026 release, the IDMC Troubleshooting MCP server is available for preview. Preview functionality is supported for evaluation purposes but is unwarranted and is not supported in production environments or any environment that you plan to push to production. Informatica intends to include the preview functionality in an upcoming release for production use, but might choose not to in accordance with changing market or technical circumstances. For more information, contact Informatica Global Customer Support.
Key capabilities
This MCP server offers the following key capabilities:
•Failure triage. Retrieve activity logs, session logs, and running job states to pinpoint the root cause of task or job failures.
•Dependency and impact analysis. Discover assets and their upstream or downstream dependencies to evaluate potential impact before making changes.
•Runtime health monitoring. Inspect Secure Agent health for each IDMC service that runs on it, connection reachability, and Data Ingestion and Replication lag.
Use cases
Use this MCP server to address the following use cases:
•Incident diagnosis. Isolate the root cause of failed jobs through end-to-end troubleshooting across job logs, underlying Secure Agent services, and connections.
•Change safety. Trace asset lineage and dependencies before modifying or retiring assets to evaluate blast radius and locate agent-scoped connections.
•Replication and mapping health. Monitor task configurations for Data Ingestion and Replication tasks, or evaluate transformation logic, metadata, and connections for Data Integration mappings.
•Schedule auditing. Review and audit job schedules across IDMC to locate and troubleshoot execution timing issues.
Tools
The following table describes the tools available on this MCP server:
ts_find_asset_dependencies
Returns the upstream or downstream dependencies of an asset by asset ID to assess operational impact before modifying or retiring the asset.
ts_find_connections_by_agent
Returns the connections associated with a Secure Agent or runtime environment. Optionally, filter by connection type, such as Oracle or Salesforce.
ts_find_objects
Searches the IDMC asset catalog for mappings, tasks, and connections. Filter by asset type using a FIQL query, such as type=='MTT' to return only mapping tasks. Optionally, set up pagination to handle large inventory exports.
ts_get_activity_log
Returns completed job and task activity log entries. Optionally, filter by task or set up pagination. Use this tool as an entry point to begin diagnosing failures.
ts_get_activity_session_log
Returns the detailed session log for an activity log entry by ID. Includes execution traces, error codes, and row-level processing information to evaluate job failures.
ts_get_agent_health_summary
Returns an organization-wide health summary that identifies active Secure Agent services and runtime details across all Secure Agents.
ts_get_agent_service_status
Returns the operational status of Secure Agent services on a Secure Agent, such as Data Integration Server, the Database Ingestion service, or API Microgateway Service.
ts_get_agents
Returns a list of registered Secure Agents in the organization. Use this tool to create an inventory of Secure Agents, verify their availability, and identify agents that aren't assigned to any Secure Agent group.
ts_get_connection_metadata
Returns the field structure of an object for a source or target connection.
ts_get_connection_objects
Returns the objects that a source or target connection can access, such as tables, files, and entities.
ts_get_connections
Returns connections. Optionally, filter by name substring or cap results. Use this tool to inventory connections or to locate the connection for a failed job.
ts_get_ingestion_task_details
Returns configuration details for a file ingestion and replication task. Includes project and folder locations, source and target connections, file transfer parameters, assigned Secure Agent group, and create and update timestamps. File transfer parameters include the file pattern matching rules or explicit file lists, source and target directories, and stability and duplicate-check settings.
ts_get_mapping_details
Returns configuration details for a mapping by mapping ID. Includes the mapping name, description, parameters, objects, mapping status, tasks associated with the mapping, and deployment details. This tool requires the mapping ID. If you only have the mapping name, use the ts_get_mapping_details_by_name tool instead.
ts_get_mapping_details_by_name
Returns the configuration details for a mapping by mapping name. Includes the mapping name, description, parameters, objects, mapping status, tasks associated with the mapping, and deployment details. This tool requires the mapping name. If you only have the mapping ID, use the ts_get_mapping_details tool instead.
ts_get_mapping_transformation_details
Returns transformation details for a mapping by mapping ID. Includes advanced properties, such as tracing level and connection-specific settings, and sequence generator states. Optionally, filter by transformation type. This tool requires the mapping ID. If you only have the mapping name, use the ts_get_mapping_transformation_details_by_name tool instead.
ts_get_mapping_transformation_details_by_name
Returns transformation details for a mapping by mapping name. Includes advanced properties, such as tracing level and connection-specific settings, and sequence generator states. Optionally, filter by transformation type. This tool requires the mapping name. If you only have the mapping ID, use the ts_get_mapping_transformation_details tool instead.
ts_get_running_jobs
Returns running jobs. Optionally, includes child jobs.
ts_get_schedule_details
Returns schedules. Optionally, filter the results using a FIQL query to audit or locate schedules.
ts_get_taskflow_status
Returns the run status of published taskflows. Optionally, filter results by run ID, run status, and start and end time windows. Omit parameters to list recent taskflow runs. This tool provides read-only telemetry and doesn’t start, stop, resume, or otherwise change a taskflow run.
Note:
In AI Agent Engineering, the MCP server tools are called "actions."
•idmc-global skill (Recommended). The primary coordinator that runs all other troubleshooting skills. Informatica recommends installing this skill to handle end-to-end troubleshooting.
•Individual troubleshooting skills. Focused skills that handle specific troubleshooting and diagnostic areas. You can install only the skills that your AI agents use.