Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
Studio
Overview
Description from the maker (original English)
Build and run visual creative-production workflows from your AI agent.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs in the cloud
- Transport: Streamable HTTP
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://mcp.studio.kaitoi.ioRun this in your terminal
claude mcp add --transport http studio https://mcp.studio.kaitoi.ioOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"studio": {
"url": "https://mcp.studio.kaitoi.io"
}
}
}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.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"studio": {
"type": "http",
"url": "https://mcp.studio.kaitoi.io"
}
}
}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.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://mcp.studio.kaitoi.ioMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
Basic checksi
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
- ✓ Pass
Maker matches the repo
The registry name was verified against the domain kaitoi.io (the registry checks domain ownership)
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- … Not checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Otheri
- More stars than 0% of the other 32564 servers in this category
- Published to the registry more recently than 11% of the other 32564 servers in this category
- Basic checks equal to or better than 100% of the other 32564 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Studio safe?
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.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
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.
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 5 months ago.
Which apps can use it?
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.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, Tools MCP
Alternatives
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
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
Tools MCP
by First-CH
Web production tools for AI agents: contrast, JP text, WebP, JSON-LD, slugs, dates and 40+ more
Runs on your computerUpdated today
Install
README from the maker
Open the README
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.
Kaitoi Studio MCP
Connect an MCP-compatible agent to Kaitoi Studio to discover nodes, work with projects and assets, inspect workflows, and run creative-production graphs. This repository contains connection documentation, examples and registry metadata for Kaitoi's hosted server; the backend runs as part of Kaitoi Studio.
Connect
Add the remote server using your client's MCP connection settings:
https://mcp.studio.kaitoi.ioThe transport is Streamable HTTP. Compatible clients discover OAuth and open Kaitoi's browser sign-in and consent flow. Each user connects their own account. Account permissions and the granted mcp:read / mcp:write scopes determine available actions. Check current account eligibility at kaitoi.io/studio.
A URL-only configuration for clients that support remote HTTP and OAuth:
{"mcpServers": { "kaitoi-studio": { "url": "https://mcp.studio.kaitoi.io" } } }
For clients using manually supplied bearer tokens, generate the client-specific configuration in Studio's Settings → MCP. Keep that token private and out of source control. A manually pasted token is an alternative connection mode; it is not a replacement for OAuth in directory submission.
Connection examples:
- Native remote HTTP with OAuth
- Claude Code with browser authorization
- Legacy Claude Desktop bridge with OAuth
- Manual bearer-token alternative
Workflows
The current implementation includes tools for:
- Discovering nodes and inspecting their inputs before running them.
- Building and validating graphs and saving reusable projects.
- Starting durable runs, polling their status and retrieving results.
- Browsing existing projects, files and supported workflow templates.
- Reading API contracts and guidance for building applications with Kaitoi.
- Connecting to an explicitly selected, opted-in Studio session when supported.
The authenticated server's discovery responses are authoritative. Tool counts, profiles, optional integrations and UI features vary by deployment, account permissions and granted scopes; this README does not certify an exact live catalog or availability in every host.
Studio canvas and headless graphs
An unattached MCP connection uses a separate account-scoped server graph. Connecting the server does not automatically attach an agent to whichever Studio tab is open. Where Studio attachment is enabled and advertised, select and attach the intended opted-in tab explicitly. Lost attachment must be resolved explicitly rather than silently switching to another graph.
Execution and results
Provider-backed operations may consume existing Kaitoi credits and provider allowances. Use the advertised run/status/result contracts and stable idempotency keys to avoid duplicate execution when retrying. A pending result means poll the original run, rather than starting it again. Media rendering and optional Run Inspector UI depend on host and server support; structured results remain the baseline interface.
First requests
- “List my Kaitoi projects.”
- “Find nodes that join two pieces of text. Show their inputs without running anything.”
- “Describe the workflow available to this connection without changing it.”
- “Show the API contract for the workflow template I select.”
Support and policies
Public-directory submission and approval are separate from connecting the hosted server directly. Nothing in this README implies approval or endorsement by a particular MCP client or directory.
Registry metadata
server.json contains the source metadata for the io.kaitoi/studio MCP Registry listing. mcp-registry-metadata.json provides descriptive information and tool groups for maintainers. Updating these files on GitHub does not publish a new Registry version or submit a ChatGPT plugin; those are separate release steps. The live authenticated catalog remains authoritative.
License
Repository documentation and examples are provided under the MIT License. Access to the hosted server is governed by the Kaitoi Studio terms of service.