A Model Context Protocol (MCP) server that provides Jira integration tools, built with mcp-framework.
# Install dependencies
npm install
# Build the project
npm run buildFor local development with ROO CLINE, update the args to contain the path to dist/index.js of this repo on your machine. Make sure to npm run build beforehand:
{
"mcpServers": {
"braindone": {
"command": "node",
"args":["/home/user/braindone-mcp/dist/index.js"]
}
}
}Add this configuration to your Claude Desktop config file, updating the path to match your local setup:
{
"mcpServers": {
"braindone": {
"command": "node",
"args": ["/path/to/your/braindone-mcp/dist/index.js"]
}
}
}Config file locations:
- MacOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%/Claude/claude_desktop_config.json
This MCP server provides the following Jira integration tools:
Creates new Jira tickets with customizable fields:
- Ticket name/summary
- Description
- Assignee ID
Updates existing Jira tickets with:
- Summary
- Description
- Assignee
- Status
Retrieves tickets from a specified Jira project with:
- Summary
- Status
- Assignee
- Description
Fetches Jira users with pagination support:
- Configurable start index
- Adjustable results per page
braindone-mcp/
├── src/
│ ├── tools/
│ │ ├── CreateTicketTool.ts
│ │ ├── UpdateTicketTool.ts
│ │ ├── GetTicketsTool.ts
│ │ └── GetAllUsers.ts
│ ├── clients/
│ │ └── jira.client.js
│ └── index.ts
├── package.json
└── tsconfig.json
- Make your changes to the tools
- Run
npm run buildto compile - Restart the client, or restart the server inside of Roo-Cline's MCP server section
The Jira integration uses the following default settings:
- Project Key: MFLP
- Issue Type: Task
These can be modified in the CreateTicketTool configuration.