Atlassian Jira MCP
aashariConnects to Jira for issue lookup, JQL search, and comments
Connects to Jira for issue lookup, JQL search, and comments On the other side: reads and writes linear issues, projects, and cycles through the graphql api
Follow the tracker your team already opens. Choosing fresh: Linear.
Jira is where enterprise process lives; Linear is where small teams actually work. The MCP choice mostly follows the tool your team already opens: an agent that files work into the wrong tracker is worse than no integration, because nobody will see the ticket.
| Option | Install | Source | Link |
|---|---|---|---|
| Atlassian Jira MCP | npx -y @aashari/mcp-server-atlassian-jira | Community | Repository ↗ |
| Linear MCP | npx -y @tacticlaunch/mcp-linear | Community | Repository ↗ |
Your organisation runs Jira and the workflow is defined by fields and transitions.
The team is small, the cycle is weekly, and issues are created in seconds.
A project going archived, or a maintainer changing the install path, flips this comparison faster than any feature release. Both entries are re-checked weekly, and the date above tells you how much to trust the details.
Gives an agent scoped read, write, and search access to directories you explicitly allow
Read-only access to a repository's history: status, diffs, commit logs, and blame
Reads content types and entries and can create drafts in a Contentful space
Searches Gmail and reads threads, with optional draft creation
Serves version-specific documentation for thousands of libraries, so an agent stops writing code against an API that changed two releases ago
Runs read-only SQL against a Postgres database and returns the schema alongside results, which is what makes it usable without pasting table definitions into the prompt