Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Turn any OpenAPI 3 spec into a working MCP server. One file, local (stdio) or remote (HTTP).
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.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"openapi": {
"command": "npx",
"args": [
"-y",
"@asthanaji/openapi-mcp"
]
}
}
}Run this in your terminal
claude mcp add openapi -- npx -y @asthanaji/openapi-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"openapi": {
"command": "npx",
"args": [
"-y",
"@asthanaji/openapi-mcp"
]
}
}
}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": {
"openapi": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@asthanaji/openapi-mcp"
]
}
}
}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 one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
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.
Runs on your computer; the tool list appears in your AI app after you install it.
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 with the GitHub account Asthanaji05, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 26 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Master CSS
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.
Inspect Master CSS classes, generated CSS, and project stylesheets from your AI client.
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.
Turn any OpenAPI 3 spec into a working MCP server. One file, about 130 lines, no dependencies.
node openapi-mcp.mjs https://your-api.com/openapi.json
Every API endpoint becomes a tool that an AI client (Claude, Cursor, etc.) can call. There is no code generation and no per-endpoint files. The spec is read at startup, and the tools are built in memory.
Requires Node 18 or newer.
git clone <this-repo>
cd openapi-mcp node openapi-mcp.mjs sample/animechan.openapi.json
It prints openapi-mcp: 4 tools from "Animechan" -> ... and then waits silently for an MCP client. That is normal: it talks JSON-RPC over stdin/stdout and is not meant to be read by humans.
Add this to ~/Library/Application Support/Claude/claude_desktop_config.json, then restart the app:
{
"mcpServers": { "animechan": { "command": "node", "args": ["/full/path/openapi-mcp.mjs", "/full/path/animechan.openapi.json"] } } }
If the client can't find node, use the full path from which node.
Start the server, then register it:
MCP_AUTH_TOKEN=secret node openapi-mcp.mjs sample/animechan.openapi.json --http 8787
claude mcp add --transport http animechan http://localhost:8787/mcp \ --header "Authorization: Bearer secret"
Then ask in plain English: "give me a random quote from Naruto".
| Mode | Command | Use when |
|---|---|---|
| Local (stdio) | node openapi-mcp.mjs | The client launches the server on your machine |
| Remote (HTTP) | node openapi-mcp.mjs --http | The client connects to a URL, or you want to self-host |
In HTTP mode, clients send JSON-RPC messages as POST http://host: /mcp. Put --http last.
Test it by hand:
curl -X POST localhost:8787/mcp -H 'Authorization: Bearer secret' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
node openapi-mcp.mjs <spec-url-or-file> [base-url] [--http <port>]
| Argument / env var | What it does | |
|---|---|---|
| OpenAPI 3 spec, as a URL or a local file (JSON; YAML needs npm i yaml) | |
[base-url] | Overrides the API address. Defaults to servers[0].url in the spec | |
API_TOKEN | Your secret for the API. The spec's securitySchemes decide where it goes (see Authentication) | |
OAUTH_CLIENT_ID, OAUTH_CLIENT_SECRET | OAuth2 client-credentials: the token is fetched and refreshed automatically | |
OAUTH_REFRESH_TOKEN | OAuth2 refresh-token grant (use with the client id and secret) | |
OAUTH_TOKEN_URL, OAUTH_SCOPE | Optional: override the tokenUrl from the spec, or request a scope | |
API_HEADERS | Extra headers sent on every call, for anything the schemes don't cover. Example: '{"X-App-Id":"abc"}' | |
TOOL_FILTER | Regex. Only tools whose name matches are exposed. Example: `'^(get\ | list)'` for read-only |
MCP_AUTH_TOKEN | HTTP mode only. Requires Authorization: Bearer on every request |
Big APIs can have hundreds of endpoints. Too many tools makes the model choose worse, so use TOOL_FILTER to keep the useful ones.
The server reads securitySchemes from the spec and puts your secret in the right place. You only supply the secret as an environment variable:
| Spec says | Set | Sent as |
|---|---|---|
http / bearer | API_TOKEN=tok | Authorization: Bearer tok |
http / basic | API_TOKEN=user:pass | Authorization: Basic |
apiKey in header | API_TOKEN=key | The header named in the spec (e.g. X-Key: key) |
apiKey in query | API_TOKEN=key | The query parameter named in the spec |
apiKey in cookie | API_TOKEN=key | Cookie: name=key |
oauth2 / openIdConnect, you already have an access token | API_TOKEN=token | Authorization: Bearer token |
oauth2, machine-to-machine | OAUTH_CLIENT_ID + OAUTH_CLIENT_SECRET | Token fetched from the tokenUrl, cached, and renewed before it expires |
oauth2, you logged in once elsewhere | the two above + OAUTH_REFRESH_TOKEN | Access tokens renewed from the refresh token |
Example for Claude Desktop:
{
"mcpServers": { "my-api": { "command": "node", "args": ["/full/path/openapi-mcp.mjs", "https://my-api.com/openapi.json"], "env": { "API_TOKEN": "your-secret" } } } }
Notes:
security list is used (or the first one defined). Per-endpoint security overrides are not applied, so the secret is sent on every call.$ref pointers.operationId is the name, summary the description, and parameters plus request body the input schema.HTTP followed by the response body (cut at 50,000 characters).Many small public APIs only have HTML docs. For those, write a small spec by hand (see sample/animechan.openapi.json, 4 tools in about 35 lines), then run it the same way.
MCP_AUTH_TOKEN bearer token). Some remote clients may require these.MCP_AUTH_TOKEN, or anyone who finds the URL can use your API key.Issues and pull requests are welcome. The goal is to stay small and readable, so please keep new features to a few lines each.