Aleph
Query live FP&A data, build reports and update dashboards from your AI assistant.
Query a Trussi roofing CRM — pipeline, job costing, collections — and create quotes, comments and calendar events.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Trussi AI MCP server connects a Trussi roofing CRM — a contractor platform covering projects, estimating, crew scheduling, job costing and invoicing — to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists 32 tools that read the pipeline, financials and schedule, and four that write. Sign-in is OAuth 2.0 with PKCE and two scopes.
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
sitemap.xml, every product and integration page, the FAQ, and a llms.txt probe that returned the site's soft-404 shell. No vendor enumeration exists to diff against, in either direction.trussi.write is all-or-nothing across commenting, quoting, scheduling and pipeline advancement.trussi_run_saved_report executes an account-defined artifact. Its behaviour depends on report definitions we cannot see. Review your saved reports before granting the connector.initialize capabilities.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.
https://my.trussi.ai/.well-known/oauth-protected-resource; authorization server metadata at https://my.trussi.ai/.well-known/oauth-authorization-server (2026-08-23). Control probes at sibling .well-known paths returned distinct 404s, so the 200s are genuine rather than a catch-all. · retrieved 2026-08-23robots.txt, which allows all paths except /studio (retrieved 2026-08-23) · retrieved 2026-08-23Connect Trussi AI once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.