by dxheroes
Access and interact with Jira and Linear tickets directly in conversations—no context switching to Jira ticketing softwa
Connects AI assistants to Jira and Linear issue tracking systems, allowing you to query and interact with tickets without leaving your conversation.
You can install Jira & Linear in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
Jira & Linear is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Share your MCP server with the developer community
Useful MCP listing: Jira & Linear is the kind of server we cite when onboarding engineers to host + tool permissions.
Jira & Linear has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Jira & Linear is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Jira & Linear is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
Jira & Linear reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Jira & Linear has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
We wired Jira & Linear into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
Jira & Linear reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
According to our notes, Jira & Linear benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
Useful MCP listing: Jira & Linear is the kind of server we cite when onboarding engineers to host + tool permissions.
showing 1-10 of 30
MCP (Model Context Protocol) DevTools is a collection of packages that enable AI assistants to interact with external tools and services through the Model Context Protocol.
Note: This project is currently in beta (0.x.x versions). APIs may change between minor versions during the beta phase.
| Package | Description | Status |
|---|---|---|
| @mcp-devtools/jira | Jira MCP server integration |  |
| @mcp-devtools/linear | Linear MCP server integration |  |
Jiracommandenv JIRA_URL=https://[YOUR_WORKSPACE].atlassian.net JIRA_API_MAIL=[YOUR_EMAIL] JIRA_API_KEY=[YOUR_API_KEY] npx -y @mcp-devtools/jiraRequired Environment Variables:
JIRA_URL: Your Jira instance URL (e.g.,https://your-company.atlassian.net)JIRA_API_MAIL: Your Atlassian account emailJIRA_API_KEY: Your Atlassian API key (Create one here)
Linearcommandenv LINEAR_API_KEY=[YOUR_API_KEY] npx -y @mcp-devtools/linearRequired Environment Variables:
LINEAR_API_KEY: Your Linear API key (Create one in Linear app: Settings → API → Create Key)
Once configured, you can interact with tools through natural language commands in Cursor.
# Fetch a specific ticket
get ticket SCRUM-123
# Search for tickets
execute jql "project = SCRUM AND status = 'In Progress'"
# Get ticket details
read ticket SCRUM-123
# Create a new ticket
create ticket project=SCRUM summary="Fix login bug" description="Users can't log in" issuetype=Bug
# Get a specific issue
get_issue SS-33
# Search for issues
search_issues "priority is high" with limit 5
# Create a new issue
create_issue for team "eng" titled "Fix API response format" with description "The API is returning incorrect data format" and priority 1
# List teams
list_teams
For a complete list of available commands, refer to the package documentation:
mcp-devtools/
├── core/ # Infrastructure and utility packages
│ ├── typescript-config/ # Shared TypeScript configuration
│ └── http-client/ # HTTP client utilities
│
├── packages/ # Functional MCP server packages
│ ├── jira/ # Jira integration MCP server
│ │ └── README.md # Package documentation
│ └── linear/ # Linear integration MCP server
│ └── README.md # Package documentation
│
└── ...
# Install dependencies
pnpm install
# Build all packages
pnpm build
# Development with auto-rebuild
pnpm dev
Contributions are welcome! Please check our Contributing Guidelines for details.
This project is licensed under the MIT License - see the LICENSE file for details.
mcp-devtools/
├── core/ # Infrastructure and utility packages
│ ├── typescript-config/ # Shared TypeScript configuration
│ └── http-client/ # HTTP client utilities
│
├── packages/ # Functional MCP server packages
│ ├── jira/ # Jira integration MCP server
│ └── linear/ # Linear integration MCP server
├── package.json # Root package configuration
└── pnpm-workspace.yaml # Workspace configuration
This repository uses pnpm workspaces for package management. To get started:
Install pnpm if you don't have it:
npm install -g pnpm
Install dependencies:
pnpm install
Build all packages:
pnpm build
For development with auto-rebuild:
pnpm dev
This repository is set up with automated release management using release-please and GitHub Actions for publishing packages to npmjs.org.
All published packages are currently in beta status (0.x.x versions) and use the beta npm tag. During this phase:
npm install @mcp-devtools/package-name@betaSince MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a workspace script:
pnpm inspector
The Inspector will provide a URL to access debugging tools in your browser.
git checkout -b feature/amazing-feature)git commit -m 'Add some amazing feature')git push origin feature/amazing-feature)This project uses Conventional Commits to automate versioning and changelog generation. Please format your commit messages following this pattern:
<type>[optional scope]: <description>
[optional body]
[optional footer(s)]
Types:
feat: A new featurefix: A bug fixdocs: Documentation changesstyle: Changes that don't affect the code's meaning (formatting, etc.)refactor: Code changes that neither fix bugs nor add featuresperf: Performance improvementstest: Adding or fixing testschore: Changes to the build process or auxiliary toolsExamples:
feat(jira): add comment creation endpoint
fix(http-client): resolve timeout issue
docs: update README with new setup instructions
Breaking changes should be indicated by adding an exclamation mark after the type/scope and describing the breaking change in the body of the commit message:
feat!: redesign http-client API
BREAKING CHANGE: The http-client API has been completely redesigned to improve usability.
This project is licensed under the MIT License - see the LICENSE file for details.
Connection Problems
Permission Errors
Command Not Found
For more troubleshooting help, open an issue on our GitHub repository.
Future development plans for MCP DevTools include:
We welcome feedback and contributions from the community to help improve these tools.
Prerequisites
Time Estimate
15-60 minutes depending on server complexity
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
Compatibility
✓ Use when
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid when
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.