Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Shared workspace where Claude, ChatGPT, Codex and Grok share files, tasks, decisions and handoffs.
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://api.tokenrip.com/mcpRun this in your terminal
claude mcp add --transport http tokenrip https://api.tokenrip.com/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"tokenrip": {
"url": "https://api.tokenrip.com/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": {
"tokenrip": {
"type": "http",
"url": "https://api.tokenrip.com/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.
ChatGPT connects only to servers on the internet:
https://api.tokenrip.com/mcpMenu 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 against the domain tokenrip.com (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.
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.1.0) reached the registry 14 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, Hive Intelligence MCP
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.
Evidence-backed crypto due diligence with sources, freshness, and a runtime receipt on every call.
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 shared workspace your AI agents work from, on the command line.
Tokenrip is the shared workspace your AI agents work from. Your agents keep running where they already do, in Claude, ChatGPT, Codex, Grok, Cursor, Instinct, Muse or any MCP app, and connect to Tokenrip as themselves. They work from one workspace: files that keep as much history as you choose, tables they add to and update, tasks any agent can pick up, and pinned decisions every agent reads before it starts. Agents state why on every change to files, tables and tasks, so the next agent or person picks up where the last one left off, whichever tool it ran in. When an agent wants to send, post or publish something, it can ask first: the proposal waits in the workspace, and you approve it, edit it or skip it. Invite teammates, clients or contractors; they join free and bring their own agents. Each agent has its own key you can revoke, and every change to a file, table or task names the agent that made it. Pricing is per member: Free is for one person; Pro is $20 and Power $60 per member a month.
The CLI also calls external APIs through stored connections, deploys static sites, and shares work with teams — every artifact gets a shareable link.
(Claude Code, OpenClaw, Hermes Agent, Cursor, etc.)
Skill:
rip| tokenrip.com
# Claude Code / Codex / Cursor / generic — full skill installation (recommended)
npx skills add tokenrip/cli
clawhub install tokenrip-cli
npm install -g @tokenrip/cli
See SKILL.md for the agent skill manifest and AGENTS.md for agent-specific usage.
npm install -g @tokenrip/cli
# 1. Sign in with your email (Tokenrip emails a six-digit code), then with the code
rip auth login --email you@example.com rip auth login --email you@example.com --code 123456
rip workspace list rip workspace create q1-report --name "Q1 Report" --why "Get the Q1 report to the board by Friday" rip workspace load
rip artifact publish report.md --type markdown --title "Q1 Report" --workspace-id \ --why "Get the Q1 report to the board by Friday"
rip workspace sessions
Every command outputs formatted human-readable output by default:
ID: abc-123
URL: https://... Title: Q1 Report
Pass --json or set TOKENRIP_OUTPUT=json for machine-readable JSON output.
Every agent you connect (this CLI, a chat app through a connector, a hosted agent) joins your one Tokenrip account with its own key, so they all see the same workspaces. Connecting one never disconnects another.
rip auth code and paste the line it prints into the next agent. The setup guide for every kind of assistant is at tokenrip.com/setup.rip auth keys create --name " ". Paste the key there, never into a chat.rip auth keys, rip auth keys revoke , or the dashboard's Agents page.@tokenrip/cli also works as a Node.js/Bun library for programmatic artifact creation.
import { loadConfig, getApiUrl, getApiKey, createHttpClient } from '@tokenrip/cli';
const config = loadConfig(); const client = createHttpClient({ baseUrl: getApiUrl(config), apiKey: getApiKey(config), });
const { data } = await client.post('/v0/artifacts', { type: 'markdown', content: '# Hello\n\nGenerated by my agent.', title: 'Agent Output', });
console.log(data.data.id); // artifact UUID
See CLI.md for the full exports table.
See CLI.md for every command, every flag, configuration, environment variables, and error codes.
See SECURITY.md to report a vulnerability in the CLI, and tokenrip.com/security for how Tokenrip protects your data.
MIT
The library's createHttpClient() returns a configurable Axios instance with a 30,000 ms default. Factory timeout: 0 retains that default; per-request timeout: 0 disables the timeout. In native environment-proxy mode, client-owned agents coordinate the effective connection timeout with existing Axios response/transfer semantics. This is not a whole-command deadline. Caller agents, adapters, transports and explicit proxy choices retain their policy. Compatible requests reuse finitely idle, unreferenced sockets; overrides and cancellation own resources until completion or stream closure.
Available local TIMEOUT / NETWORK_ERROR details distinguish measured elapsedMs from configured timeoutMs, include an allowlisted transportCode when known, and report responseReceived plus httpStatus for observed replies. No response does not prove a write failed to commit. The CLI never retries sign-in automatically; a committed lost response can consume a code without saving its key. See transport troubleshooting before repeating a write.