Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Finished, editable PowerPoint (.pptx) decks from a brief and your documents
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
AuthorizationValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http kinsy https://mcp.kinsy.ai/mcp --header 'Authorization: your-value'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"kinsy": {
"url": "https://mcp.kinsy.ai/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"kinsy": {
"type": "http",
"url": "https://mcp.kinsy.ai/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Authorization secret required HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
We have not read this server’s tool list yet; we check endpoints in rotation.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified against the domain kinsy.ai (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Not checked yet; we check endpoints in rotation
Not checked yet; we check endpoints in rotation
Not checked yet; we read the tool list when we check the endpoint
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: Authorization
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (0.1.0) reached the registry 11 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: Spec Driven Development, Remote Desktop Commander, FlyDocs
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Spec-driven development workflow: your agent works issues, sessions and the status lifecycle.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
The remote Model Context Protocol server behind https://mcp.kinsy.ai/mcp. Hosted assistants and agents connect to it with a Kinsy API key and turn a brief and the user's source material into a finished, editable PowerPoint (.pptx) deck.
It is a thin client over the public Kinsy API: every call is made with the caller's own key, so credits, limits and deck ownership are enforced by the API exactly as for the CLI. The server stores nothing and holds no credentials of its own.
| Tool | What it does | Changes anything? |
|---|---|---|
create_deck | Starts a deck from a brief and optional sources (text). Answers at once with a deck_id. | Spends credits |
wait_for_deck | Waits for a deck to finish (up to 540 s), streaming progress, then returns its links. | No |
get_deck | Status and links; optionally slide image links and the claims the sources could not back. | No |
export_deck | A fresh one-hour download link for the .pptx, PDF, or a zip of slide images. | No |
edit_slide | Rewrites one slide from an instruction. | Spends credits |
list_themes | The theme ids create_deck accepts. | No |
Results are a short sentence plus structured content. The server never echoes a brief or source text back, and never includes the key.
Create a key in Settings → API keys on kinsy.ai, then point your client at https://mcp.kinsy.ai/mcp with the header Authorization: Bearer ksy_live_…. Per-client instructions: kinsy.ai/docs/mcp.
python3 -m venv .venv && .venv/bin/pip install -r requirements.lock pytest
.venv/bin/python -m pytest KINSY_MCP_SERVE=1 KINSY_API_BASE=https://kinsy.ai .venv/bin/uvicorn kinsy_mcp.server:app --port 8080
requirements.in lists the direct dependencies; scripts/lock.sh resolves the hash-pinned requirements.lock the image installs.
MIT. © Kinsy.