Markdown Pipeline
io.github.markdown-pipelinePublished by GitHub account markdown-pipelinev0.1.16Updated Nov 3, 2026
Your team's Jira as clean Markdown files, kept current for your AI agent. Local and read-only.
Overview
Local, read-only MCP server that lets an agent search and read your team's Jira issues and folders as clean Markdown files kept current on your machine.
- What you can do
- Search and read the Markdown files the app writes, plus your raw and wiki folders
- List files and see recent changes, such as what changed since yesterday
- Check sync status and trigger a sync of Jira issues and local folders into Markdown
- No tool writes or edits your files; the agent does the summarizing and analysis from the files
- When to use it
- When you want Claude Code or Codex to answer questions about your team's Jira issues or local folders without giving the agent direct Jira access, and you are fine with the content living as Markdown files in a folder or repo you choose.
- Requirements
- Runs locally on Linux (tested; macOS untested, Windows via WSL 2) as a Python package installed with uv/uvx; the install script needs network access and installs under your home folder. A Jira Cloud account and its API token are configured in the app, not in the MCP server. Connect with the mdpipeline connect command for Claude or Codex. No environment variables or headers declared.
Installation
In SourceWeft
- Open Markdown Pipeline in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
Markdown Pipeline
Your team's tools as clean Markdown files, kept current for your AI agents. Early access: Jira Cloud and folders on your computer, on Linux.
- Local. It runs on your computer. Your files go to a folder you choose, or to a GitHub repo you choose.
- We only read. We never change anything in Jira or in your source folders.
- Raw layer only. It does not summarize or analyze anything. Your agent (Claude Code, Codex) does that, from the files.
- It sees what you see. It reads Jira with your own account's API token, so the files hold only the issues your account can read. The token never appears in the files, the logs or your agent's answers. Anyone who can open the folder or repo you choose can read the files, so choose it the way you'd choose who sees those issues.
- Open source. Apache-2.0. The code that reads your Jira is in this repository.
Install
Linux (tested). One command. It installs uv if you don't have it (a Python tool manager), then the app, all under your home folder, with no administrator rights:
It installs the latest release from GitHub Releases. No GitHub account, token or sign-in is needed. Then type mdpipeline: your browser opens the app. If your shell says mdpipeline: command not found, open a new terminal (or run uv tool update-shell) and try again.
Run the same command again any time to move to the newest release; your settings and pipelines are kept.
Platforms: Linux (tested). macOS is untested. On Windows, use WSL 2 (Ubuntu) and run the command inside it. On a server or in WSL 2, background sync stops when you log out unless you run loginctl enable-linger $USER once; after a reboot, logging in or running any mdpipeline command starts it again.
Use it from your agent (MCP)
The app includes a local MCP server, so Claude Code or Codex can search and read the files.
It prints the exact command (Claude Code) or config block (Codex) for your setup. Your agent starts the server itself when it needs it; nothing extra runs in the background. Tools: search, read, list, recent_changes ("what changed since yesterday?"), sync_status and sync. No tool writes or edits your files. The server reads only the Markdown files the app wrote (and your raw/ and wiki/ folders), on your computer.
What we send
Usage data only if you choose to share it, and the words you type in a feedback or source request when you press Send.
The full list, in plain words: what-we-send. Turn it off any time: mdpipeline usage off.
Feedback and problems
Open an issue on this repository: Issues. Tell us what you tried, what you expected and what happened.
Uninstall
mdpipeline uninstall turns background sync off and prints the one command that removes the program. The Markdown files it wrote stay where they are.
Full reference (commands, settings, safety rules): docs/reference.md.
License
Apache-2.0. See LICENSE.
Source: README.md at commit 7da65a7
Tools
0Version history
2- v0.1.16LatestNov 3, 2026
- v0.1.15Nov 1, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts