Connect the systems your business already runs on. Give agents the context and capabilities they need, with access scoped to the work. Host your own connections in your VPC and access your data where it already lives.
Showing 24 of 24 connections
Bring repository context, issues, and pull requests into engineering tasks.
Authorize the repositories and tool sets your agent needs. Confirm the setup for GitHub.com or your Enterprise environment.
Use issues, projects, and work history to keep delivery tasks grounded in your team’s plans.
Connect through Atlassian’s remote MCP server. Authorize your Atlassian account and confirm access to the relevant Jira Cloud projects.
Give agents access to the pages, runbooks, and team knowledge they need for a task.
Use Atlassian’s remote MCP server with permission to the relevant Confluence Cloud spaces. Keep page access aligned with the acting user.
Find relevant conversations and channel context for investigations and team coordination.
Slack MCP access requires an authorized app or supported partner integration. Workspace scopes and app approval determine available data and tools.
Connect workspace pages and knowledge so agents can find and organize useful context.
Authorize Notion MCP for the account and workspace you intend to use. Confirm the pages and actions available through its permission model.
Connect issues, projects, and comments to planning and delivery workflows.
Use Linear’s authenticated remote MCP server. Choose its read-only endpoint or read scope when the task does not need writes.
Bring GitLab project and development context into your agents’ work.
Enable and authorize the MCP server for your GitLab instance. Available tools and account requirements depend on the instance version and configuration.
Connect tasks and projects to help agents understand and coordinate ongoing work.
Authorize Asana’s MCP integration with the appropriate account and application permissions. Select the tool set that fits your workflow.
Bring design context into engineering work and connect implementation decisions to the source design.
Use Figma’s remote MCP server with the required seat, account permissions, and client approval. Figma also offers a desktop server for supported setups.
Use collaborative board content to inform research, planning, and documentation tasks.
Authorize Miro’s MCP server for the relevant team and boards. Consult its tool list for supported board operations.
Give incident investigations the error and debugging context available in Sentry.
Authorize the Sentry organization and projects needed for the task. Apply your data-handling rules to error payloads and debugging context.
Use logs, metrics, and monitoring context to help explain service behavior.
Check MCP availability for your Datadog site and authorize the required product scopes. Review which observability data may reach the selected model.
Connect dashboards and supported observability sources to agent-led investigations.
Run Grafana’s MCP server with access to your Grafana instance and approved data sources. Scope its service account and enabled tools.
Bring incident and service context into operational investigations and response preparation.
Run PagerDuty’s official MCP server with approved account access. Restrict the enabled tools and require approval for incident-changing actions.
Use the tools exposed by Elastic Agent Builder to search and analyze approved data.
Configure Elastic Agent Builder’s MCP endpoint, subscription, and access controls. Only expose the tools and datasets needed for the task.
Connect approved database and MongoDB platform tools to data exploration workflows.
Use MongoDB’s official MCP server with scoped database or Atlas credentials. Prefer read-only access when the task does not require database changes.
Expose governed data and Cortex capabilities through a Snowflake-managed MCP server.
Have an administrator configure the Snowflake-managed MCP server and the tools it exposes. Account roles and tool permissions control access.
Connect project and database context to development and investigation tasks.
Authorize Supabase MCP, scope it to the intended project, and use read-only settings where appropriate. Review enabled features before connecting sensitive data.
Use Neon’s Postgres project and query tools for development and database investigations.
Authorize Neon’s MCP server and review its database-management permissions. Use an appropriate development branch and approve schema-changing operations.
Connect Cloudflare account and platform tools to infrastructure investigation workflows.
Choose Cloudflare’s published MCP server for the capability you need. Authorize the relevant account and restrict permitted API operations.
Bring project and deployment context into troubleshooting and development tasks.
Authorize Vercel’s MCP server for the relevant account and team. Check client compatibility and project permissions before use.
Use approved billing and payment context to support finance and customer operations.
Authorize Stripe MCP with appropriate permissions. Start in test mode and require explicit policy approval for financial actions.
Bring CRM context into customer research, pipeline reviews, and sales preparation.
Configure HubSpot’s remote CRM MCP server with the required OAuth app and scopes. Available objects and actions depend on your account permissions.
Connect conversation and customer context to support research and case preparation.
Authorize the Intercom MCP server for your workspace. Confirm regional availability and the conversation and contact permissions your agent needs.
Every connection has an owner, approved tools, and a clear authorization boundary. Manage configuration through the UI, CLI, or Terraform.
Choose your workflowPick the integration and grant access through your provider’s approved process.
Assign a Capability Owner and expose only the tools and resources needed for the task.
Test an allowed action and a denied action, then attach the connection to the agent.
Bring another MCP server or build an adapter around an existing business API.
