Phuriwaj

Composio — MCP Connector for Jira and External Tools

Composio is an AI agent integration platform that exposes 100+ tools (Jira, GitHub, Gmail, Slack, etc.) as MCP servers, usable from Claude Code, Cowork, and custom agents.

Why / When to Use

Use when:

  • You need Jira access from Claude but can’t use Atlassian Rovo (e.g., personal account with non-business email)
  • You want Claude Code to create/update Jira tickets autonomously
  • You need a quick MCP connector without writing custom server code

Rovo restriction: Atlassian Rovo AI cannot be enabled on Jira sites registered with generic email domains (gmail.com, outlook.com, etc.). Composio bypasses this entirely.

Core Setup — Adding to Claude (Web)

  1. Go to claude.ai → Settings → Integrations
  2. Click “Add custom connector” (or “Add MCP server”)
  3. Enter the Composio MCP URL:
    https://mcp.composio.dev/[tool-name]/[your-api-key]
    
    Example for Gmail:
    https://mcp.composio.dev/gmail/[your-api-key]
    
  4. Sign up at composio.dev to get your API key

Core Setup — Claude Code (CLI)

Add to ~/.claude/settings.json or project .claude/settings.json:

{
  "mcpServers": {
    "composio-jira": {
      "command": "npx",
      "args": ["@composio/mcp", "jira"],
      "env": {
        "COMPOSIO_API_KEY": "your-api-key"
      }
    }
  }
}

Key Options / Variants

ConnectorMCP URL Pattern
Jirahttps://mcp.composio.dev/jira/[api-key]
Gmailhttps://mcp.composio.dev/gmail/[api-key]
GitHubhttps://mcp.composio.dev/github/[api-key]
Slackhttps://mcp.composio.dev/slack/[api-key]

Gotchas

  • Composio is NOT pre-listed in Claude’s connector directory — requires manual setup
  • Zapier IS pre-listed (one-click), free tier = 50 sends/month — better for casual use
  • For Jira specifically: Composio works on personal Atlassian accounts; Atlassian’s own MCP uses OAuth and also lacks the domain restriction
  • Composio acts as an intermediary — your credentials/data pass through their servers

Source

Conversations “Composio AI agent integration platform” and “Testing Gmail connector email delivery” — 2026-05-20

Updates — 2026-05-21

Microsoft To Do via Composio — Permissions Issue

Composio has Microsoft To Do connected (via Outlook, phuriwaj@outlook.com) and can list task lists and tasks. However, creating tasks fails with 401 because the Outlook connection is missing the Tasks.ReadWrite Microsoft Graph permission scope.

Fix:

  1. Go to composio.dev → Connections → Outlook
  2. Disconnect the current connection
  3. When reconnecting, look for a scope/permissions option and ensure Tasks or To Do is checked
  4. If no scope selector exists, raise with Composio support

Alternative: Microsoft To Do is also accessible via the native Microsoft 365 connector in Claude.ai (does not require Composio).

Task Management — What’s Connected via Composio

AppStatusAccount
Microsoft To Do (via Outlook)✅ Connected (read-only until Tasks.ReadWrite fixed)phuriwaj@outlook.com
TodoistAvailable but not connected via Composio (use native Claude.ai connector instead)

Source: Conversation “Composio AI agent integration platform” — 2026-05-21