Jira-mini-mcp Server

Jira-mini-mcp is an MCP integration. Minimal Jira Cloud MCP server: broad reads, a narrow 3-tool write surface, optional read-only mode.

Packages and local setup

The published pypi package is jira-mini-mcp, version 1.3.0. Its declared MCP transport is stdio.

The package declares JIRA_BASE_URL (required): Your Jira Cloud site, e.g. https://example.atlassian.net; JIRA_AUTH_METHOD: api_token (default) or oauth; oauth needs an OAuth 2.0 (3LO) app and a one-time jira-mini-mcp login; JIRA_EMAIL: The email your Jira API token belongs to (JIRA_AUTH_METHOD=api_token); JIRA_API_TOKEN: A Jira Cloud API token (JIRA_AUTH_METHOD=api_token); JIRA_OAUTH_CLIENT_ID: Client ID of your OAuth 2.0 (3LO) app (JIRA_AUTH_METHOD=oauth); JIRA_OAUTH_CLIENT_SECRET: Secret of your OAuth 2.0 (3LO) app (JIRA_AUTH_METHOD=oauth); READ_ONLY_MODE: Set to true, 1, or on to register only the six read tools and withhold the three write tools; STRUCTURED_OUTPUT: Set to true, 1, or on to also send structuredContent and an outputSchema; by default each result is sent once, in content; DISABLE_STRUCTURED_OUTPUT: With STRUCTURED_OUTPUT=true, comma-separated tool names that still return content only, without structuredContent.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository. This profile uses version 1.3.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related productivity & project management MCP servers for tools that cover the same kind of work.