skills.rest
FRIKKern
FRIKKernCOMMUNITY
Explore all skills by this author →
GitHub

doey-mcp-example

Declare MCP server dependencies in skill frontmatter for per-team isolation.

6|2|Updated Mar 15, 2026
Search Tags:#isolation#integration#mcp#config#server#skill#per-team
One-click install
npx skills add https://github.com/FRIKKern/doey --skill doey-mcp-example
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: doey-mcp-example
Source: https://github.com/FRIKKern/doey/tree/main/.claude/skills/doey-mcp-example
Command: npx skills add https://github.com/FRIKKern/doey --skill doey-mcp-example

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

MCP-based skill integrations often require per-team external server processes, isolating dependencies per team and simplifying lifecycle management.

Core Features & Use Cases

  • Declarative MCP servers: Define multiple MCP servers in the skill frontmatter and have them automatically instantiated per team.
  • Per-team isolation: Each team gets independent MCP server instances to prevent cross-team data leakage.
  • Lifecycle management: Automatic config generation, binding to launches, and cleanup when teams despawn.

Quick Start

Configure a skill with mcp_servers in frontmatter and launch the team to start per-team MCP servers.

Frequently Asked Questions about doey-mcp-example

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I isolate MCP server instances per team?▼

Per-team isolation is achieved by declaring mcp_servers in a skill's frontmatter. When a team spawns, the system generates independent per-team MCP configs and attaches them to the Claude launch.

What is the best way to manage MCP server lifecycles for multiple teams?▼

Automatic lifecycle management handles MCP servers by generating configs and binding them to launches on team spawn, then executing automatic cleanup when teams despawn.

How do I configure external MCP servers for a skill?▼

You configure external MCP servers declaratively by specifying mcp_servers in the skill's frontmatter. The runtime enforces the frontmatter schema and automatically instantiates the defined servers per team.

Does MCP per-team isolation prevent cross-team data leakage?▼

Yes, per-team isolation prevents cross-team data leakage by generating independent MCP server instances for each team. This separates external server processes and their dependencies across team boundaries.

When do I need per-team MCP config generation?▼

Per-team MCP config generation is needed when skill integrations require isolated external server processes. It simplifies dependency management by automatically binding independent configs to the team launch.

Related Skills

Explore More Software Engineering Skills→
saffron-healthsaffron-health
862

generate-spec

Generate phased specification documents from code and documentation analysis.

Official
Advanced
FRIKKernFRIKKern
6

doey-scaffy-mcp

Orchestrate per-team MCP server instances for Scaffy template tooling across workers.

Community
Intermediate
fredrick84823fredrick84823
2

implement-team-plan

Orchestrate team-plan execution with Claude Code agent teams and produce a walkthrough artifact.

Community
Advanced
claude-office-skillsclaude-office-skills
368

Monday.com Automation

Automate Monday.com workflows, board management, and cross-board integrations.

Official
Advanced