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
Platter
Overview
Description from the maker (original English)
MCP server exposing Read, Write, Edit, Bash, Glob, Grep, and JS tools over stdio.
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 on your computer
- Transport: stdio, 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 your computer with your user’s permissions (files, network, apps).
- The registry lists no key to fill in.
You need
- DockerDocker installed
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
claude mcp add platter -- docker run -i --rm ghcr.io/hadriangateway/platter:2.0.3Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"platter": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/hadriangateway/platter:2.0.3"
]
}
}
}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": {
"platter": {
"type": "stdio",
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"ghcr.io/hadriangateway/platter:2.0.3"
]
}
}
}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.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
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 with the GitHub account hadriangateway, which owns the repo
- … 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 applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 18336 servers in this category
- Published to the registry more recently than 10% of the other 18336 servers in this category
- Basic checks equal to or better than 100% of the other 18336 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 Platter 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 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).
Is it still maintained?
The GitHub repo last changed –, and the latest version (2.0.3) 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. You also need MCPB, Docker on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, NexusWindows
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 2 days ago
Install
NexusWindows
by pironjulien
Windows computer use in the background: desktop apps driven without your mouse or keyboard.
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.
platter
*Your computer, served on a platter.*
MCP server that exposes Read, Write, Edit, Bash, Glob, Grep, and JS tools over Stdio and StreamableHTTP transports. Built with Bun, compiles to standalone executables.
Designed to be used by browser-based (or any MCP-compatible) agents, like Hadrian, to control a computer.
Tools
| Tool | Description |
|---|---|
| read | Read file contents with pagination (offset/limit). Detects image files (JPEG, PNG, GIF, WebP) and returns metadata. Truncates text to 2000 lines or 50KB. |
| write | Create or overwrite files. Auto-creates parent directories. |
| edit | Find-and-replace with exact or fuzzy matching (normalizes smart quotes, dashes, and Unicode whitespace). Requires a unique match, or use replace_all for every occurrence (exact matches only). Returns a unified diff. |
| bash | Execute shell commands with optional timeout. Output truncated to last 2000 lines or 50KB. |
| glob | Fast file pattern matching. Returns up to 500 paths matching a glob pattern (e.g. **/*.ts). |
| grep | Search file contents using ripgrep. Supports regex, file filtering, context lines, and multiple output modes. Requires rg to be installed. |
| js | Evaluate JavaScript/TypeScript in a persistent Node.js vm context. State persists across calls within a session. Supports await, console.log, and loading packages from unpkg.com via await load("package"). Auto-returns the last expression. Not a security sandbox — see Security below. |
Quick start
From a release binary
Download the latest binary for your platform from Releases, or grab it with curl:
# Download (replace the filename for your platform)Available: platter-linux-x64, platter-linux-arm64, platter-darwin-x64, platter-darwin-arm64
curl -fsSL https://github.com/hadriangateway/platter/releases/latest/download/platter-linux-x64 -o platter chmod +x platter
./platter # stdio mode ./platter -t http # HTTP mode on :3100
Docker
docker run --rm -i ghcr.io/hadriangateway/platter # stdio modedocker run --rm -p 3100:3100 ghcr.io/hadriangateway/platter -t http --host 0.0.0.0 # HTTP mode
See Docker below for mounting paths, networking, installing extra software, and building custom images.
From source
bun installbun run dev # run directly from TypeScript bun run compile # build standalone binary for current platform
Usage
platter v1.x.xYour computer, served on a platter.
Usage: platter [options]
Options: -t, --transport Transport mode (default: stdio) --tray Run the HTTP server with a Linux system tray (implies --transport=http, persists state across restarts in ~/.config/platter) -p, --port HTTP port (default: 3100) --host HTTP bind address (default: 127.0.0.1) --cwd Working directory for tools (default: current directory) --cors-origin Allowed CORS origin (default: *) --auth Auth mode: oauth, bearer, jwks, none (default: oauth) --auth-token Bearer token for HTTP auth (auto-generated if omitted) --tls-cert TLS certificate file (PEM) — enables HTTPS --tls-key TLS private key file (PEM)
External JWKS / OIDC (--auth jwks — verify tokens from an external IdP): --oauth-issuer Issuer URL; OIDC-discovers the JWKS endpoint --jwks-url Explicit JWKS endpoint (overrides discovery) --oauth-audience Expected token audience (strongly recommended) --jwks-scope-grants Map tools: token scopes to tool access (fail closed: a token with no tools: scopes is granted no tools)
Process management: --max-processes Max concurrent bash processes per session (default: 20) --max-sessions Max concurrent HTTP sessions (default: unlimited)
Restrictions: --tools Comma-separated tools to enable (default: all) Valid: read, write, edit, bash, glob, grep, js --allow-path Restrict read/write/edit/glob/grep to this path (repeatable) Does not restrict bash or js --allow-command Allow bash commands matching this pattern (repeatable) Pattern must match the entire command string Applies to bash only; does not restrict js
Sandbox (applies to bash only; the js tool is never sandboxed): --sandbox Use just-bash sandbox instead of native bash --sandbox-fs Filesystem backend: memory, overlay, readwrite (default: readwrite) --sandbox-allow-url Allow network access to URL prefix (repeatable)
-h, --help Show this help message -v, --version Show version number
Restrictions
You can limit which tools are registered, which filesystem paths file tools can access, and which commands the bash tool can execute.
Tool selection
Only register specific tools. Unregistered tools are completely hidden from MCP clients:
platter --tools read,glob,grep # read-only serverplatter --tools read,write,edit # no bash/search/js
Path restrictions
Restrict file-accessing tools (read, write, edit, glob, grep) to one or more directory trees. Paths are resolved to absolute form and symlinks are resolved via realpath to prevent escaping:
platter --allow-path /home/user/projectplatter --allow-path /home/user/project --allow-path /tmp
Command restrictions
Only allow bash commands whose entire command string matches at least one regex pattern:
platter --allow-command "git( .*)?" # git onlyplatter --allow-command "git( .*)?" --allow-command "npm( .*)?" # git or npm platter --allow-command "ls( .*)?" --allow-command "cat .*" # ls or cat
Patterns are anchored: --allow-command "git( .*)?" compiles to ^(?:git( .*)?)$, so git status matches but rm -rf / && git status does not.
Combined example
# Locked-down: read-only tools, scoped to one directoryplatter --tools read,glob,grep --allow-path /home/user/project
Full tools, but bash restricted to git/npm, files restricted to project
platter --allow-path ./my-project --allow-command "git( .*)?" --allow-command "npm( .*)?"
Active restrictions are logged to stderr at startup.
Authentication
Controlled by --auth :
| Mode | Description |
|---|---|
oauth (default) | OAuth 2.1 Authorization Code + PKCE, with a static bearer token as fallback |
bearer | Static bearer token only |
jwks | Resource-server mode: verifies JWT access tokens issued by an external OAuth/OIDC issuer (Auth0, Keycloak, Okta, Entra) via JWKS |
none | No authentication |
OAuth 2.1 (--auth oauth)
MCP clients that support RFC 9728 (Protected Resource Metadata) can discover platter's OAuth endpoints automatically and authenticate without manual token copying.
The flow:
- Client discovers
/.well-known/oauth-authorization-serverand/.well-known/oauth-protected-resource/mcp - Client registers via
POST /register(RFC 7591 dynamic client registration) - Client initiates Authorization Code + PKCE flow via
/authorize - A confirmation code is displayed out-of-band (printed to stderr, or shown as a desktop notification in tray mode)
- User sees a consent page, enters the confirmation code, selects which tools to grant, and approves or denies the request
- Client exchanges the authorization code for tokens at
/token - Subsequent requests use
Authorization: Bearer
The confirmation code proves that the person approving the request has access to the platter process — a remote attacker who can reach the consent page cannot approve without it. Codes are single-use and expire after 5 minutes, with a maximum of 5 attempts.
Access tokens expire after 1 hour and can be refreshed. Client registrations are persisted to ~/.config/platter/clients.json. A static bearer token is also accepted as a fallback for clients that don't support OAuth.
Bearer token (--auth bearer)
A random bearer token is generated at startup and printed to stderr (or stored in the system keyring in tray mode). Every request must include Authorization: Bearer . You can provide your own:
platter -t http --auth bearer --auth-token my-secret-tokenNo authentication (--auth none)
Disable authentication entirely (e.g. behind a reverse proxy that handles auth):
platter -t http --auth noneExternal JWKS / OIDC (--auth jwks)
In jwks mode platter acts as a pure resource server: it does not mint its own tokens. Instead it verifies JWT access tokens issued by an external OAuth/OIDC authorization server (Auth0, Keycloak, Okta, Microsoft Entra) — validating the signature against the issuer's JWKS, plus the iss, aud, and exp claims. This lets you put platter behind your existing IdP without a reverse proxy.
# Auth0 (root issuer)platter -t http --auth jwks \ --oauth-issuer https://YOUR_TENANT.auth0.com/ \ --oauth-audience https://platter.example.com/mcp
Keycloak (realm issuer)
platter -t http --auth jwks \ --oauth-issuer https://kc.example.com/realms/myrealm \ --oauth-audience platter-api
Skip discovery / point at a JWKS endpoint directly
platter -t http --auth jwks \ --jwks-url https://idp.example.com/.well-known/jwks.json \ --oauth-audience platter-api
Audience validation (strongly recommended). Set --oauth-audience to the API identifier configured in your IdP. If you omit it, platter accepts *any* valid token from the issuer — including tokens minted for a different resource server (a confused-deputy risk). platter prints a warning at startup when audience validation is disabled.
Discovery. With --oauth-issuer, platter fetches the issuer's /.well-known/openid-configuration (falling back to /.well-known/oauth-authorization-server) at startup to find the jwks_uri and re-advertise the authorization server to RFC 9728-capable MCP clients (at /.well-known/oauth-protected-resource/mcp). Pass --jwks-url to skip discovery, or if the IdP isn't reachable at startup. If discovery fails but --jwks-url is set, token verification still works — only the RFC 9728 auto-advertisement is skipped.
Authorization (what a token can do). By default a verified token gets admin-level access, bounded only by the operator's CLI restrictions (--tools, --allow-path, --allow-command, --sandbox) — the IdP controls *who* gets in, the CLI flags control *what* they can do. Pass --jwks-scope-grants to additionally honor tools: scopes in the token (e.g. tools:read tools:bash), which further narrow the granted tools (they can only narrow, never widen the operator's ceiling). The scope claim and Entra-style scp claim are both supported. In this mode access is fail closed: a token carrying no tools:* scope is granted no tools at all, so a token must explicitly request the tools it needs.
No static fallback. Unlike oauth mode,
Only the beginning is shown; read the rest in the repo