MCP DevTools
[](https://github.com/modelcontextprotocol/mcp-devtools)
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.
Highlights
- **Seamless Integration**: Connect AI assistants to external services and tools
- **Extensible Framework**: Easily create new integrations with the Model Context Protocol
- **Powerful Interactions**: Enable AI to access and manipulate data from external services
- **Robust Integrations**: Comprehensive functionality for Jira and Linear
- **Developer-Friendly**: Simple setup with detailed documentation for the best developer experience
**Note**: This project is currently in beta (0.x.x versions). APIs may change between minor versions during the beta phase.
Available Packages
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
[object Object] | [object Object] | [object Object] |
Quick Start
Configuration in Cursor IDE
Jira Integration
- Open Cursor Settings MCP
- Click "Add New MCP Server"
- Fill in the following details: - **Name**: `Jira` - **Type**: `command` - **Command**: `env JIRA_URL=https://[YOUR_WORKSPACE].atlassian.net JIRA_API_MAIL=[YOUR_EMAIL] JIRA_API_KEY=[YOUR_API_KEY] npx -y @mcp-devtools/jira`
**Required Environment Variables**: - `JIRA_URL`: Your Jira instance URL (e.g., `https://your-company.atlassian.net`) - `JIRA_API_MAIL`: Your Atlassian account email - `JIRA_API_KEY`: Your Atlassian API key ([Create one here](https://id.atlassian.com/manage-profile/security/api-tokens))
Linear Integration
- Open Cursor Settings MCP
- Click "Add New MCP Server"
- Fill in the following details: - **Name**: `Linear` - **Type**: `command` - **Command**: `env LINEAR_API_KEY=[YOUR_API_KEY] npx -y @mcp-devtools/linear`
**Required Environment Variables**: - `LINEAR_API_KEY`: Your Linear API key (Create one in Linear app: Settings API Create Key)
Using Tools
Once configured, you can interact with tools through natural language commands in Cursor.
Jira Examples:
Linear Examples:
For a complete list of available commands, refer to the package documentation:
- [Jira Package Documentation](./packages/jira/README.md)
- [Linear Package Documentation](./packages/linear/README.md)
Documentation
- [Jira Package Documentation](./packages/jira/README.md)
- [Linear Package Documentation](./packages/linear/README.md)
- [Getting Started Guide](./docs/getting-started.md)
- [Contributing Guidelines](./CONTRIBUTING.md)
Repository Structure
Development
Contributing
Contributions are welcome! Please check our [Contributing Guidelines](./CONTRIBUTING.md) for details.
License
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
Support
- **GitHub Issues**: For bug reports and feature requests
- **Discussions**: For questions and community support
Project Structure
Development
Getting Started
This repository uses pnpm workspaces for package management. To get started:
- Install pnpm if you don't have it: ```bash npm install -g pnpm ```
- Install dependencies: ```bash pnpm install ```
- Build all packages: ```bash pnpm build ```
Development Workflow
For development with auto-rebuild:
Publishing to NPM
This repository is set up with automated release management using release-please and GitHub Actions for publishing packages to npmjs.org.
Beta Status
All published packages are currently in beta status (0.x.x versions) and use the `beta` npm tag. During this phase:
- Breaking changes may occur in minor version updates
- Install the packages using: `npm install @mcp-devtools/package-name@beta`
- When the project reaches stability, we will release version 1.0.0
Debugging
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a workspace script:
The Inspector will provide a URL to access debugging tools in your browser.
Contributing
- Fork the repository
- Create a feature branch (`git checkout -b feature/amazing-feature`)
- Commit your changes (`git commit -m 'Add some amazing feature'`)
- Push to the branch (`git push origin feature/amazing-feature`)
- Open a Pull Request
Conventional Commits
This project uses [Conventional Commits](https://www.conventionalcommits.org/) to automate versioning and changelog generation. Please format your commit messages following this pattern:
Types:
- `feat`: A new feature
- `fix`: A bug fix
- `docs`: Documentation changes
- `style`: Changes that don't affect the code's meaning (formatting, etc.)
- `refactor`: Code changes that neither fix bugs nor add features
- `perf`: Performance improvements
- `test`: Adding or fixing tests
- `chore`: Changes to the build process or auxiliary tools
Examples:
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:
License
This project is licensed under the MIT License - see the [LICENSE](LICENSE) file for details.
Troubleshooting
Common Issues
- **Connection Problems** - Ensure your API credentials are correct - Check network connectivity to your service instances - Verify URLs and workspace names
- **Permission Errors** - Ensure your accounts have appropriate permissions for the actions you're attempting - API tokens may need specific permissions enabled in your account settings
- **Command Not Found** - If using npx, ensure you're connected to npm registry - For local installations, check that your package installation was successful
For more troubleshooting help, open an issue on our GitHub repository.
Roadmap
Future development plans for MCP DevTools include:
- Additional service integrations (GitHub, Confluence, etc.)
- Enhanced security features
- Support for custom authentication methods
- Expanded querying capabilities
- Performance optimizations
Community and Support
- **GitHub Issues**: For bug reports and feature requests
- **Discussions**: For questions and community support
- **Contributing**: See our contributing guidelines above
We welcome feedback and contributions from the community to help improve these tools.