Lets an AI client validate, lint, diff, and convert agent skill files across multiple IDEs like Cursor, Claude, and VS Code.
Also known as ModelBound/modelbound-mcp-server, modelbound-mcp-server
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.1.2
- Last commit
- Oct 13, 2026
- License
- MIT
What is ModelBound MCP?
ModelBound lets an AI client validate, lint, diff, and convert agent skill files across multiple IDEs like Cursor, Claude, and VS Code.
Summary generated from the project's README
About ModelBound MCP server
Managing agent skills across different AI environments is what modelbound-mcp enables for developers using tools like Cursor, Claude, Windsurf, and VS Code. This local-first MCP server allows you to validate, lint, diff, and convert skill files so your rules and context remain portable between platforms. It runs locally over stdio and does not require an account or API key for basic local operations.
Users can perform offline safety scans using the flightCheck tool to detect injection risks, secrets, or destructive commands. The server also provides specialized tools like skills.convert to translate files between IDE formats and skills.lint to check for broken links or token counts. If you choose to use the optional cloud sync with a MODELBOUND_API_KEY, you gain access to cloud.pushSkill, cloud.pullSkill, and cloud.search to manage your skills across a team or multiple machines.
What you can do with it
- 1Convert skills between IDEsTranslate a rule written for Cursor into a format compatible with Claude.
- 2Perform offline safety scansRun a flight check to ensure your agent skills do not contain dangerous commands or secrets.
- 3Validate skill file complianceCheck if your skill files meet the agentskills.io formatting standards.
- 4Sync skills to the cloudPush your local agent rules to a remote repository for team access using an API key.
Written from the project's README. Every use case is checked against a quote from it.
How to install ModelBound MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall ModelBound MCP in Claude Code
$ claude mcp add --env 'MODELBOUND_API_KEY=<YOUR_MODELBOUND_API_KEY>' modelbound-mcp-server -- npx -y modelbound-mcpInstall ModelBound MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"modelbound-mcp-server": {
"command": "npx",
"args": [
"-y",
"modelbound-mcp"
],
"env": {
"MODELBOUND_API_KEY": "<YOUR_MODELBOUND_API_KEY>"
}
}
}
}Install ModelBound MCP in VS Code
.vscode/mcp.json
{
"servers": {
"modelbound-mcp-server": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"modelbound-mcp"
],
"env": {
"MODELBOUND_API_KEY": "<YOUR_MODELBOUND_API_KEY>"
}
}
}
}Install ModelBound MCP in VS Code CLI
$ code --add-mcp '{"name":"modelbound-mcp-server","type":"stdio","command":"npx","args":["-y","modelbound-mcp"],"env":{"MODELBOUND_API_KEY":"<YOUR_MODELBOUND_API_KEY>"}}'Install ModelBound MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"modelbound-mcp-server": {
"command": "npx",
"args": [
"-y",
"modelbound-mcp"
],
"env": {
"MODELBOUND_API_KEY": "<YOUR_MODELBOUND_API_KEY>"
}
}
}
}Install ModelBound MCP in Codex
$ codex mcp add modelbound-mcp-server --env 'MODELBOUND_API_KEY=<YOUR_MODELBOUND_API_KEY>' -- npx -y modelbound-mcpInstall ModelBound MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.modelbound-mcp-server] command = "npx" args = ["-y", "modelbound-mcp"] [mcp_servers.modelbound-mcp-server.env] MODELBOUND_API_KEY = "<YOUR_MODELBOUND_API_KEY>"
Install ModelBound MCP in Gemini CLI
$ gemini mcp add -s user -e 'MODELBOUND_API_KEY=<YOUR_MODELBOUND_API_KEY>' modelbound-mcp-server npx -- -y modelbound-mcpInstall ModelBound MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"modelbound-mcp-server": {
"command": "npx",
"args": [
"-y",
"modelbound-mcp"
],
"env": {
"MODELBOUND_API_KEY": "<YOUR_MODELBOUND_API_KEY>"
}
}
}
}Configuration
MODELBOUND_API_KEYSecretModelBound API key for optional cloud sync features. Get one at https://modelbound.co/settings/api-keys
| Name | Description | |
|---|---|---|
| MODELBOUND_API_KEY | ModelBound API key for optional cloud sync features. Get one at https://modelbound.co/settings/api-keys | Secret |
Automated checks
Ran Nov 13, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work
- Source repository linked and reachablemodelbound/modelbound-mcp-server is public and reachablegithub.com/modelbound/modelbound-mcp-server ↗Pass
- Package names this repository as its sourcemodelbound-mcp names modelbound/modelbound-mcp-server as sourcenpmjs.com/package/modelbound-mcp ↗Pass
- Build provenance (Sigstore attestation)No build attestation published for this releaseNot checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-10-13github.com/modelbound/modelbound-mcp-server ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNo popular package one edit away from modelbound-mcpPass
- No critical advisory in the package or its dependencies109 resolved dependencies checked; no critical advisoryosv.dev ↗Pass
- 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 handshakeNot checked
README
View on GitHubmodelbound-mcp
Local-first MCP server for agent skills. Validate, lint, diff, and convert agent skill files across Cursor, Claude, Codex, Kiro, Windsurf, VS Code, and Amazon Q — no account required. Optional cloud sync with ModelBound.
Why ModelBound?
AI tools come and go. You might use Cursor today, switch to Claude Code tomorrow, and try Kiro next week — but your skills, rules, and context shouldn't be locked into any one of them. ModelBound gives you a single place to store and manage your agent skills, so you can move between tools freely without rebuilding your setup each time. Write a skill once, sync it everywhere, and get more value out of every AI subscription you're already paying for.
What it does
modelbound-mcp is a small Model Context Protocol server you run locally over stdio. It exposes tools to your IDE / agent using dot-notation naming for navigable discovery:
Local (no API key, no network):
ide.detectLayout— find which IDE conventions your repo usesskills.listLocal,skills.readLocal,skills.writeLocalskills.lint— front-matter, token count, broken links, TODO scan, pass / warn / fail checks (scanner h5)skills.flightCheck— Flight Check offline safety scan (injection, exfiltration, secrets, destructive commands, wildcard tools, loop hazards); same rules asnpx modelbound checkskills.checks— deterministic safety/quality checks without full lint (no numeric score)skills.scaffold— create a skill with default scope constraintsskills.reviewStatus,skills.reviewRequest,skills.reviewApprove,skills.reviewReject,skills.reviewGateskills.validateFormat— agentskills.io complianceskills.convert— translate between IDE formats (e.g. Cursor → Claude)skills.diff— compare a local skill with its cloud counterpart
Cloud (with MODELBOUND_API_KEY):
cloud.pullSkill,cloud.pushSkill,cloud.searchcloud.listSkills— now acceptsai_typeandsource_platformfilters; every row includesai_type,source_platform,source_path, andrepocloud.resourceTree— returns the team's full hierarchy grouped by platform → top-level dir (.claude/skills,.cursor/rules,.kiro/steering, …) → files. Use this beforecloud.listSkillswhen an orchestrator needs to map context before loading.cloud.installMarketplaceSkilloptimization.health
Resource hierarchy
Orchestrators that juggle multiple AI platforms can call cloud.resourceTree once to get a complete map of available skills, rules, hooks, steering files, and system prompts — grouped exactly how each platform expects them on disk. Pair it with the new ai_type / source_platform filters on cloud.listSkills to load only the slice you need. See examples/resource-tree.ts.
The cloud tools are a thin JSON-RPC proxy to mcp.modelbound.co. All business logic stays server-side; this repo never touches your data or secrets.
Migration from 0.1.x — old snake_case names (
detect_ide_layout,pull_skill, …) were removed in 0.2.0. The hosted ModelBound MCP server still accepts both forms forever for backward compatibility.
Anti-slop (0.4.x) — trust scanner bumped to h5 with scope-limit, unbounded-wording, dependency, and refactor findings.
skills.readLocalnow returnschecks,scanner_version,review_state, andreview_meta. Override default scope limits via.modelbound/task-budgets.json. Useskills.reviewGatein CI to block unapproved skills.
Install
npx modelbound-mcp
Or install globally:
npm i -g modelbound-mcp
Use as an MCP server
Cursor (.cursor/mcp.json)
{
"mcpServers": {
"modelbound": {
"command": "npx",
"args": ["-y", "modelbound-mcp"],
"env": { "MODELBOUND_API_KEY": "mb_live_..." }
}
}
}
MODELBOUND_API_KEY is optional. Without it, local tools still work.
See examples/ for Claude Desktop, Kiro, Windsurf, and VS Code configs.
Use as a CLI
modelbound-mcp detect # which IDE layouts exist here?
modelbound-mcp ls # list every skill file
modelbound-mcp lint .cursor/rules/ # lint a directory
modelbound-mcp lint .codex/skills/ # lint Codex skills
modelbound-mcp validate ./SKILL.md # agentskills.io compliance
modelbound-mcp convert --from cursor --to claude ./rule.mdc > out.md
Tests
npm test # unit tests (registry parity, checks, review, harness)
npm run smoke # local MCP tools + CLI subcommands (+ cloud if MODELBOUND_API_KEY set)
npm run test:e2e # offline anti-slop / review lifecycle
CLI vs MCP tool mapping: docs/PARITY.md.
Contributing
We want help. Specifically:
- New IDE adapters — Zed, Aider, Continue, JetBrains AI, Cline. See CONTRIBUTING.md for the ~50 line recipe.
- Linter rules — token estimation accuracy, dead-link detection, format-specific gotchas.
- Format converters — fidelity improvements between adapter pairs.
Browse good first issues and the roadmap.
Related projects
| Project | Description |
|---|---|
| ModelBound CLI · npm | Terminal + CI for token optimization, skill pipeline, and version management |
| Cursor Extension · Marketplace | VS Code/Cursor extension for rules sync and MCP bridge |
| Cursor Plugin | Cursor slash commands for pipeline, safety checks, and versions |
| Claude Code Plugin | Claude Code plugin for pipeline, hooks, and skill sync |
| Dev Packs | Open-source curated AI context packs for engineering teams |
Also on Smithery (stdio via npx modelbound-mcp) and the MCP Registry. Install hub: modelbound.co/connect
License
MIT © ModelBound
ModelBound MCP questions
How do I add ModelBound MCP to Claude Code?
Run claude mcp add --env 'MODELBOUND_API_KEY=<YOUR_MODELBOUND_API_KEY>' modelbound-mcp-server -- npx -y modelbound-mcp in your terminal. Add --scope user to make it available in every project.
How do I add ModelBound MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Can I use ModelBound without an API key?
Yes, the local tools work without an API key, though cloud features require one.
What IDEs does it support?
It supports Cursor, Claude, Codex, Kiro, Windsurf, VS Code, and Amazon Q.
How can I sync my skills across different AI tools?
ModelBound allows you to write a skill once and sync it across different platforms to avoid being locked into one IDE.