Sync Jira and Linear

Keep Jira and Linear in sync so teams can use whichever tracker they prefer. New issues created in either tool appear automatically in the other.

Prerequisites

• Jira API token (generate here)
• Linear API key (Settings → API)
• WCP running

1. Register Connections

# Jira
curl -X POST http://localhost:8000/api/connections \
  -H "Content-Type: application/json" \
  -d '{
    "name": "jira",
    "command": "npx",
    "args": ["-y", "@anthropic/mcp-server-jira"],
    "env": {
      "JIRA_URL": "https://yourteam.atlassian.net",
      "JIRA_EMAIL": "you@company.com",
      "JIRA_API_TOKEN": "ATATT3x..."
    }
  }'

# Linear
curl -X POST http://localhost:8000/api/connections \
  -H "Content-Type: application/json" \
  -d '{
    "name": "linear",
    "command": "npx",
    "args": ["-y", "@anthropic/mcp-server-linear"],
    "env": { "LINEAR_API_KEY": "lin_api_..." }
  }'

2. Scan and Verify

curl -X POST http://localhost:8000/api/capabilities/scan
curl http://localhost:8000/api/capabilities/syncable-pairs

You should see a pair with capability tasks or issues linking both apps.

3. Run Sync

curl -X POST http://localhost:8000/api/sync/run/await

4. Conflict Strategy

For issue trackers being migrated, source_wins is recommended with the authoritative tool as source:

curl -X PUT http://localhost:8000/api/conflicts/strategy \
  -H "Content-Type: application/json" \
  -d '{"strategy": "source_wins"}'

Tips

• Run a one-time bulk sync first, then switch to scheduled syncs
• Use the Links API to verify which issues are paired: curl http://localhost:8000/api/links
• Check logs for per-item results: curl http://localhost:8000/api/logs?limit=20