Integrations

Integrations

What Cabinet connects to. Grouped by category, with status pills.

AI providers

Cabinet is bring-your-own-AI. Connect the providers you already pay for; Cabinet routes your agents' calls. There's no Cabinet middleman, no inference markup.

ProviderBest forStatus
Anthropic ClaudeLong careful writing, strong reasoninglive
OpenAI GPTFast triage, cheap routing, strong tool uselive
Google GeminiLong-context research, low cost per tokenlive
xAI GrokFresh news access, lighter taskslive
Local — Ollama / LM StudioOffline, private, no API billlive
OpenRouterOne key, many providers, automatic fallbacksoon
Together / Groq / ReplicateSpecialty model hostssoon

→ Read BYOAI for routing, fallbacks, budgets.

Tool servers (MCP)

Model Context Protocol servers add tool surfaces to your agents. Cabinet connects via stdio or HTTP transport.

MCP serverWhat it gives agentsStatus
filesystemRead/write inside a folder (built-in)live
chrome-devtoolsDrive a browser, take screenshotslive
githubIssues, PRs, file ops, searchlive
gws (Google Workspace)Sheets / Drive / Gmail / Calendar via service accountlive
playwrightHeavier browser automationlive
figmaRead components and designslive
stripeCustomer / subscription / invoice opslive

Add an MCP server to a cabinet by writing one file at .mcp/servers.json — Cabinet picks it up on next boot.

Connectors (live messaging surfaces)

Push notifications, approve from your phone, trigger tasks from a DM.

ConnectorWhat it doesStatus
SlackTrigger tasks, get approvals, receive briefingssoon
TelegramDM your agents. Approve from the lock screen.soon
DiscordChannel-driven approvals + briefingssoon
Email (IMAP/SMTP)Inbox triage, draft replies, follow-upssoon
SMS (Twilio)One-line approvals on the roadsoon
iMessage (BlueBubbles)Mac-only iMessage bridgelater

Each connector ships as an MCP server + a Cabinet plugin. Authorization is OAuth where possible, scoped tokens where not.

File sources

Beyond editing files in the cabinet folder, Cabinet can read your data where it already lives.

SourceHow it's wiredStatus
Symlinks ("Load Knowledge")Right-click → Load Knowledge → pick a folderlive
Linked git reposFolder with .repo.yamllive
Embedded appsFolder with index.htmllive
Google Workspace pagesMarkdown page with google: frontmatterlive
Office docs.docx / .xlsx / .pptx render inline read-onlylive
Notion importRead-only import from a Notion workspacesoon
Obsidian vault adoptionOpen an Obsidian vault as a cabinet (zero conversion)live

Skill marketplaces

Where agents pick up new instructions.

MarketplaceWhat's thereStatus
skills.shPublic registry of agent skills, with security scanslive
GitHub URLsInstall from any public repo with a SKILL.md at the rootlive
BundledCommon skills (research synthesis, code review, doc edits) ship with the applive

→ Read Skills for how a SKILL.md is structured and the security model.

Template marketplaces

Where you find pre-built cabinets.

MarketplaceWhat's thereStatus
cabinets.shPublic registry of plug-and-play cabinets — full AI teams in one folderlive
GitHub URLsInstall any public repo with a .cabinet at the rootlive
Local foldersnpx cabinets add ./my-template works on local paths toolive

Smart home & devices

IntegrationWhat it doesStatus
Home AssistantCabinet as the brain on top of your HA setuplater
Voice (TTS / Whisper)Voice in / voice out for agent chatssoon

Read on

  • BYOAI — provider routing, fallbacks, local-only mode.
  • Skills — the security model around installable instructions.
  • Templates — pre-built cabinets you install in one command.
  • Reference → Manifest schema — where provider routing config lives.