Integrations
Connect the tools your work already lives in
138 connectors across 17 categories, from your tracker and repo to your cloud, docs and models. Plane, GitHub and Slack integrate natively today; dozens more are MCP-ready in a click; the rest are connectable now, with deeper sync rolling out.
The catalogue
Find your stack
Start with the tools teams reach for first, or open the full catalogue. Adding a new one is a line of configuration, not a release.
Native integrations (Plane, GitHub, Slack) run today. MCP-ready ones connect in a click and your agents can use them. The rest of the catalogue is connectable now, with deeper sync rolling out. The badge on each tile shows how it connects.
PlaneMemoryProjects & work-items (open-source Jira-like) to Brain OSAPI keyProject management
GitHubActionsRepos, issues, PRs (code-side management)OAuthDev & CI/CD
SlackActionsChannels, messages, issue mirroringOAuthCommunication
LinearIssues & projects (GraphQL)MCPProject management
AsanaTasks & projectsMCPProject management
ClickUpTasks, docs, goalsMCPProject management
JiraIssues & sprints (Atlassian)MCPProject management
monday.comWork OS & boardsMCPProject management
AirtableNo-code bases & tablesMCPProject management
GitLabRepos, MRs, CI pipelinesMCPDev & CI/CD
SentryError & performance trackingMCPDev & CI/CD
GrafanaDashboards & metricsMCPDev & CI/CD
VercelFrontend deploys & logsMCPHosting & infra
CloudflareDNS, CDN, WAFMCPHosting & infra
SupabasePostgres, auth, storageMCPDatabases
NeonServerless PostgresMCPDatabases
StripeMRR, customers, invoicesMCPPayments
PayPalPayments & payoutsMCPPayments
SquarePayments & POSMCPPayments
HubSpotCRM, deals, marketingMCPCRM & sales
IntercomSupport & customer conversationsMCPCRM & sales
AttioModern data-driven CRMMCPCRM & sales
NotionDocs & knowledge basesMCPProductivity & docs
CanvaDesigns & assetsMCPDesign & media
FigmaFiles & design systemMCPDesign & media
WebflowSites & CMSMCPDesign & media
WixSites & CMSMCPDesign & media
ZapierNo-code automationsMCPAutomation
How it works
Connect, remember, act
An integration isn't a logo on a page. In TaskForce a tool earns its place in three steps, and each one is explicit about where it stands.
Connect
Connector availability
A connector can be configured and connected. OAuth is available for supported providers; the rest use encrypted credentials you provide.
Remember
Ingestion into Memory
A connected tool's data flows into the Brain OS decision graph, so runs can start from the context your team has already built. Live for Plane today, rolling out per tool.
Act
Action via MCP
Agents can use the tools you connect. Anything not explicitly read-only is treated as a write - the agent proposes it, and it runs only after a human approves it.
Illustrative - one shared memory. Native integrations feed runs today; the wider catalogue connects now, deeper sync rolling out.
Integrations brings in the context.
Memory preserves the reasoning.
Learn moreOrchestration decides what happens next.
Learn moreWe mark integrations Beta on purpose: connecting is here today, deep sync and MCP actions are rolling out. Follow it on the public roadmap.
Security & permissions
Your credentials, your scopes, your control
Connecting real systems to AI raises one question first: what can an agent actually do with that access? The short version is here. The full one lives in the Trust Center.
OAuth where supported
GitHub and Slack connect over OAuth; the rest use tokens or keys you provide.
Encrypted at rest
Every credential is stored encrypted, never in the codebase.
Bounded by capability
Agents can only invoke what a connector exposes - and only what the credentials and scopes you configure permit.
Out of the prompt
Connector secrets are used server-side to reach the tool; they're never placed in a model prompt.
Your tools become context and capabilities for every run
Connect your stack. Give every run the context it needs. Let agents act through the tools you already use, with humans still in control.