An md file as a chat interface and editable history in one.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"chat-md": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
An md file as a chat interface and editable history in one.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in productivity / writing
Persistent memory using a knowledge graph
Dynamic problem-solving through sequential thought chains
mini cli search engine for your docs, knowledge bases, meeting notes, whatever. Tracking current sota approaches while being all local
A markdown editor — and the bridge to your LLM. Local-first, MIT, ~15 MB. Bundled MCP server lets Claude Code / Codex / Cursor drive your vault directly. 14 AI providers BYOK.
MCP Security Weekly
Get CVE alerts and security updates for Chat.Md and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Finally, a fully editable chat interface with MCP support on any LLM.
chat.md is a Visual Studio Code extension that reimagines AI interaction through plain text files. Unlike ephemeral web interfaces or proprietary chat windows, chat.md embraces a file-first approach where your conversations with AI are just markdown files with a .chat.md extension. Edit them, version control them, share them - they're your files. The AI directly writes its response in the file.
Any '*.chat.md' file is now an AI agent hackable by you. Go crazy with non linear AI conversation.
Here's the chat I used to publish this vscode extension using gemini-2.5-pro and wcgw mcp
NOTE ⚠️: chat.md is 100% AI coded and should be treated as a feature rich POC.
| Other AI Tools | chat.md |
|---|---|
| ❌ Linear conversations or limited editing | ✅ Non-linear editing - rewrite history, branch conversations |
| ❌ Tool execution tied to proprietary implementations | ✅ Any LLM model can do tool calling |
| ❌ Can't manually edit AI responses | ✅ Put words in LLM's mouth - edit and have it continue from there |
| ❌ MCP not supported in many LLMs | ✅ Any LLM model can use MCP servers |
| ❌ Max token limit for assistant response can't be resumed | ✅ Resume incomplete AI responses at any point |
| ❌ Conversations live in the cloud or inaccessible | ✅ Files stored locally alongside your code in human readable format |
| ❌ Separate context from your workspace | ✅ Attach files directly from your project |
Unlike Copilot's inline suggestions, ChatGPT's web interface, or Cursor's side panel, chat.md treats conversations as first-class files in your workspace:
# %% user
How can I optimize this function?
[#file](src/utils.js)
# %% assistant
Looking at your utils.js file, I see several opportunities for optimization:
1. The loop on line 24 could be replaced with a more efficient map/reduce pattern
2. The repetitive string concatenation can be improved with template literals
...
Chat.md is a Model Context Protocol (MCP) client - an open standard for tool execution that works with any LLM.
Chat.md doesn't restrict any LLM from tool calling unlike many chat applications.
<tool_call>
<tool_name>filesystem.searchFiles</tool_name>
<param name="pattern">*.js</param>
<param name="directory">src</param>
</tool_call>
[file](path/to/file)Since chat.md files are just text, you have complete control over your AI interactions: