Capytail
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Capytailroute this request: write a Python script"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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.
Related MCP server: skills-mcp-server
Install
npm install -g capytailFrom source:
npm install
npm run build
node dist/src/cli.js --helpMCP runtime
Start the read-only MCP server:
capytail mcpPublic MCP tools:
Tool | Purpose |
| Select relevant capabilities for a request. |
| List compact discovered capabilities. |
| 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-mediumThe 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 |
| ~1.0k–1.3k | ~10–15ms |
| ~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 buildLicense
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/juancruzmunozalbelo/capytail'
If you have feedback or need assistance with the MCP directory API, please join our Discord server