The Legora integration connects Ironclad contract intelligence to Legora through the Ironclad MCP server. In the current beta, users can search Ironclad workflows and contracts, select multiple executed contracts, and transfer them to Legora for Tabular Review. This article explains the integration's purpose, current scope, and an observed NDA comparison and redlining workflow.
Use Case
Legal teams can use Ironclad to manage contract records and Legora for legal analysis and document review. In the demonstrated workflow, a user uploads an NDA to Legora, retrieves a precedent confidentiality definition from Ironclad, compares the definitions, and prepares a redline draft in Legora.
Prerequisites
| Features |
Legora's Ironclad integration, Ironclad MCP server, and limited beta access. |
| Connected Systems |
Legora and the Ironclad MCP server. |
Release: This article describes features and functionality planned for our October release. Some features may not be available until October 8, 2026.
Limited Beta: The Legora integration is currently in limited beta. Features or behaviors may change before the integration becomes generally available. Access is currently restricted to approved customers. If you're interested in this feature, please reach out to your Ironclad representative or Support to see if you're eligible for EAP access.
Legora Integration Features
The current beta supports the following capabilities:
Invoke Ironclad from a Legora Agent prompt by mentioning
@ironclad.Search Ironclad workflows and contracts from Legora.
Review multiple matching Ironclad records, including record IDs, titles, statuses, and execution dates.
Search for and select multiple executed contracts stored in Ironclad.
Transfer selected contracts to Legora for Tabular Review.
Ground Legora's analysis in contract context from the Ironclad repository.
The integration uses existing MCP client and server capabilities. Search results are permission-aware and are limited to Ironclad data the authenticated user can access.
How It Works
At a high level, the Ironclad workflow works as follows:
The user connects Legora to the appropriate Ironclad environment and authorizes access.
The user mentions Ironclad in a Legora Agent prompt.
Legora searches Ironclad workflows and contracts.
The user reviews matching records and selects one or more executed contracts.
Legora transfers the selected contracts for use in Tabular Review.
The user reviews the results in Legora.
Example: Compare and Redline an NDA in Legora
The following workflow assumes that you have:
- Access to Legora and the Agent workspace.
- An NDA or other document available to upload into Legora.
- Permission to view the precedent contract in Ironclad.
- Connected and configured the integration in Ironclad under Company Settings.
To compare and redline an NDA in Legora:
- Open the Legora Agent from the left side panel.
- Click the plus icon (+) and select Attach file from the dropdown menu.
- Select Upload file, and attach your NDA.
- Prompt Legora to summarize the uploaded NDA's confidentiality section.
- Review the confidentiality summary and then prompt Legora to find a precedent NDA in Ironclad.
-
Example:
@ironclad, do we have a precedent NDA with Example Company, and if so, what's our standard confidentiality definition?
-
Example:
Compare the confidentiality definitions.
-
Ask Legora to create a redline draft.
Example: Redline the confidentiality section of the uploaded NDA to match the definition we just pulled from Ironclad.
Select Review to open the proposed edits. The Edits view shows a summary of the proposed change alongside redline markup in the document editor.
Confirm that the proposed definition, exclusions, and surrounding language match the intended precedent and the reviewer's legal requirements.
If the redline is acceptable, save the draft to Legora.
Known Limitations
The integration is in beta and may change as Legora and Ironclad validate the workflow.
Configuration, access behavior, and error handling are still being validated during beta.
Users may not see citations, source links, or highlighted contract locations in MCP responses.
Legora may identify a record as relevant based on metadata or title and then determine from the document content that it is a different contract type. Users should verify the returned record before relying on the analysis.
The integration does not replace Ironclad workflows, approvals, repository permissions, or contracting controls.
Resources
Explore articles, courses, and support options to get the most out of Ironclad.