Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Verified component catalog over remote MCP: agents pick ids and get a project that builds.
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://www.botkelp.com/mcpRun this in your terminal
claude mcp add --transport http botkelp https://www.botkelp.com/mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"botkelp": {
"url": "https://www.botkelp.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": {
"botkelp": {
"type": "http",
"url": "https://www.botkelp.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://www.botkelp.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.
Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.
get_helpFree. Short usage index. Then search_components to pick ids.
search_componentsFree. Compact catalog TSV: id, provides, requires, conflictsWith. Omit args for all.
get_componentOne component's source files, UNRENDERED (EJS markers, not build-ready): inspect only; use purchase_scaffold for real files. Free, 32/day, signed-in account.
purchase_scaffoldBuys a CI-green starter repo for component ids (credits via your signed-in account, or x402). Returns a git clone command and projectid. Red builds are refused and not charged. delivery "inline" returns files instead (more tokens).
get_scaffoldRefetches a scaffold you purchased (fresh clone command), no extra credits. Credit-flow projects need Maintain on. Same site_profile/delivery options as purchase_scaffold.
get_projectsLists this account's saved scaffold projects (id, name, description, repo, components, maintain state). Use the projectid with get_scaffold to re-fetch a scaffold — no project_api_key is needed as a tool argument.
set_projectsTurn Maintain on/off for a project and/or rotate its project key. Off keeps existing clones; it stops future get_scaffold access.
get_siteprofileYour site profiles (privacy, terms, cookies, licence, custom_field) as JSON. list: true for names, or siteprofilename for one; field filters. Use next.arguments when a purchase reply says incomplete: true.
set_siteprofileCreates or updates one named site profile for this account. Fields omitted from `field` keep their current saved value (or blank, if the profile is new); pass only what changed. custom_field entries are merged key-by-key. An account may keep more than one named profile (e.g. one
get_adminpagesetLists this account's admin page set names (omit name), or returns one set's exact files (pass name). These are the file trees purchase_scaffold's admin_page_set param bakes into a dedicated forked repo. Requires a linked account (transport auth).
set_adminpagesetCreates or fully replaces one named admin page set for this account — real file source (React/Next.js), not text config. purchase_scaffold's admin_page_set param bakes a chosen set into a brand-new, dedicated repo. An account may keep more than one named set.
verify_scaffoldRemote `npm install && npm run build` of your edited files (send every file). Call with files -> WAIT + jobId; call again with jobId -> OK or FAIL with the error tail. Needs a purchased projectid.
report_issueReport a catalog/code bug or request a component (files an issue on botkelp/components). Signed-in account, 10/day. No secrets.
get_githubShows whether this account has a GitHub repo connected, or lists files under a path in that repo. If not connected, the result includes installUrl — open it (GitHub App) to grant read access to one repo. Sign in on botkelp.com with GitHub first so the install is tied to your acco
set_githubReturns a GitHub App install URL so the user can grant BotKelp read access to one of their repos. Open the URL, pick a single repo, approve. Then purchase_scaffold template_files: [{ source: "app/legal/" }] copies those pages into the clone. disconnect: true drops the connection.
get_account_statusNo params. Says whether you are signed in (authenticated) and account tools work (accountToolsReady). Never returns a key.
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 8, 2026
The publisher (aiscimi-code) is not the repo owner (botkelp); someone else may have listed it
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 677 ms (HTTP 200)
No sign-in needed
Read 16 tool descriptions and found no hidden instructions to the AI
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 2 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 (1.1.0) reached the registry 17 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, A1RO — Irish employment tools
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.
Irish temp worker cost, public holiday pay and holidays, and SafeHandle certificate checks.
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.
Public source for the individual components BotKelp actually uses.
You can browse, copy, and reuse these files. That is the point of this repository.
Each folder under components/ is one component:
manifest.json — id, immutable semver, requires / provides, compatibility ranges, npm packages, and generator actionstemplates/ — the files the generator applies (EJS templates; most are plain source with no templating)versions/ / (optional) — additional immutable releases. The top-level manifest.json is always the latest. Older releases live under versions/ so shipping 2.0.2 never overwrites 1.4.2.compatibility is a hard registry rule, not something an agent should guess. Example:
"compatibility": { "nextjs": ">=16 <17", "react": ">=19 <20" }
BotKelp MCP looks up (component, version, stack) and:
COMPONENT_VERSION_INCOMPATIBLE plus alternatives — no filesallow_incompatible: true → returns the pin with a warning; still compatible: falseThe same list is in CATALOG.md and catalog.json.
This repository is the source of truth for BotKelp's component catalog. The MCP generator and website load these files (not a private copy). It is not a demo and not a cleaned-up excerpt.
purchase_scaffold (a full app with several components already wired together) are not published here.If you want a generated project, connect your agent to the BotKelp MCP server at https://www.botkelp.com/mcp (remote HTTP; there is no npm package or stdio server), call get_help and search_components to pick component ids, then call purchase_scaffold. Building uses account credits (sign in with MCP OAuth, or send a bk_live_ key from https://www.botkelp.com/dashboard as an Authorization: Bearer header; never as a tool argument), and you are only charged when the build passes. Setup for each client: https://www.botkelp.com/llms.txt
If you want to copy a navbar, a Supabase client, or Tailwind config, use this repo.
components/ /.manifest.json for npm packages and env vars.templates/ into your app at the destination paths listed in the manifest.dependencies / devDependencies.nextjs-base is the base component the others sit on. It is still one component, not a product app we ship as a complete build.
BotKelp-authored files are under the BotKelp Limited Use Licence.
INTLEACHT RESEARCH LIMITED trading as BotKelp is named on every file. You may copy individual component source into your own projects. You may not present this catalog or the generator as your own product, and you may not strip operator attribution from files as published here.
Third-party projects named in a component keep their own licences. Copying a component does not re-licence Next.js, Tailwind, Prisma, or anything else.
The registry on the BotKelp website shows the same components, with copyable file contents. repo: https://github.com/botkelp/components