Skip to main content

Use Third-Party MCP Connections in Ironclad Agent via the MCP Gateway

!

Release: The following functionality will be live on November 5th. To learn more about the features included in our November release, refer to What's New in Ironclad: November 2026.

Summary

Ironclad agent can connect to a third-party MCP server and use that system’s tools to answer questions alongside Ironclad context. For example, it can retrieve supplier usage or benchmark data from a connected procurement system while you are working in Ironclad Agent.

This is Ironclad Agent as an MCP client: Ironclad Agent calls the external server on behalf of the signed-in user. It is different from the Ironclad MCP Server, where Claude, ChatGPT, or another external client connects into Ironclad.

Permissions

Features

Ironclad Agent, MCP

Permissions

  • This feature is in Early Access and may change before it is generally available. If you're interested in this feature, please fill out this form to apply for EAP access.

  • You need your own account and permission in the third-party system.

  • Each user must complete their own OAuth connection. An admin cannot connect on another user’s behalf.

Set up a connection

  1. In Ironclad, click the Agent icon in the bottom right corner.

  2. Click Connectors indicated by a plug icon.

  3. Click Manage Connectors.

  4. If you click All Available, you will see Legora and Tropic added recently. More to be added going forward.

  5. If you don’t see the connector you want, select Add custom server.

  6. Enter the MCP server URL supplied by the vendor.

  7. Select Add.

  8. Complete the vendor’s OAuth authorization flow, if prompted.

  9. Return to Ironclad Agent and confirm that the connector shows up when you click ‘Manage Connectors’.

Example: Tropic

Use the vendor URL approved for your rollout. Do not substitute a URL from an untrusted source.

Use the connection in agent

If you use similar MCP connectors, such as Spendflo and Zylo, specify which connected system you want Ironclad Agent to use. Start your request with the connection name—for example, “Ask Zylo…” or “Ask Spendflo…”—to route it to the intended MCP connection.

Examples:

  • “Check from Zylo, what is our current usage for Lovable?”

  • “Ask Spendflo if the pricing in this contract is competitive?”

  • “Use Tropic to compare this quoted price with relevant market benchmarks.”

Ironclad Agent may combine the external result with Ironclad contract context when the task calls for it. Review the returned answer and the underlying source system before making a material business or legal decision.

Disconnect or reconnect

Use Manage Connections to disconnect a connection or start the authorization flow again. Reconnect when the vendor token expires, permissions change, or agent reports an authorization failure.

Troubleshooting

  • The connection option is missing: Ask your Ironclad administrator whether third-party MCP connectors are enabled for your company.

  • The connection will not save: Verify the server URL and ask the vendor or administrator to confirm that the URL is approved.

  • OAuth fails: Restart the connection flow and confirm that you are signing in with the intended vendor account.

  • Ironclad Agent returns no data: Confirm that your vendor account can access the requested information and that the question names the intended connection.

  • Ironclad Agent uses the wrong source: Re-run the prompt with an explicit prefix such as “Ask Zylo” or “Ask Tropic.”

  • A tool times out or fails: Try a narrower question, then retry after a short wait. If the issue persists, capture the prompt, approximate time, connection name, and error message for support.

Resources

Explore articles, courses, and support options to get the most out of Ironclad.

Help Center

  • No relevant resources at this time.

Academy

  • No relevant resources at this time.

Support

Did this answer your question?