📌Overview

Purpose: To provide a collection of packages that enable AI assistants to seamlessly interact with external tools and services using the Model Context Protocol.

Overview: MCP DevTools offers an extensible framework designed to facilitate robust integrations between AI assistants and platforms like Jira and Linear. The framework allows developers to easily create new integrations, enabling powerful data interactions through natural language commands.

Key Features:

• Seamless Integration: Connect AI assistants to various external services and tools, enhancing their capabilities.

• Extensible Framework: Simplifies the creation of new integrations, allowing for tailored functionalities with the Model Context Protocol.

• Powerful Interactions: Enables AI to access, search, and manipulate data from external services efficiently.

• Robust Integrations: Comprehensive support for Jira and Linear, offering specific functionalities for project management tasks.

• Developer-Friendly: Easy setup with thorough documentation ensures an optimal developer experience.

---

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

Package	Description	Status
@mcp-devtools/jira	Jira MCP server integration
@mcp-devtools/linear	Linear MCP server integration

🚀 Quick Start

Configuration in Cursor IDE

Jira Integration

1. Open Cursor Settings → MCP
2. Click "Add New MCP Server"
3. 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 API tokens at https://id.atlassian.com/manage-profile/security/api-tokens)

Linear Integration

1. Open Cursor Settings → MCP
2. Click "Add New MCP Server"
3. 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, interact with tools through natural language commands in Cursor.

Jira Examples:

# 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

Linear Examples:

# 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:

• Jira Package Documentation
• Linear Package Documentation

📖 Documentation

• Jira Package Documentation
• Linear Package Documentation
• Getting Started Guide
• Contributing Guidelines

🧩 Repository Structure

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
└── ...

🛠 Development

Getting Started

This repository uses pnpm workspaces for package management.

1. Install pnpm if you don't have it:

   npm install -g pnpm
   

2. Install dependencies:

   pnpm install
   

3. Build all packages:

   pnpm build
   

Development Workflow

For development with auto-rebuild:

pnpm dev

Publishing to NPM

• This repository uses automated release management with release-please and GitHub Actions.
• All packages are currently in beta (0.x.x versions) and tagged beta on npm.
• Breaking changes may occur during minor version updates in this phase.
• Install beta packages with: npm install @mcp-devtools/package-name@beta
• Version 1.0.0 will be released upon project stability.

Debugging

MCP servers communicate over stdio, making debugging challenging. Use the MCP Inspector:

pnpm inspector

This provides a URL for browser debugging tools.

🤝 Contributing

1. Fork the repository
2. Create a feature branch (git checkout -b feature/amazing-feature)
3. Commit your changes (git commit -m 'Add some amazing feature')
4. Push to the branch (git push origin feature/amazing-feature)
5. Open a Pull Request

Conventional Commits

This project uses Conventional Commits for automatic versioning and changelog generation. Use the format:

<type>[optional scope]: <description>

[optional body]

[optional footer(s)]

Common types:

• feat: A new feature
• fix: A bug fix
• docs: Documentation changes
• style: Formatting changes
• refactor: Code changes without adding features or fixing bugs
• perf: Performance improvements
• test: Adding or fixing tests
• chore: Changes to build processes or auxiliary tools

Breaking changes are marked with an exclamation mark after the type/scope and a description in the body:

feat!: redesign http-client API

BREAKING CHANGE: The http-client API has been completely redesigned.

📄 License

This project is licensed under the MIT License.

🆘 Support

• GitHub Issues: For bug reports and feature requests
• Discussions: For questions and community support

Troubleshooting

Common Issues

1. Connection Problems

   • Verify API credentials
   • Check network connectivity
   • Confirm URLs and workspace names

2. Permission Errors

   • Ensure appropriate account permissions
   • API tokens may require specific permissions

3. Command Not Found

   • If using npx, ensure connection to npm registry
   • Check package installation for local setups

Roadmap

Future plans include:

• Additional service integrations (GitHub, Confluence, etc.)
• Enhanced security features
• Custom authentication support
• Expanded querying capabilities
• Performance optimizations

Community and Support

• GitHub Issues: Bug reports and features
• Discussions: Questions and community support
• Contributing: See contributing guidelines above

We welcome feedback and contributions to improve these tools.