Claude Ironclad Contracts connectorWhat Claude can do in your Ironclad Contracts account.
The Claude Ironclad Contracts connector exposes 6 tools. 4 of them read your repository and your obligations, 2 create or edit obligations, and none is left undocumented. Below: what Claude finds, what it records, and what your Ironclad setup decides.
Verified Trustpilot reviews · AI, automation & growth agency
What changes once Claude can search your contracts
Legal and ops teams lose time hunting for the one agreement that answers a question. With this connector, you type the question the way you would ask a colleague, and Claude queries your Ironclad repository itself, returning only contracts your own account is allowed to open. It can also keep the obligations attached to those contracts up to date.
Answer a contract question in one message. Procurement wants every supplier agreement governed by a given law that ends within the year: Claude sends that sentence to conversational_search, the same engine behind Ironclad's own conversational search, and lists what comes back.
See what you owe, and to whom. Through list_obligations and get_obligation, Claude reads the commitments tied to your contract records, with their type, owner and status, so a quarterly review starts from facts rather than memory.
Log a new commitment as it comes up. A renewal adds a reporting duty: create_obligation records it against the right contract, and update_obligation moves its status once it is done.
What it will not do: the search tool is strictly read-only, so it never edits, drafts or deletes a contract. No tool removes an obligation. The five obligation tools only work if your company has Ironclad's Obligations add-on. And nothing fires on its own when a contract nears its end date; that kind of background job is the work of an automation tool, a different trade that the Integrations hub covers.
Five words before you connect
The vocabulary Claude uses around this connector, quickly.
- Connector
- The link you set up once between Claude and an account you already own, so Claude can work in that account while it answers.
- Tool
- One named action a connector lets Claude take. Claude chooses the tools it needs by itself, and the directory lists each one by name.
- Authorization
- The login screen of the service itself, where you give Claude the access it will use. Granted once per person, and revocable.
- Approval
- The confirmation Claude waits for before doing something that changes your account, shown in the conversation when it matters.
- MCP
- The shared standard connectors are built on, which is what lets an assistant such as Claude talk to an outside service like Ironclad.
Connect Ironclad to Claude in three steps
- 01
Find Ironclad in Claude
Open Claude's settings, go to Customize and then Connectors, and look for Ironclad Contracts in the list. On a Team or Enterprise workspace, an Owner or Primary Owner switches the connector on before each member can sign in.
- 02
Start the connection
Click Connect on its row, then sign in to Ironclad in the window Ironclad opens. The login belongs to Ironclad, which is how it ties each request to one named user. If the link breaks later, Disconnect and connect again.
- 03
Review the authorization screen
Read the authorization screen before you accept. It is Ironclad's screen, not Claude's, and it is what defines what the access covers. You can also withdraw that access later from the Ironclad side.
The 6 tools, split by what they do
Ironclad Contracts gives Claude 6 tools: 4 that read your account, 2 that change something in it.
Two groups: what Claude reads and what it changes in Ironclad. Tool names stay exactly as Claude displays them.
- 4 read
- 2 write
What Claude reads (4)
4 toolsFour tools that look at contracts and obligations and leave them untouched.
conversational_search
Runs a plain-language query across your contract repository, using the engine behind Ironclad's dashboard search, and returns only results your Ironclad login may see. It understands semantic filters such as governing law or an expiry window.
get_obligation
Opens a single obligation tied to an Ironclad record and shows its details: type, name, description, status and owner. Claude reads one commitment in full instead of a list.
list_obligations
Gives Claude a list of the contractual obligations linked to your records, so it can scan many commitments at once and sort or summarise them for you in the chat.
list_obligation_types
Returns the categories of obligation your Ironclad instance uses. Claude checks this list so a new entry lands in a type that already exists instead of guessing a label.
What Claude changes (2)
2 toolsTwo tools that record or edit obligations. No source details their confirmation, so the general rule below applies.
create_obligation
Approval: see the ruleRecords a new contractual obligation against an Ironclad record, with its type, name, description, status and owner filled in from what you told Claude.
update_obligation
Approval: see the ruleEdits an obligation that already exists: Claude can move its status, hand it to another owner or rewrite its description after a discussion.
What Claude checks with you first
By default, Claude stops and asks before each action it takes on an account on someone's behalf, and the prompt appears in the conversation at that moment.
On Team and Enterprise workspaces, owners decide whether a member can let some actions through without being asked every time. They can also restrict what a connector may do for the whole organization, for example keeping reading open and closing writing. That setting binds everyone, and nobody lifts it from a personal account. Claude also acts with the rights of the person who connected, nothing more: a contract your Ironclad user and group permissions hide stays hidden in the chat.
Which plans include it
None of the 819 sheets in the official directory shows plan availability, so the answer for this connector is published nowhere.
What Anthropic does publish is the general rule: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner enables the connector before members connect one by one. For the current state of Ironclad Contracts on your account, open its sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you, so nothing starts on its own when a contract is signed or reaches its end date.
This connector is documented by its publisher only: no page of Claude's help center covers it. The tool list is an observed floor, not a promise, since an administrator can open actions that no public sheet shows. The partner badge is not a security audit, and Anthropic says on every sheet that it does not choose the tools a publisher exposes nor guarantee they work as announced. Other pages of this series, such as the Claude asana connector, use the same reading grid.
Need help connecting Ironclad Contracts to Claude?
A person reads every message.
