Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Connect AI agents to Process Street workflows, tasks, runs, data sets, and operational records.
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 …”.
Works in Claude on the web, desktop and mobile:
https://mcp.process.st/Run this in your terminal
claude mcp add --transport http process-street https://mcp.process.st/Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"process-street": {
"url": "https://mcp.process.st/"
}
}
}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": {
"process-street": {
"type": "http",
"url": "https://mcp.process.st/"
}
}
}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:
https://mcp.process.st/Menu 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.
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 6, 2026
The registry name was verified with the GitHub account process-street, which owns the repo
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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 (1.0.0) reached the registry 2 months 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, Whisper
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.
One routable IPv6 per AI agent, verifiable from the DNS root. Keyless tools need no signup.
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.
Process Street's hosted Model Context Protocol server connects compatible AI clients to Process Street workflows, workflow runs, tasks, users, data sets, and operational records.
This repository contains the public discovery metadata for the hosted server. It does not contain the server implementation.
Use this remote server URL in an MCP client:
https://mcp.process.st/
The server uses Streamable HTTP. Compatible clients can use the interactive authorization flow. Process Street API keys can also be supplied as bearer tokens where the client supports custom authentication.
See the Process Street MCP Server guide for setup instructions for supported clients.
The server exposes Process Street operations as MCP tools. Depending on the connected user's permissions, these tools can help an AI client:
Access remains subject to the user's Process Street permissions. Organizations that require SAML SSO are not currently supported by the documented MCP connection flow.
server.json is published in the Official MCP Registry as io.github.process-street/process-street-mcp version 1.0.0.
Published Registry versions are immutable. Any metadata correction must use a new unique version.
Issues and pull requests in this repository should concern public discovery metadata or its documentation. Product support and security matters should use the official resources above.