Connect your work tools to every AI workspace, safely.

Install trusted MCP kits for Jira and Confluence, run them locally or through a governed gateway.

Use Jira and Confluence from supported AI clients today, then extend the same governed gateway into communication channels.

Explore Connectors ↗Try the Playground

Read-only by defaultPer-user identityAction approvalsAuditable

Work itemPROJ-2481

Connected

Staged rollout is ready, but the owner is still unassigned.

Safe next stepDraft owner update

Jira issue+Confluence decision→ MCPoppins

Governed resultDrafted from both connected tools

Approval-ready Jira update

PROJ-2481 · Add rollout owner and link decision RFC-14. No write has happened yet.

Sources: #launch-ops thread · Confluence RFC-14 · Jira PROJ-2481

Jira liveConfluence citedR2 approval

Target workspacesRun this governed flow in Teams and your IDE

Same policy →

Available connectorsJira · 17 toolsConfluence · 13 toolsGateway · 20 HTTP toolsRead-only by default

Intelligent gateway

22 intent patterns. 4 cross-system workflows.

The gateway chains Jira and Confluence tools, remembers conversation context, and formats responses for each channel.

Capabilities✓ Intent routing✓ Conversation memory✓ Audit trail✓ Action approvals✓ Channel formatting✓ Proactive insights✓ Graceful degradation✓ Suggested actions✓ Cross-system linking

API endpoints/health/tools/chat/audit/conversation/:userId/approvals/webhooks/teams/webhooks/slack

Platforms

Meet teams where they already work.

Supported clients run the kits today. Planned channels use the existing gateway and adapter guides.

Supported✓ Kiro IDE✓ VS Code✓ GitLab Duo✓ Claude Desktop✓ Cursor✓ Windsurf

PlannedWebsite ChatMicrosoft TeamsSlackWhatsAppDiscordTelegram

The promise

Find the work. Read the docs. Ask before posting.

Every package starts read-only, keeps credentials outside the code and makes write approval explicit.