Integrations
What Stride connects to
10 connections spanning source control, communication, migration, AI assistants and coding agents, and APIs. Each card states the direction and depth of the connection, including Jira Cloud, which is two-way only for the length of a migration window rather than an ongoing sync.
stride.page/plan/issues
- GitHubSource control · GitHub → StrideLink pull requests to stories and surface merge status through the Stride GitHub App.View setup
- GitLabSource control · GitLab → StrideLink merge requests to issues and surface pipeline status for connected GitLab projects.View setup
- SlackCommunication · Stride → SlackSend selected mentions, story changes, and sprint events to a connected Slack channel.View setup
- Jira CloudProject management · 30-day two-wayImport a Jira Cloud project and keep supported epics, stories, subtasks, sprints, and comments synchronized both ways during the 30-day migration window. After that, Stride becomes the system of record.View setup
- ClaudeAI assistant · MCP read/writeRead and update the same Stride delivery record from Claude on the web, desktop and mobile, and in Cowork, through Model Context Protocol (MCP).View setup
- ChatGPTAI assistant · MCP read/writeRead and update the same Stride delivery record from ChatGPT, with the Stride AI plugin from its plugin directory, through Model Context Protocol (MCP).View setup
- Claude CodeAI coding agent · MCP read/writeRead and update the same Stride delivery record from Claude Code through Model Context Protocol (MCP).View setup
- OpenAI CodexAI coding agent · MCP read/writeRead and update the same Stride delivery record from Codex through Model Context Protocol (MCP).View setup
- CursorAI coding agent · MCP read/writeRead and update the same Stride delivery record from Cursor through Model Context Protocol (MCP).View setup
- Webhooks & REST APIBuild your own · REST + webhooksUse the public REST API and HMAC-signed webhooks to connect systems outside the supported catalog.View setup