How do I install the Connect skill?

Run npx skillmds@latest add activeing123/connect in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Connect safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Connect?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Connect free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Connect?

activeing123 (@activeing123) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Connect by activeing123 — Agent Skill

Name: Connect
Author: activeing123

File contents

Connect agents to MCP servers with mcptoon

mcptoon keeps one config (~/.mcptoon/config.json) as the single source of truth for every MCP server an agent may use. It syncs that config into Claude Desktop, Claude Code, Cursor, Codex, Cline, Windsurf and VS Code, and can expose all servers through one stdio gateway (mcptoon serve).

First move: look before you change anything

mcptoon list            # what servers are configured right now
mcptoon doctor          # config syntax + connectivity diagnosis

If doctor reports problems, fix those before adding anything new.

Add servers

mcptoon discover                  # scan + probe locally installed MCP servers
mcptoon discover --write          # and write what was found into config
mcptoon add <name> --help         # see add options for stdio/http servers
mcptoon install <name> --npm @scope/pkg   # from npm
mcptoon install <name> --pip pkg          # from pip
mcptoon install <name> --url https://host/mcp   # streamable-http / sse

After editing ~/.mcptoon/config.json by hand, validate with mcptoon doctor.

Sync one config to every agent

mcptoon sync              # write config into all detected agents
mcptoon sync --dry        # preview only
mcptoon sync --agent claude   # one agent only

Expose everything through one gateway (recommended for agents)

Instead of registering N servers in an agent, register ONE:

{ "mcpServers": { "mcptoon": { "command": "mcptoon", "args": ["serve"] } } }

mcptoon serve speaks MCP over stdio and forwards to every configured server. Benefits: one entry in the agent config, tool lists stay compact, and Plugin skills appear as MCP prompts automatically.

Token efficiency flags

Tool manifests can be huge. When calling mcptoon from a terminal, keep output small on purpose:

mcptoon manifest --toon        # standard TOON format (~34% saved)
mcptoon manifest --slim        # ultra-compact schemas (93% saved)
mcptoon manifest --compact     # names only (99.2% saved)
mcptoon search <query>         # find a tool without dumping the whole manifest
mcptoon inspect <server> <tool>   # full schema for exactly one tool

Toggles

Single tools can be disabled without removing the server (agents then never see them): toggle in ~/.mcptoon/config.json on the server entry, then mcptoon sync.

Rules of thumb

Never edit agent-side config files directly; edit mcptoon's config and sync.
mcptoon watch (if running) syncs on every save.
Verify with mcptoon health — exit code 1 means something is down (CI-friendly).

---name: connectdescription: Connect any AI agent to MCP servers through mcptoon — one config synced everywhere, one stdio gateway, 99.2% fewer tokens on tool discovery.---# Connect agents to MCP servers with mcptoonmcptoon keeps one config (`~/.mcptoon/config.json`) as the single source of truthfor every MCP server an agent may use. It syncs that config into Claude Desktop,Claude Code, Cursor, Codex, Cline, Windsurf and VS Code, and can expose allservers through one stdio gateway (`mcptoon serve`).## First move: look before you change anything```bashmcptoon list # what servers are configured right nowmcptoon doctor # config syntax + connectivity diagnosis```If `doctor` reports problems, fix those before adding anything new.## Add servers```bashmcptoon discover # scan + probe locally installed MCP serversmcptoon discover --write # and write what was found into configmcptoon add <name> --help # see add options for stdio/http serversmcptoon install <name> --npm @scope/pkg # from npmmcptoon install <name> --pip pkg # from pipmcptoon install <name> --url https://host/mcp # streamable-http / sse```After editing `~/.mcptoon/config.json` by hand, validate with `mcptoon doctor`.## Sync one config to every agent```bashmcptoon sync # write config into all detected agentsmcptoon sync --dry # preview onlymcptoon sync --agent claude # one agent only```## Expose everything through one gateway (recommended for agents)Instead of registering N servers in an agent, register ONE:```json{ "mcpServers": { "mcptoon": { "command": "mcptoon", "args": ["serve"] } } }````mcptoon serve` speaks MCP over stdio and forwards to every configured server.Benefits: one entry in the agent config, tool lists stay compact, and Pluginskills appear as MCP prompts automatically.## Token efficiency flagsTool manifests can be huge. When calling mcptoon from a terminal, keep outputsmall on purpose:```bashmcptoon manifest --toon # standard TOON format (~34% saved)mcptoon manifest --slim # ultra-compact schemas (93% saved)mcptoon manifest --compact # names only (99.2% saved)mcptoon search <query> # find a tool without dumping the whole manifestmcptoon inspect <server> <tool> # full schema for exactly one tool```## TogglesSingle tools can be disabled without removing the server (agents then never seethem): toggle in `~/.mcptoon/config.json` on the server entry, then `mcptoon sync`.## Rules of thumb- Never edit agent-side config files directly; edit mcptoon's config and `sync`.- `mcptoon watch` (if running) syncs on every save.- Verify with `mcptoon health` — exit code 1 means something is down (CI-friendly).

Frequently asked questions

Connect