"Jira Software" matching MCP servers:

Enables natural-language interaction with self-hosted Jira and Bitbucket, providing tools for ticket management, pull requests, code review, and git context.

Jira CLI & MCP Server — dual-mode Go binary for Jira Cloud with 9 tools, 4 prompts, permission introspection, and dev-status API.

Enforces structured, evidence-guided software engineering tasks with cognitive actions (investigate, plan, verify, remember) and persistent state for LLM-based coding agents.

Enables governed multi-agent software factory operations through eight typed, audited tools for Sprint planning, submission, decisions, inspection, cancellation, and resumption.

Keeps Jira Cloud, Jira Server, Linear or its own built-in tracker (plus Confluence pages) in one local SQLite file. Its MCP tools answer from that file: read-only SQL, full-text search across issues, comments and wiki pages, issue detail, sprint and retro reads.

Haft is an MCP server that enforces engineering discipline for AI-assisted software delivery, providing tools for problem framing, decision contracts, and commission-based execution harnesses.

Local-first dev memory: indexes Git commits, PRs, Jira/Linear tickets, Confluence docs, Slack threads, and Calendar events into a local SQLite/FTS5/ONNX index, and exposes them as MCP tools so Claude Code, Cursor, and Codex can search and cite your past work.

Self-hostable, markdown-native team wiki with a built-in MCP server: agents search, read, and write your wiki pages (ranked Postgres full-text + semantic search, backlink traversal). Plus Atlas, which auto-generates a cited, coverage-checked wiki from your git repos and Jira.

An MCP server that provides Claude Code with 99 methodology skills, seed patterns, decision logging, and memory tools to improve software development decisions. It acts as a cognitive scaffold layer, enabling better working methods rather than just additional data.

Gives AI coding agents persistent, structured memory of a software project across sessions — goals, architecture, tech stack, decisions, and progress — stored locally in an embedded SQLite vault. Agents recall and update that context automatically through MCP tools whenever they open the project.