Integrations
TaskGate comes with 100+ integrations. Every connection is an external tool that agents can only reach through the gate.
The catalogue
Pick a tool on Connections. The catalogue covers developer tools, communication, documents, CRM and support, payments and finance, data, observability, marketing and more — among them:
GitHub, GitLab, Linear, Jira, Asana, Sentry, Figma, Slack, Microsoft Teams, Zoom, Notion, Confluence, Google Drive, SharePoint / OneDrive, Airtable, HubSpot, Salesforce, Zendesk, Intercom, Stripe, Shopify, QuickBooks, Snowflake, BigQuery, Datadog, PagerDuty, Gmail, Outlook and many more.
How a connection is made
- Sign in. Many integrations connect with just a sign-in — choose Sign in with … and approve access in the tool. No keys to paste.
- Token or key. Others take a token or API key, and the catalogue says where to find it.
- Your own systems. Add any Model Context Protocol (MCP) server over HTTP, or a plain REST endpoint as an HTTP API connection, where you describe its tools.
For each connection TaskGate sets the endpoint, the hosts it may reach and how tightly it's brokered. Outbound calls go only to the hosts on the connection's egress allow-list.
Tools are admitted, then pinned
Every tool version is admitted explicitly, pinned by digest, and re-reviewed when its descriptor drifts. An agent calls only the pinned version. A tool that has changed since it was admitted is refused until it is reviewed again. The Tools page lists the admitted-tool catalogue.
Model providers
On Models, link an OpenAI, Anthropic or Azure key so agents can reach a model through the TaskGate gateway. Model routes can be held to the provider regions you allow.