BotKelp MCP server
Commit Oct 29, 2026Allows AI agents to browse a verified component catalog and retrieve specific code artifacts or scaffolds based on version and compatibility rules.
Also known as botkelp/components, components
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.1.0
- Last commit
- Oct 29, 2026
- License
- —
What is BotKelp MCP?
BotKelp allows AI agents to browse a verified component catalog and retrieve specific code artifacts or scaffolds based on version and compatibility rules.
Summary generated from the project's README
About BotKelp MCP server
Retrieving verified code artifacts and scaffolds for specific software stacks is what BotKelp enables for AI agents. Developers use this remote HTTP MCP server to browse a component catalog and fetch individual files like navbars, Supabase clients, or Tailwind configurations. The server manages complex compatibility rules by checking component manifests against specific versions of frameworks like Next.js or React to ensure the requested code works with the existing environment.
To use the server, agents connect via a remote HTTP endpoint and must authenticate using MCP OAuth or a live API key provided in the Authorization header. The system provides tools such as get_help and search_components to identify component IDs. While it can return individual templates, it also supports the purchase_scaffold command to build full applications using account credits. The server handles versioning through immutable semver, allowing agents to request specific releases or let the system auto-select the best compatible version for a given stack.
What you can do with it
- 1Find compatible code componentsAsk the agent to search for a component that works with a specific version of Next.js and React.
- 2Generate a full application scaffoldInstruct the agent to build a complete project by wiring several components together using account credits.
- 3Retrieve specific file templatesRequest the source files for a specific component to manually integrate them into a local project.
- 4Verify component dependenciesHave the agent check the manifest of a component to see which npm packages and environment variables are required.
Written from the project's README. Every use case is checked against a quote from it.
How to install BotKelp MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall BotKelp MCP in Claude Code
$ claude mcp add --transport http components https://www.botkelp.com/mcpInstall BotKelp MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"components": {
"url": "https://www.botkelp.com/mcp"
}
}
}Install BotKelp MCP in VS Code
.vscode/mcp.json
{
"servers": {
"components": {
"type": "http",
"url": "https://www.botkelp.com/mcp"
}
}
}Install BotKelp MCP in VS Code CLI
$ code --add-mcp '{"name":"components","type":"http","url":"https://www.botkelp.com/mcp"}'Install BotKelp MCP in Codex
$ codex mcp add components --url https://www.botkelp.com/mcpInstall BotKelp MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.components] url = "https://www.botkelp.com/mcp"
Install BotKelp MCP in Gemini CLI
$ gemini mcp add -s user --transport http components https://www.botkelp.com/mcpInstall BotKelp MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"components": {
"url": "https://www.botkelp.com/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablebotkelp/components is public and reachablegithub.com/botkelp/components ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearLast commit or release 2026-10-29github.com/botkelp/components ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 450 msPass
README
View on GitHubBotKelp components
Public source for the individual components BotKelp actually uses.
You can browse, copy, and reuse these files. That is the point of this repository.
What we are providing
Each folder under components/ is one component:
manifest.json— id, immutable semver,requires/provides,compatibilityranges, npm packages, and generator actionstemplates/— the files the generator applies (EJS templates; most are plain source with no templating)versions/<semver>/(optional) — additional immutable releases. The top-levelmanifest.jsonis always the latest. Older releases live underversions/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:
- Exact version + compatible → returns that artifact
- Exact version + incompatible →
COMPONENT_VERSION_INCOMPATIBLEplus alternatives — no files - No version → auto-selects the best compatible release
allow_incompatible: true→ returns the pin with a warning; stillcompatible: false
The 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.
What we are not providing
- Not a complete application. Cloning this repo will not give you a running site.
- Not assembled / generated project builds. Scaffolds built by the BotKelp MCP tool
purchase_scaffold(a full app with several components already wired together) are not published here. - Not the BotKelp service. The MCP server, billing, accounts, and generation engine live elsewhere and are not in this repository.
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.
How to copy a component
- Open
components/<id>/. - Read
manifest.jsonfor npm packages and env vars. - Copy the files under
templates/into your app at thedestinationpaths listed in the manifest. - Install the listed
dependencies/devDependencies. - Respect the licences of any upstream library the component wraps (Next.js, Tailwind, shadcn/ui, Supabase, and so on). Those remain their own.
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.
Licence
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.
Site
The registry on the BotKelp website shows the same components, with copyable file contents. repo: https://github.com/botkelp/components
BotKelp MCP questions
How do I add BotKelp MCP to Claude Code?
Run claude mcp add --transport http components https://www.botkelp.com/mcp in your terminal. Add --scope user to make it available in every project.
How do I add BotKelp MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
How does the server handle version compatibility?
The server checks the requested version against compatibility ranges; if incompatible, it returns an error and alternatives instead of files.
Can I use this repository to run a complete application?
No, the repository contains individual components and templates, not a complete or assembled application build.
How do I authenticate with the BotKelp MCP server?
You can sign in using MCP OAuth or provide a live API key via an Authorization Bearer header.