MCP use case
Send contracts to the inbox from your agent
Your agent already reads your email. Have it submit the messages that contain contract terms to the inbox, where you review the proposed fields before anything is created.
Claude Code
Find the email where Brightloom confirmed our plan and add it to the vendor inbox.
- Submitted 'Your Brightloom Studio subscription' to the inbox.
- It is waiting for your review; nothing is recorded until you accept it.
What you get
What changes when the agent does it
Terms leave the inbox
Confirmation emails become reviewable items instead of buried threads.
You still decide
The agent submits; you accept or reject each proposal.
Click-through deals count
A self-serve confirmation becomes a contract in its own right.
How it works
Set it up in three steps
This job needs a write key.
- 1
Issue a write key
Submitting to the inbox is a reversible write, so the key needs the write ceiling.
- 2
Submit the text
The agent sends the email text to the inbox.
inbound_createFromText - 3
Review in the product
You check the proposed fields and accept or reject them.
Questions
Frequently asked questions
Can the agent create the contract directly?
No. It submits an inbox item. A person accepts the proposal before a vendor or contract exists.
Does the email text go anywhere else?
It is stored with the inbox item and sent to the extraction provider named in the privacy policy.
More
Keep exploring
- Ask what renews this quarter, from Claude Code
Connect Claude Code to your vendor register over MCP and ask what renews, what you can still do and what it costs.
- Write a weekly renewal digest for your team
Have an agent read the renewal calendar and findings each week and write a short digest of what needs a decision.
- Clean up duplicate vendors and missing owners
Have an agent find duplicate vendors and missing owners, then propose fixes you approve.