To connect to Informatica MCP servers, you need the endpoint URL and authentication credentials.
MCP server endpoint URL
This is the address your MCP client uses to communicate with the Informatica MCP server. The MCP server endpoint URLs are displayed in the marketplace when you select the MCP server or view its documentation.
If you use AI Agent Engineering, the endpoint URL is displayed in the code block on the MCP server’s Configuration tab.
Authentication credentials
The authentication credentials you provide vary based on the authentication method you use.
You can use any of the following methods to authenticate with an Informatica MCP server:
JSON web token (JWT) authentication
If your organization uses JWT authentication, you can use the bearer token to authenticate with the MCP server. You get the token when you log in to IDMC through the REST API.
Session-based authentication
If your organization uses session-based authentication, you can use the session ID to authenticate with the MCP server. You get the session ID when you log in to IDMC through the REST API.
Note:
Effective in the October 2025 release, session-based authentication is deprecated. Informatica intends to drop support for session-based authentication in a future release. For more information, see the important notices in What's New.
OAuth authentication
You can use an OAuth token for authentication if your organization uses SAML single sign-on or AI Agent Engineering. If your organization uses SAML single sign-on, you can use a federated identity provider like Azure AD or Okta to generate the token. If you use AI Agent Engineering, you'll need to register a client directly with Informatica’s internal authorization server.
You enter the authentication credentials in the configuration file for the tool you use to connect to the MCP server. If you use AI Agent Engineering, the code block on the MCP server’s Configuration tab shows where to enter the authentication credentials.