# Trellus AI: MCP server status, API access gate and what it does > A hybrid AI calling platform: a parallel dialer embedded in Salesloft/Outreach/HubSpot with real-time AI... No MCP found, Gate unknown. Checked 2026-08-24. *Markdown twin of the HTML page at the same path. Same content, no navigation, no styling, no scripts. Links below point at other twins. Site map for machines: [llms.txt](../llms.txt). The whole dataset: [directory.json](../data/directory.json).* --- [Directory](../index.md) / [AI SDRs](../categories/ai-sdr-agents.md) / Trellus AI # Trellus AI [No MCP found](../mcp/none-found.md) [Gate unknown](../gates/unknown.md) [AI SDRs](../categories/ai-sdr-agents.md) RESEARCHED Checked 2026-08-24 > **RESEARCHED** Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 0. Vendor: [https://trellus.ai](https://trellus.ai) · entry id 04-trellus-ai · source 04-ai-sdr-agents.md line 429 **What it does** A hybrid AI calling platform: a parallel dialer embedded in Salesloft/Outreach/HubSpot with real-time AI coaching for live reps, plus separate fully-autonomous voice agents for inbound call handling, appointment setting, and FAQ response. **AI features, separated from automation with an AI label on it** Important and explicit distinction confirmed on the vendor's own site: outbound cold-calling is NOT autonomous - Trellus augments a human dialer with live coaching and parallel-line dialing; only inbound call handling uses fully autonomous voice agents. This is one of the more honest vendor self-descriptions found in this pass. **RevOps role** Calling/dialing augmentation layer that sits inside an existing sales-engagement platform rather than replacing one. **MCP server** - **Status bucket**: No MCP found - **Auth**: n/a - **Parsed URLs**: 0 found in the mcp_url field No server was found at the time of the check. That is a statement about the search, not a promise that none exists. The status was established on 2026-08-24 and has not been re-fetched since. mcp_status, verbatim from the file: none-found The mcp_url field is empty on this entry. 21 of 293 entries are. **Access gate** - **Gate bucket**: Gate unknown - **Can a solo operator reach it**: Not established api_gate, verbatim from the file: unknown - no pricing/API docs found on this pass 83 of 293 entries carry an unknown gate. Unknown is a legal answer and it ships as unknown rather than as a guess. **API documentation** No documentation URL recorded. 263 of 293 entries are in the same position. Blank is legal and it is published as blank. **GitHub health** Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build. The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale. **Jobs it can do** - [Place an outbound call](../jobs/place-outbound-call.md) - [Book a meeting](../jobs/book-a-meeting.md) - [Answer an inbound chat or call](../jobs/answer-inbound-chat.md) - [Score rep performance](../jobs/score-rep-performance.md) A job tag means the vendor says the tool does this. It is not a test result, not proof the capability is reachable through the tool's MCP server, and not proof it is available on the gate this entry records. Tagged by machine-pass on 2026-08-25 against the closed 55 job vocabulary. 271 of 293 entries carry at least one tag; 827 tags are assigned in total. **Sources** - [https://trellus.ai](https://trellus.ai) 1 source URL. Thin. The standing rule is at least two independent sources with the vendor's own site unable to be both of them, and this entry does not meet it. 32 entries are in the same state and they are listed on the methodology page. Raw sources field, verbatim: https://trellus.ai **Notes, verbatim from the file** Worth citing specifically as a counterexample to the category's hype: Trellus's own marketing explicitly says it does not autonomously cold-call, which is a useful contrast against vendors that imply full autonomy for the same job. **Provenance** - **Entry id**: 04-trellus-ai - **Source file**: 04-ai-sdr-agents.md - **Source line**: 429 - **Tier**: RESEARCHED - **last_checked**: 2026-08-24 - **Data baked**: 2026-08-25 Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the [methodology page](../methodology.md).