Server data from the Official MCP Registry
Local-first MCP server for agent skills. Validate, lint, diff, and convert across IDEs.
Local-first MCP server for agent skills. Validate, lint, diff, and convert across IDEs.
This is a well-structured MCP server for local skill file management with optional cloud sync. Authentication and authorization are properly handled: local tools require no credentials and work offline, while cloud tools properly gate access behind `MODELBOUND_API_KEY` checks. Path traversal is mitigated with the `inside()` function. Minor code quality issues exist (broad exception handling, weak input validation on some cloud tool parameters) but do not present security risks. Permissions appropriately match the server's purpose. Supply chain analysis found 2 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.
7 files analyzed · 7 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: MODELBOUND_API_KEY
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-modelbound-modelbound-mcp": {
"env": {
"MODELBOUND_API_KEY": "your-modelbound-api-key-here"
},
"args": [
"-y",
"modelbound-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
Local-first MCP server for agent skills. Validate, lint, diff, and convert agent skill files across Cursor, Claude, Kiro, Windsurf, VS Code, and Amazon Q — no account required. Optional cloud sync with 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.
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 (per the Smithery quality guidelines):
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 scanskills.validateFormat — agentskills.io complianceskills.convert — translate between IDE formats (e.g. Cursor → Claude)skills.diff — compare a local skill with its cloud counterpartCloud (with MODELBOUND_API_KEY):
cloud.pullSkill, cloud.pushSkill, cloud.searchcloud.listSkills — now accepts ai_type and source_platform filters; every row includes ai_type, source_platform, source_path, and repocloud.resourceTree — returns the team's full hierarchy grouped by platform → top-level dir (.claude/skills, .cursor/rules, .kiro/steering, …) → files. Use this before cloud.listSkills when an orchestrator needs to map context before loading.cloud.installMarketplaceSkilloptimization.healthOrchestrators 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.
npx modelbound-mcp
Or install globally:
npm i -g modelbound-mcp
.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.
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 validate ./SKILL.md # agentskills.io compliance
modelbound-mcp convert --from cursor --to claude ./rule.mdc > out.md
We want help. Specifically:
Browse good first issues and the roadmap.
| 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, trust & safety, 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
MIT © ModelBound
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
by mcp-marketplace · Developer Tools
Create, build, and publish Python MCP servers to PyPI — conversationally.