Enterpret fork of @aashari/mcp-server-atlassian-jira adding an ATLASSIAN_OAUTH_BEARER mode (3LO bearer + cloudId discovery) so a Nango-supplied access token plugs straight into Jira Cloud REST. Used b
{ "mcpServers": { "enterpret-jira-mcp": { "command": "npx", "args": [ "-y", "@enterpret/[email protected]" ] } }}Power your agent
The publisher's own command. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
npx -y @enterpret/[email protected]Claude Code has no install link for a local command. Copy the command below and run it in a terminal.
claude mcp add enterpret-jira-mcp -- npx -y @enterpret/jira-mcp@0.1.0Run in a terminal.
{ "mcpServers": { "enterpret-jira-mcp": { "command": "npx", "args": [ "-y", "@enterpret/[email protected]" ] } }}claude_desktop_config.json
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchOverview
Enterpret fork of @aashari/mcp-server-atlassian-jira adding an ATLASSIAN_OAUTH_BEARER mode (3LO bearer + cloudId discovery) so a Nango-supplied access token plugs straight into Jira Cloud REST. Used by the Orbit/wisdom-v2 jira_mcp bring_token connector.
Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
No required environment variable is listed on this record.
@enterpret/jira runs locally over stdio.
Last checked 2026-11-16. Enterpret fork of @aashari/mcp-server-atlassian-jira adding an ATLASSIAN_OAUTH_BEARER mode (3LO bearer + cloudId discovery) so a Nango-supplied access token plugs straight into Jira Cloud REST. Used by the Orbit/wisdom-v2 jira_mcp bring_token connector.
From the publisher
README is not crawled yet. Open the repository
Enterpret fork of @aashari/mcp-server-atlassian-jira adding an ATLASSIAN_OAUTH_BEARER mode (3LO bearer + cloudId discovery) so a Nango-supplied access token plugs straight into Jira Cloud REST. Used by the Orbit/wisdom-v2 jira_mcp bring_token connector.