SpecDown MCP Server
OfficialClick on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@SpecDown MCP ServerShow me the spec documents in my project."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
SpecDown MCP Server — AI-Native Markdown MCP for AI Assistants
AI-native Markdown MCP server for SpecDown — give Claude, Cursor, Copilot, and other AI coding assistants direct read/write access to your Markdown spec documents.
Stop copy-pasting specs into AI chat. Connect once, AI reads your Markdown docs forever — AI-native spec-driven development.
Jump to your IDE: Cursor • Claude Desktop • Claude Code • Windsurf • OpenCode • VS Code • Codex CLI
What is AI-Native Markdown MCP?
Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external tools and data sources. specdown-mcp is an AI-native Markdown MCP server that exposes your SpecDown spec documents as MCP resources — so Claude, Cursor, and other AI tools can read, search, and edit your specs directly.
AI-native Spec as Code + AI = spec-driven development:
Engineer writes Markdown spec → AI reads spec via MCP → AI implements feature from specRelated MCP server: MCP Docs Provider
Features
Read & search Markdown docs — list projects, browse document tree, full-text search
Edit docs — update Markdown content, create new documents (auto-versioned)
Upload images — attach image assets and get markdown links back for documents
Inline comments — add and list comments anchored to specific text
Sync planning for agents — inspect remote snapshots, plan local-vs-remote sync, and apply remote sync operations
AI-native spec-driven development — give AI full Markdown context with zero copy-paste
13 MCP tools — complete read/write and sync-planning API for your spec documents
MCP resources —
specdown://projects,specdown://project/{id}
Prerequisites
SpecDown account — free plan available
API key — generate at Settings → API Keys
Quick Start
No install needed — npx runs it on demand:
# Verify it works
SPECDOWN_API_KEY=your_key npx specdown-mcpIDE Configuration
Replace YOUR_API_KEY with your key from SpecDown Settings.
Cursor
Config path: .cursor/mcp.json (project) or ~/.cursor/mcp.json (global)
{
"mcpServers": {
"specdown": {
"command": "npx",
"args": ["-y", "specdown-mcp"],
"env": {
"SPECDOWN_API_KEY": "YOUR_API_KEY"
}
}
}
}Claude Desktop
macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"specdown": {
"command": "npx",
"args": ["-y", "specdown-mcp"],
"env": {
"SPECDOWN_API_KEY": "YOUR_API_KEY"
}
}
}
}Claude Code
{
"mcpServers": {
"specdown": {
"command": "npx",
"args": ["-y", "specdown-mcp"],
"env": {
"SPECDOWN_API_KEY": "YOUR_API_KEY"
}
}
}
}Windsurf
Config path: ~/.windsurf/mcp.json or .windsurf/mcp.json (project)
{
"mcpServers": {
"specdown": {
"command": "npx",
"args": ["-y", "specdown-mcp"],
"env": {
"SPECDOWN_API_KEY": "YOUR_API_KEY"
}
}
}
}OpenCode
Config path: opencode.json (project root) or ~/.config/opencode/opencode.json
{
"mcpServers": {
"specdown": {
"command": "npx",
"args": ["-y", "specdown-mcp"],
"env": {
"SPECDOWN_API_KEY": "YOUR_API_KEY"
}
}
}
}VS Code
Config path: .vscode/mcp.json
{
"servers": {
"specdown": {
"type": "stdio",
"command": "npx",
"args": ["-y", "specdown-mcp"],
"env": {
"SPECDOWN_API_KEY": "YOUR_API_KEY"
}
}
}
}Codex CLI
Config path: ~/.codex/config.toml
[mcp_servers.specdown]
command = "npx"
args = ["-y", "specdown-mcp"]
[mcp_servers.specdown.env]
SPECDOWN_API_KEY = "YOUR_API_KEY"Available MCP Tools
Tool | Description |
| List all projects you have access to |
| List Markdown documents in a project |
| List preview-only project attachments |
| Read full Markdown content by ID or project+path |
| Read attachment metadata, text preview, embed ref, and download URL |
| Full-text search across all Markdown spec docs |
| Get project overview: tree, README, description |
| List inline comments on a document |
| Add a comment (anchored to text or threaded reply) |
| Create a new Markdown document or folder |
| Replace Markdown content (auto-versioned on change) |
| Upload an image asset and return a markdown link |
| Upload HTML/HTM as editable documents, or other attachments with a |
| Return remote sync snapshots and summary for a project subtree |
| Compare local snapshots with remote docs and produce a sync plan |
| Apply remote upsert/delete operations produced from a sync plan |
Environment Variables
Variable | Required | Description |
| Yes | Your API key from SpecDown Settings |
| No | Override API base URL (for self-hosted instances) |
Troubleshooting
Error: SPECDOWN_API_KEY must be set
→ Add SPECDOWN_API_KEY to the env block in your IDE's MCP config.
Unauthorized or 401
→ Key may be invalid or expired. Regenerate at Settings → API Keys.
Server not appearing in IDE
→ Restart the IDE after editing MCP config. Cursor: Cmd+Shift+P → "MCP: Reload Servers".
npx: command not found
→ Install Node.js ≥ 18 from nodejs.org.
Self-hosted SpecDown
Point the MCP server at your own instance:
"env": {
"SPECDOWN_API_KEY": "YOUR_API_KEY",
"SPECDOWN_API_URL": "https://your-specdown.example.com"
}Related
SpecDown — Markdown editor online, Spec as Code platform
specdown-cli — Markdown CLI for terminal, CI/CD, and automation
License
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/specdown-app/mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server