Trussi AI
by Trussi AI
Query a Trussi roofing CRM — projects, pipeline, job costing and collections — from an AI agent, and create quotes, comments and calendar events. Anthropic lists 32 tools; Trussi publishes no tool list. OAuth 2.0 with PKCE and two scopes, read and write.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Trussi AI via MCP
https://my.trussi.ai/api/mcp/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Trussi AI Tools & Capabilities (32)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Trussi publishes no tool list for this server. The 32 names come from Anthropic's directory. We checked the connector page, the site's
sitemap.xml, every product and integration page, the FAQ, and allms.txtprobe that returned the site's soft-404 shell. No vendor enumeration exists to diff against, in either direction. - The vendor advertises a capability the tool list does not support. Trussi's connector page says an assistant can "message customers"; no listed tool can. We could not establish whether the copy is loose or the listing is short.
- We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request on 2026-08-23, so no parameter-level detail is published here. Every read/write classification on this page is ours, derived from names and vendor prose.
- One scope covers all four writes.
trussi.writeis all-or-nothing across commenting, quoting, scheduling and pipeline advancement. - A pipeline stage change has downstream effects. Trussi documents stage changes triggering scheduling, opening invoicing and starting a collections clock. The stage itself is reversible; what it sets off may not be.
- Whether a connector-created calendar event notifies the customer is unresolved. Trussi documents customer notifications moving with a rescheduled job, but not whether the connector path triggers them. We did not test it. Treat it as unknown rather than as a no.
trussi_run_saved_reportexecutes an account-defined artifact. Its behaviour depends on report definitions we cannot see. Review your saved reports before granting the connector.- No rate limits are published. We found no Trussi documentation of request quotas, 429 responses or retry headers for the MCP endpoint or the underlying API.
- No prompts or resources surface. The directory lists zero prompt names and no MCP app widget for this connector, and the gated endpoint prevented us from confirming what the server declares in its
initializecapabilities. - Do not confuse this with Trussi AI Chat. That is a separate, separately documented Trussi product — a Claude-powered website chat widget that qualifies inbound leads and creates them in the pipeline. It is not this connector, it does not use this endpoint, and its lead-creating behaviour is not part of the 32 tools.
Frequently asked questions
Trussi.AI is a CRM and operations platform built specifically for roofing contractors, covering projects, estimating, crew scheduling, job costing and invoicing. Its MCP server connects that account to an AI assistant. Trussi describes itself as the operating system for roofing companies, from the first knock to the final invoice, and says it was built inside Shamrock Roofing in Overland Park, Kansas.
Not through any tool Anthropic lists. Trussi's connector page says an assistant can create or update records and message customers, but none of the 32 tool names carries a send, email, text or notify verb. The closest is trussi_create_comment. Treat the customer-messaging claim as vendor copy that the published tool list does not support.
Two, and they are a real boundary. Trussi's RFC 9728 descriptor advertised trussi.read and trussi.write on 2026-08-23, and its authorization server advertises the same pair with PKCE required. You can grant reading without granting writing. What the split cannot do is separate a routine write from a consequential one — all four writes sit behind the same trussi.write grant.
Anthropic's directory lists 32 tool names as of 2026-08-23. Trussi publishes no tool list of its own anywhere we could find, so there is no second enumeration to diff the 32 against. That makes this the no-vendor-enumeration case: we cannot report a clean listing, only that nothing exists to check it with.
Four of 32: trussi_create_calendar_event, trussi_create_comment, trussi_create_quote and trussi_update_pipeline_stage. No tool name carries a delete, remove, archive, void or cancel verb. A narrow scan for risky verbs returns zero matches on this listing, which is why the writes have to be found by reading every verb rather than by pattern-matching.
Probably, but it is the one tool whose behaviour is defined by your account rather than by Trussi. It executes a report someone in your company built and saved. Trussi describes saved reports as running against live data and being rerun rather than rebuilt, which is read-shaped. We could not read its schema, so the report definition is the boundary, not the tool name.
Effectively the whole company ledger. The read tools cover customer records, project files, revenue trend, collections and accounts receivable, job-level profit analysis, marketing-channel performance, per-user activity timelines and a sales leaderboard. Trussi states access is scoped to the connected user's own permissions, so a rep and an owner see different slices.
An account admin opens Settings then Integrations in Trussi, selects AI Connector, generates a connection credential, and chooses which scopes it may read or write. You then connect from Claude using the endpoint https://my.trussi.ai/api/mcp/mcp. Trussi recommends running a read-only query first to confirm scoping before enabling writes.
Sources
- Trussi AI Connector documentation (retrieved 2026-08-23). Content recovered from the page's Next.js RSC flight payload; a plain text extraction of the same response yields 627 words and omits most of the body. · retrieved 2026-08-23
- Trussi AI Chat integration page, for the separate product (retrieved 2026-08-23) · retrieved 2026-08-23
- Trussi FAQ, pricing and platform scope (retrieved 2026-08-23) · retrieved 2026-08-23
- Trussi product documentation, pipeline stage effects and job records (retrieved 2026-08-23) · retrieved 2026-08-23
- Trussi product documentation, estimating, waste factor and DocuSign (retrieved 2026-08-23) · retrieved 2026-08-23
- Trussi product documentation, scheduling, material orders and customer notifications (retrieved 2026-08-23) · retrieved 2026-08-23
- Trussi product documentation, job costing and collections (retrieved 2026-08-23) · retrieved 2026-08-23
- Trussi product documentation, saved reports and leaderboards (retrieved 2026-08-23) · retrieved 2026-08-23
- Live OAuth posture check: anonymous initialize returned HTTP 401 with a www-authenticate header naming the resource metadata; RFC 9728 descriptor at
https://my.trussi.ai/.well-known/oauth-protected-resource; authorization server metadata athttps://my.trussi.ai/.well-known/oauth-authorization-server(2026-08-23). Control probes at sibling.well-knownpaths returned distinct 404s, so the 200s are genuine rather than a catch-all. · retrieved 2026-08-23 - Trussi
robots.txt, which allows all paths except/studio(retrieved 2026-08-23) · retrieved 2026-08-23 - Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-23 · retrieved 2026-08-23
- Trussi support — <mailto:admin@trussi.ai> · Privacy
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Analytics
- Developer
- Trussi AI
- Tools
- 32
- Domain
- my.trussi.ai
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.