mcp-server-atlassian-jira
An MCP server for interacting with Atlassian Jira, enabling issue management, attachments, and other operations via natural language.
README
mcp-server-atlassian-jira (UFC fork)
Private UFC fork of
aashari/mcp-server-atlassian-jira
(forked at upstream commit aab8b7f2, one commit past v3.3.0), carrying:
- Binary response corruption fix - upstream's
fetchAtlassian()(src/utils/transport.util.ts) read every response body viaresponse.text(); for binary endpoints (attachment content, thumbnails, exports) that is a lossy, irreversible UTF-8 decode. Fixed: non-JSON/text/XML bodies are read viaarrayBuffer()and returned as{ __binary: true, contentType, byteLength, base64 }. Covered by regression tests insrc/utils/transport.util.test.ts. - Ported upstream community PR #173 (author
cedral) -jira_attach(multipart upload) andjira_get_attachment(byte-exact download to a local file). DOTENV_CONFIG_PATHwith~-expansion insrc/utils/config.util.ts@loadFromEnvFile, plusUSE_DOTENVtoggle - credentials live in a per-user file outside any repo/package tree (team convention:~/.claude/jira.env).- Unconditional
main()insrc/index.ts(the upstreamrequire.main === moduleguard broke startup under embedded Node runtimes). node:httpstransport fallback (safeFetchinsrc/utils/transport.util.ts) - in some MCP host processes the globalfetch(undici) fails withTypeError: fetch faileddespite a live network (observed 2026-07-14 in a Claude-Code-session-spawned connector instance, while a Desktop-spawned instance on the same machine was fine). On that failure the request is retried through the classicnode:httpsstack (multipart encoded vianew Response(FormData), redirects followed withAuthorizationdropped cross-host).FORCE_HTTPS_FALLBACK=trueforces the fallback path (diagnostics / emergency lever). Verified live: JSON GET, JQL search, and a byte-exact 2.1 MB binary download through the media-CDN redirect.- Unresolved-template env guard + creds-path fallback - some hosts pass
the MCPB manifest env without substituting
${user_config.*}; a literal "${...}" value is non-empty and would shadow the .env file and leak into the URL ("ENOTFOUND ${user_config...}.atlassian.net"). Such values are now treated as unset, and when noDOTENV_CONFIG_PATHsurvives, the .env lookup falls back to<cwd>/.env, then~/.claude/jira.env.
Full background and verification evidence:
tools/jira-mcp-plugin/README.md in the 1C_Workspace repo.
How this repo is consumed
This repo exists as a standalone git package so that npx can install it
directly (npx cannot install from a monorepo subdirectory). The
jira@ufc-1c Claude Code plugin (marketplace arcankostenko/1C_Workspace)
declares:
"command": "npx",
"args": ["-y", "github:asky74/mcp-server-atlassian-jira#v3.3.0-ufc.3"]
On first start npm clones this repo (using your system git - your existing
GitHub credentials cover the private access), installs devDependencies, and
the prepare script compiles TypeScript into dist/. Subsequent starts run
from the npx cache. No manual npm install step.
Releases are tags (v<upstream>-ufc.<n>, e.g. v3.3.0-ufc.1). To ship an
update: commit, tag, push the tag, then bump the tag in the plugin's
.mcp.json.
Local working-clone convention: 1C_Workspace/mcp-servers/mcp-server-atlassian-jira/
- an inner repo like
BAS_KUP_local/(own.git/origin, not tracked by the monorepo's whitelist.gitignore).
Credentials: ~/.claude/jira.env with ATLASSIAN_SITE_NAME,
ATLASSIAN_USER_EMAIL, ATLASSIAN_API_TOKEN (see .env.example). Never
commit credentials here.
Development
npm install # also builds (prepare -> tsc)
npm test # 6 suites / 61 tests
manifest.json + .mcpbignore here build the optional Claude Desktop MCPB
bundle (npx @anthropic-ai/mcpb pack .) - a personal, per-machine option.
The 2026-07-13 "built-in-node fetch blocker" is not reproducible on
current Desktop (>=1.20186, Electron 42.5.1 / node 24.17): a probe script
run inside the real MCP runtime on 2026-07-14 got HTTP 200 from both undici
fetch and classic https.get, and the packed bundle works with the stock
command: "node" - no node.exe workaround needed. .mcpbignore caveat:
patterns are gitignore-style, keep them anchored (/src/, not src/) -
an unanchored src/ strips node_modules/*/src and breaks the bundle.
Licensing
Upstream declares "license": "ISC" in package.json but ships no LICENSE
file. This fork keeps the declared license and upstream attribution
(original work: Andi Ashari; attachment tools: cedral, PR #173).
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。