MCP Server for Submittals
Hand off the chasing. Keep the stamp.
Eleven parts still have no datasheet and the package goes out Friday. Connect your assistant to your account and put it on the hunt: ask your spec a question and get the section cited back, find every part missing a document, compile the package, read back the log. Works with any MCP-compatible assistant.
The work it takes off your desk
- Find a datasheet for every part missing one; each find waits in a review queue until you accept it
- Answer a spec question with the section and paragraph cited, straight from your uploaded book
- Compile a submittal and report the progress
- Read back the register, the log, and project status without you opening a tab
- Mark a submittal as submitted, send an RFI, and share either with the reviewer, once you say yes
Restrictions that are not settings
The limits below are not preferences anyone can toggle. They are the shape of the access itself.
- Cannot issue, send, or email anyone without showing you first and waiting for your yes
- Cannot accept its own finds into your library
- Cannot touch billing or company settings
- Cannot reach another company's projects, ever
What it looks like on a Tuesday
Ask which parts on the pump station still have no datasheet, and it pages through the register and queues a hunt for up to 25 of them in one call. Ask whether the specified transmitters need HART, and it searches the spec book and answers with the section it read. Hand it the vendor's BOM and it builds the submittal's equipment, asking first before it adds a manufacturer you do not have.
Each find waits in the same review queue you use, so you accept or dismiss it in the chat or on the part's page.
Which assistants connect
Any assistant that speaks the Model Context Protocol, including Claude. It connects through the standard sign-in and approval flow, acts with your access, and everything it does is attributed to your account. Each connection is listed in your account settings with when it was last used, and revoking it there cuts it off at once.
One endpoint, one approval
Point any MCP-compatible assistant at submittalkit.com/mcp, approve the connection once from your account page, and revoke it there any time. You get the hours back. You still review what it brings, and you still sign the record.
Questions integrators ask
RFI-01Which assistants can connect?
Any MCP client that supports sign-in with OAuth, including Claude. Point it at submittalkit.com/mcp, approve the connection once, and revoke it from your account settings any time.
RFI-02Can it send something without asking me?
No. Before it marks a submittal as submitted, sends an RFI, or emails a reviewer a link, it shows you what will happen and waits for your yes in the chat.
RFI-03Can I undo what it did?
Everything it does is a change you could make yourself and take back the same way: a section it adds can be removed, a reviewer it invites can be turned off, and a submission that never went out can be withdrawn.
RFI-04What can it never reach?
Billing, company settings, and any other company's projects. It acts with your access and nothing more.