Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Build, test and publish Olbrain AI agents from Claude Code, Codex, Antigravity, Cursor or Claude.ai.
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://alchemist.olbrain.com/mcp/Run this in your terminal
claude mcp add --transport http alchemist https://alchemist.olbrain.com/mcp/Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"alchemist": {
"url": "https://alchemist.olbrain.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": {
"alchemist": {
"type": "http",
"url": "https://alchemist.olbrain.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://alchemist.olbrain.com/mcp/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.
The server asks you to sign in before it lists its tools.
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 olbrain.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 1602 ms (HTTP 401)
Declares OAuth sign-in, so your AI app can take you to log in
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 3 of 3 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 (0.9.11) reached the registry 2 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, zanadir
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.
Find what a repository's CI is missing, and which security checks cannot fail the build.
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.
Alchemist
OLBRAIN · AGENT BUILDER
Build, test and publish Olbrain AI agents from Claude Code, Codex, Antigravity, Cursor, GitHub Copilot or claude.ai.
You describe the agent. Claude plans it with Alchemist's guidance; Alchemist builds it, tests it, checks every step — and asks you before anything goes live, unless you let Claude decide.
Install · How a build works · Capabilities · Tools · Privacy · Docs
Alchemist is Olbrain's agent builder, available as an MCP server and a Claude Code plugin. You tell Claude what the agent should do, in plain words. Claude (or Codex, Antigravity or Cursor) plans and designs the agent from your words and your project, with Alchemist's step-by-step guidance. Alchemist builds it in your Olbrain organisation, tests it on real inputs, checks each step in order, refusing one that is skipped, and publishes it.
Every agent it builds runs on Olbrain and stays visible in Noesis, Olbrain's console, where your team can open, review and change it.
Olbrain's own front door, built with Alchemist: one team of agents on WhatsApp and website chat.
/plugin marketplace add Olbrain/alchemist-plugin
/plugin install alchemist@alchemist
Then run /mcp, pick alchemist and sign in with your Olbrain account. New to Olbrain? Choose Create account on the sign-in page.
Claude Code asks before every tool call. To stop it asking each time Claude checks on a build, allow these five tools once under /permissions (they read; alchemist_state also marks the build's news as seen, and Claude shows it to you): mcp__plugin_alchemist_alchemist__whoami, mcp__plugin_alchemist_alchemist__alchemist_builds, mcp__plugin_alchemist_alchemist__alchemist_build, mcp__plugin_alchemist_alchemist__alchemist_capabilities and mcp__plugin_alchemist_alchemist__alchemist_state. Leave the rest asking, including alchemist_do and alchemist_answer: they take build steps, answer cards or change your organisation.
To see an agent drawn in a pane beside the chat, also install the canvas:
/plugin install alchemist-canvas@alchemist
It draws the agent whenever Claude shows it, and redraws it when a publish or make-live card arrives, with new, changed and removed parts marked. /agent-canvas opens the pane when the terminal is too narrow for it to open by itself. It needs a Claude Code build with plugin panes; older builds and Codex skip it.
codex mcp add alchemist --url https://alchemist.olbrain.com/mcp/
codex mcp login alchemist
Optional: copy plugins/alchemist/skills/alchemist to ~/.agents/skills/alchemist so Codex follows the same workflow as Claude, including when to continue a build and when to start a new one. Without it, the server's own instructions carry the same rule. A copied skill does not update itself: copy it again after each release (0.9.0 changes how builds run).
agy plugin install https://github.com/Olbrain/alchemist-plugin/tree/main/plugins/alchemist
Or in the Antigravity app: Customizations → Plugins → Install from URL with the same URL. This installs the Alchemist skills and connects the MCP server. Sign in with your Olbrain account when Antigravity asks; if it doesn't, open /plugin, expand alchemist under Installed and choose Sign in. The canvas is Claude Code only.
Install Olbrain Alchemist from the Cursor plugin directory: cursor.directory/plugins/alchemist. Sign in with your Olbrain account when Cursor asks, or from the alchemist row in Customize. A team admin can also add this repository in Dashboard → Plugins & MCPs → Import from Repo (https://github.com/Olbrain/alchemist-plugin). The canvas is Claude Code only.
copilot plugin marketplace add Olbrain/alchemist-plugin
copilot plugin install alchemist@alchemist
This installs the Alchemist skills and connects the MCP server in Copilot CLI. Ask Copilot to use Alchemist and sign in with your Olbrain account when the browser opens. The canvas is Claude Code only.
Add a custom connector with the URL https://alchemist.olbrain.com/mcp/ (Customize → Connectors → Add custom connector; on Team and Enterprise plans an owner adds it under Organization settings → Connectors). Then click Connect and sign in.
| Stage | What happens | Your call |
|---|---|---|
01 Brief | Your coding agent drafts what you asked for (who the agent serves, what it does, what it must not do) from your words and your project; Alchemist checks it. | Approve or change it |
02 Plan | Your coding agent drafts the agents, steps, channels and tools; Alchemist checks it. | Approve or change it |
03 Build | Alchemist builds the agent, connects its tools and knowledge, and reviews the setup for gaps and contradictions. | Sign in to tools or add keys when a card asks |
04 Test | Your coding agent writes the tests; Alchemist checks them, runs them on the draft and grades them. A job gets a live run on a real input first. | Run the live test, or not yet |
05 Publish | The tested version is published, with a 30-day free trial for a new agent. | Publish, or not yet |
06 Go live | Embed code, API and SDK steps, or the channel it answers on. | You run the commands |
Alchemist gives one stage at a time and refuses a step taken out of order. Builds started in Noesis, and plugin builds while Olbrain moves accounts over, are still planned by Alchemist's own model through the alchemist tool; the skill switches by itself.
On a build Claude plans, each agent has a budget: six passes per fix round, a stop after three passes in a row without a gain, four failed compiles and 120 draft test runs. When a build reaches one, Claude shows the best result so far and asks whether to continue (two more passes). A stronger model usually gets a build through its tests first time.
Before Alchemist publishes an agent, makes it live, merges agents or changes how one behaves, it stops with an approval card. You decide how many of these Claude answers for you: tell it in the chat, or put it in your CLAUDE.md, AGENTS.md or GEMINI.md, for example *"Approve plans and tests yourself; ask me before publishing."* If you haven't said, Claude answers every card itself in auto mode (Codex: running without approvals; Antigravity: set to proceed without asking) and asks you otherwise. It still asks for what only you can do, like sharing a Drive folder or a browser step. On a build Claude plans, removing an agent, forgetting a customer, renaming or moving an agent, changing a job's email address, and publishing despite failing tests are always answered in the browser, from the link Claude gives you. If Claude Code blocks an answer, answer the card on its build page, or allow the tool with /permissions: mcp__plugin_alchemist_alchemist__alchemist_answer when installed as the plugin, mcp__claude_ai_Alchemist__alchemist_answer when added as a claude.ai connector.
/alchemist:build starts a build./alchemist:status shows your account, organisation, builds and any cards waiting on you.A chat agent's diagram: where it hears from, what it checks, what it consults and how it ends.
Also on docs.olbrain.com.
Use Alchemist to build a chat agent for our website visitors. It answers pricing and
delivery questions from our FAQ, never promises discounts, and hands refunds to support@acme.com. Customers often ask: "Do you deliver on Sundays?" and "Can I change my order after paying?"
Only the beginning is shown; read the rest in the repo