Skip to main content
Ironclad empowers legal and business teams to manage contracts from intake to signature. With this integration, you can search, update, and monitor workflows or records using clear, natural language prompts that drop right into your automations.
Built-in pagination across workflows, comments, emails, and records keeps your contract data flowing smoothly even at high volume.

How to Use MCP Nodes

What is Ironclad MCP?

The Ironclad MCP node gives AI-powered access to Ironclad workflows, approvals, signatures, records, and schemas. Describe what you need in natural language and it returns structured data you can pass directly to the next step in your automation.

What Can It Do for You?

  • Discover and monitor workflows with filters and pagination, then return the fields you need for reporting
  • Update approvals, manage signatures, and post comments to keep deals moving forward
  • Read and enrich records, including properties, links, and relationships, for accurate contract data
  • Retrieve workflow and record schemas so you can map fields dynamically in any workflow

Available Tools

ToolWhat It DoesExample Use
get_meGet the current authenticated user’s information including ID, email, username, and granted token scopes”Return structured data for the current user including id, email, username, and scopes”
list_workflowsList workflows in your Ironclad account with filtering options and automatic pagination support”List workflows where status equals workflow status and owner email is owner email, return id, ironcladId, title, status, and createdAt as structured data”
get_workflowView data for a specific workflow by ID or Ironclad ID”Using workflow id, return title, status, counterparty, owner email, createdAt, and ironcladId as structured data”
list_workflow_approval_requestsList all approval requests on a workflow with pagination support”Given workflow id, list approval requests and return requester name, role, status, and requestedAt as structured data”
update_workflow_approvalUpdate an approval status for a specific role on a workflow”For workflow id, set approval status for role role name to approved or pending, return role, previous status, and new status as structured data”
get_workflow_sign_statusGet information about a workflow in the sign step”Given workflow id, return signers, routing order, provider, and overall sign status as structured data”
manage_workflow_signatureSend requests, cancel requests, update or delete signers, remind signers, or create recipient URLs”For workflow id, create recipient URLs for signer emails signer emails list, return signer email and recipientUrl as structured data”
list_workflow_commentsList all comments on a workflow with automatic pagination”Given workflow id, list comments and return author name, text, and createdAt as structured data”
create_workflow_commentCreate a new comment on a workflow”On workflow id, post comment comment text and return comment id, author, and createdAt as structured data”
update_workflow_metadataUpdate specific fields on a workflow using patch operations”For workflow id, update field field name to new value, return field name and updated value as structured data”
list_workflow_emailsList all email threads for a workflow with automatic pagination”Given workflow id, list email threads and return subject, sender, recipients, and lastActivityAt as structured data”
get_workflow_schemaRetrieve the schema for a workflow design”For workflow design workflow design identifier, return attribute names, types, and required status as structured data”
manage_workflowPause, resume, or cancel workflows”For workflow id, pause the workflow and return id and new lifecycle status as structured data”
list_recordsList records with filtering, sorting, and automatic pagination support”List records where type equals record type and title contains search term, return record id, type, title, status, and lastModifiedAt as structured data”
get_recordView a specific record by ID or Ironclad ID”Using record id, return title, type, status, key properties, and related workflow id as structured data”
update_record_metadataUpdate properties, links, or relationships on a record”For record id, set property property name to new value, return property name and updated value as structured data”
get_smart_import_predictionsRetrieve prediction status for a smart import record or all records in an import”Given smart import record id, return prediction status, suggested fields, and confidence scores as structured data”
get_records_schemaView schemas for contract records, including record types and metadata properties”Return available record types and for each type return property name and type as structured data”
list_scim_schemasList SCIM schemas with their attributes and metadata”List SCIM schemas and return schema name, id, and attribute paths as structured data”

How to Use

1

Create Your Ironclad MCP Node

Go to your node library, search for Ironclad, and click “Create a node with AI”
2

Add Your Prompt

Drag the Ironclad MCP node to your canvas and add your prompt in the text box.
3

Test Your Node

Run the node to see the results. If everything looks good, you’re all set. If you need tweaks, check the troubleshooting tips below.
4

Save and Reuse

Once your Ironclad MCP node works as expected, save it to your library so you can use it in any workflow.

Example Prompts

With 19 available tools, these examples showcase popular use cases. Workflows – Discovery and Monitoring:
List workflows where status equals `workflow status` and owner email is `owner email`, return id, ironcladId, title, status, and createdAt as structured data
Approvals – Update a Role’s Status:
For `workflow id`, set approval status for role `role name` to `approved or pending`, return role, previous status, and new status as structured data
Comments – Collaborate in Context:
On `workflow id`, post comment `comment text` and return comment id, author, and createdAt as structured data
Signatures – Create Recipient Links:
For `workflow id`, create recipient URLs for signer emails `signer emails list`, return signer email and recipientUrl as structured data
Records – Search and Enrich:
List records where type equals `record type` and title contains `search term`, return record id, type, title, status, and lastModifiedAt as structured data
Records – Update a Property:
For `record id`, set property `property name` to `new value`, return property name and updated value as structured data
Schemas – Map Fields Dynamically:
For workflow design `workflow design identifier`, return attribute names, types, and required status as structured data
Start with one action per node. Use list tools to find IDs, then feed those IDs into update or manage tools in the next node for fast, reliable workflows.

Troubleshooting

If your Ironclad MCP node isn’t working as expected, try these best practices:

Keep Prompts Simple and Specific

  • Good: “List workflows where title contains search term and return id and status as structured data”
  • Less Efficient: “Find all workflows for owner email, approve for role name, send signature requests to signer emails list, and then add a comment with comment text
For best results, create separate nodes for discovery, approval, signatures, and commenting. Ironclad MCP works best with focused, single-action prompts.

Match What Ironclad Can Do

  • Good: “For workflow id, set approval status for role role name to approved or pending and return new status”
  • Less Efficient: “Notify the approver in Slack and then approve the workflow”
Ironclad MCP excels at contract workflows and records. To send Slack notifications, combine it with the Slack Message Sender or Reader node in your workflow.

Break Complex Tasks Into Steps

Trying to do everything in one prompt can cause timeouts or missed fields:
Search workflows matching `status`, update approvals for role `role name`, create recipient URLs for signers `signer emails list`, and post comment `comment text`
A more efficient approach is to break the task into smaller nodes:
1

Step 1: Get Workflows

List workflows where status equals status, return workflow ids and titles as structured data
2

Step 2: Update Approvals

For workflow id, set approval status for role role name to approved or pending, return role and new status as structured data
3

Step 3: Manage Signatures

For workflow id, create recipient URLs for signer emails signer emails list, return signer email and recipientUrl as structured data
Connect these nodes sequentially in your workflow. The workflow ids from Step 1 feed into Step 2, and the outputs from Step 2 feed into Step 3.

Focus on Data Retrieval

Ironclad MCP is great for pulling or updating Ironclad data. For summaries or email drafts, pair it with other nodes. Example:
  • Good prompt: “Given workflow id, list comments and return author, text, and createdAt as structured data”
  • Less Efficient: “List comments, summarize them, and draft an email to the team”
Use the Ask AI node to summarize and Gmail Sender/Reader to draft or send emails. Keep Ironclad prompts focused on Ironclad data.

Troubleshooting Node Creation

In the node creation window, select “Request changes” and tell the AI you received empty outputs. It will add debug logs and verify the API response.
In the node creation window, use “Request changes” to explain what you expected versus what you received so the AI can refine the node.
First click “Fix with Gummie”. If multiple attempts fail, simplify your prompt or contact support.
Node creation often takes a few tweaks. Use the chat interface in the node creation window to refine filters, output fields, or pagination.

Need More Help?