Toolcapsule

Skill RainSunMe/toolcapsule/skills/toolcapsule

File-first, patchable Agent Skills for heavy MCP tools

Install

npx -y skills add RainSunMe/toolcapsule --skill toolcapsule

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

2 stars2 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Use when: turning MCP servers into lazy Agent Skills, calling MCP tools with inline JSON or local files, or looking up MCP tool schemas on demand.

SKILL.md

2.7 KB, as published. Nobody here has run it

ToolCapsule

ToolCapsule converts heavy MCP tools into compact, lazy-loaded Agent Skills. MCP stays the capability layer; Skills become the agent-facing workflow layer.

Getting started (Agent reads this first)

Check if the tcap CLI is available. If not, install it:

npm install -g toolcapsule
tcap --version

Now you can use the commands below to register MCP servers and call their tools.

Core workflow

1. Register an MCP server and generate a Skill

# Remote MCP
tcap init <profile-name> --url <mcp-url> --target claude

# Local stdio MCP
tcap init <profile-name> --command <cmd> --arg <arg> --target claude

This creates:

~/.toolcapsule/profiles/<profile-name>.json (transport config — never commit)
Skills directory with SKILL.md (safe to commit)

Supported targets: agents (default), copilot, claude, opencode, all.

2. Read the generated SKILL.md

The Skill contains a compact tool summary. Always prefer it over loading full MCP schemas.

3. Look up detailed schema on demand

tcap tools <profile>                 # compact one-line summary
tcap tools <profile> --names         # tool names only
tcap tools <profile> --json          # raw JSON
tcap schema <profile> <tool>         # compact schema for one tool

4. Call tools with inline JSON or /tmp files

# Use inline JSON for simple args
tcap call <profile> <tool> '{"key":"value"}'

# Use /tmp files for larger or frequently patched args (never the workspace)
tcap call <profile> <tool> @/tmp/tcap-<profile>-<tool>.json

# Save response to a file (avoids large responses flooding context)
tcap call <profile> <tool> @/tmp/tcap-<profile>-<tool>.json -o /tmp/tcap-<profile>-response.json

If a file-based call fails, edit the args file and re-run the same command. For simple one-off calls, inline JSON is fine.

Profile management

Profiles are stored in ~/.toolcapsule/profiles/ only. They contain transport config (URLs, commands, credentials) and must never be committed to a repository.

List profiles:

ls ~/.toolcapsule/profiles/

Safety

Never print or commit MCP URLs, tokens, API keys, or credentials.
For large, sensitive, or retryable payloads, write call args to /tmp, never to the workspace.
Profile JSON files in ~/.toolcapsule/profiles/ are private — do not read their contents to the user.
Set TOOLCAPSULE_DEBUG=1 only for debugging stderr output.