mcp-workbench-developer

Update my-agents MCP servers, agent isolation, and workbench startup flow.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/spigell/my-agents --skill mcp-workbench-developer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-workbench-developer
Source: https://github.com/spigell/my-agents/tree/main/.agents/skills/mcp-workbench-developer
Command: npx skills add https://github.com/spigell/my-agents --skill mcp-workbench-developer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires curl, awk, seq, sed, jq, tr, grep, node, and includes scripts (resource) components.

What problem does it solve?

It streamlines updates to the repo-managed MCP servers, agent isolation/wiring, and workbench startup/reload flow so changes reliably take effect without guesswork or brittle manual steps.

Core Features & Use Cases

  • MCP runtime and workbench wiring updates: Adjust shared MCP server lifecycle behavior and protocol expectations for the workbench environment.
  • Agent isolation and credential-linking correctness: Ensure agent-specific adapters, isolation rules, and auth/credential injection behavior match deployment reality.
  • Reload and sync verification: Align workbench startup, reload, and repo-managed sync logic so runtime configuration is present before tools are called.

Use cases include updating shared MCP tool contracts, fixing agent-specific MCP integration behavior, or modifying workbench startup/reload logic for a new or migrated MCP endpoint.

Quick Start

Use this skill when you need to update MCP servers, agent isolation/credentials, or the workbench startup flow for my-agents by editing the repo-managed MCP runtime and wiring.

Frequently Asked Questions about mcp-workbench-developer

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

FAQPage Schema
How do I update MCP server lifecycle behavior without redeploy guesswork?

Agent isolation and credential injection are configured by adjusting agent-specific adapters, isolation rules, and auth wiring. This ensures agent-specific MCP integration behavior matches deployment reality.

Does the workbench reload flow preserve the FastMCP HTTP stream model?

Yes, the workbench reload flow preserves the FastMCP HTTP stream model at the /mcp endpoint. It honors the expected initialize handshake, including the Accept header, and validates via targeted builds and MCP calls.

Why does my MCP tool contract fail during workbench startup?

MCP tool contracts may fail if workbench startup, reload, and repo-managed sync logic are misaligned. Aligning these processes ensures runtime configuration is present before tools are called, preventing failures.

Can I use shell scripting tools to modify workbench reload and sync logic?

Yes, you can use shell tools like curl, awk, sed, jq, and node to modify workbench reload and sync logic. These dependencies support editing the repo-managed MCP runtime and validating runtime behavior.