mcp server
neon-jira-mcp
Local MCP server for turning meeting actions into Jira issues
Set up
Runs on your computer. Pick your agent and operating system.
Before you start
- Node.js 20 or newer
{
"mcpServers": {
"neon-jira-mcp": {
"command": "npx",
"args": [
"-y",
"neon-jira-mcp"
]
}
}
}same format Cursor, GitHub Copilot CLI, Junie, JetBrains AI Assistant, Augment (Auggie CLI), Factory Droid, Kiro, Devin CLI +12
Values in angle brackets are placeholders. Restart Claude Desktop after editing its config.Claude Desktop docs
README
synced Oct 23, 2026Neon Jira MCP
Local stdio MCP for turning meeting actions into Jira issues.
This is not a generic Jira replacement. Neon Jira MCP is the narrow bridge from meeting output to reviewable Jira work items, using the local jira CLI and the user's existing Jira auth.
Tools
draft_jira_issue: returns normalized Jira fields plus a runnablejira createcommand.create_jira_issue: creates the issue through the localjiraCLI only whenconfirmed: true.
Default labels: neoquill, meeting-action.
Install
git clone https://github.com/NKDesign30/neon-jira-mcp.git
cd neon-jira-mcp
npm install
npm run build
You can also install from GitHub:
npm install -g github:NKDesign30/neon-jira-mcp
MCP config
{
"mcpServers": {
"neon-jira": {
"command": "node",
"args": ["/absolute/path/to/neon-jira-mcp/dist/index.js"]
}
}
}
Auth
Neon Jira MCP does not store Jira credentials. It shells out to the configured local jira CLI. Run jira login outside the MCP if Jira auth is missing.
Safety
The draft tool never writes to Jira. The create tool requires confirmed: true and uses execFile, not shell execution, for the real create call.