Capytail
Capytail is a local MCP capability router that selects relevant skills before loading context, enabling efficient routing without executing or loading all skills upfront.
README
Capytail
A local MCP capability router that selects relevant skills before loading context.
Capytail is a selector, not an execution gateway. It helps agents avoid loading every skill, agent, or MCP recommendation into context up front.
Status
Experimental 0.1.x.
Use it when you want:
- compact capability routing;
- read-only MCP runtime tools;
- local CLI ingestion for trusted skills;
- deterministic selection before optional full skill loading.
Do not use it as:
- an MCP proxy;
- an agent orchestrator;
- persistent memory;
- a RAG/vector database;
- a remote skill installer.
Install
npm install -g capytail
From source:
npm install
npm run build
node dist/src/cli.js --help
MCP runtime
Start the read-only MCP server:
capytail mcp
Public MCP tools:
| Tool | Purpose |
|---|---|
capytail_route |
Select relevant capabilities for a request. |
capytail_list |
List compact discovered capabilities. |
capytail_get_capability |
Fetch full content for one selected local skill/agent id. |
Normal agent flow:
capytail_route({ request })
→ capytail_get_capability({ id })
route and list return compact metadata only. They do not return full skill bodies.
CLI admin
Add a local skill after a static SkillSpector scan:
capytail add-skill ./my-skill
capytail add-skill ./my-skill --project-root . --name my-skill
capytail add-skill ./my-skill --allow-medium
The CLI uses a fixed scanner path:
$HOME/.pi/agent/tools/skillspector/.venv/bin/skillspector
--skillspector-path is intentionally rejected.
When a skill is accepted, Capytail copies it into:
.capytail/skills/<name>/
Then it enriches the copied SKILL.md with missing routing metadata:
aliases: <name>
triggers: ...
use_when: ...
It also associates the skill with the current project using the existing capability graph:
{
"graph": {
"projectId": "project:my-project",
"edges": [
{
"from": "project:my-project",
"relation": "project_has_skill",
"to": "skill:project:my-skill"
}
]
}
}
The original source skill is not modified.
Configuration
Capytail reads capytail.config.json or .capytail/config.json from the project root.
See examples/capytail.config.json.
Benchmarks
In a local corpus of 43 SKILL.md files:
| Flow | Approx tokens | Time |
|---|---|---|
| Load all skills | ~121k | n/a |
route only |
~1.0k–1.3k | ~10–15ms |
route + get |
~7.4k–40.8k | ~63–80ms |
See docs/benchmarks.md.
Security model
See SECURITY.md and docs/security-model.md.
Short version:
- MCP surface is read-only.
- Skill ingestion is CLI-only.
- Local paths only.
- Static SkillSpector scan only,
--no-llm. - No remote URL ingestion.
- No dependency installation.
- No skill execution.
Development
npm test
npm run typecheck
npm run build
License
MIT
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。