Workspace Initialization

Initialize MCP Server workspaces after verifying trusted markers and paths.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/sharpninja/mcpserver-copilot-plugin --skill workspace-initialization
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Workspace Initialization
Source: https://github.com/sharpninja/mcpserver-copilot-plugin/tree/main/skills/workspace
Command: npx skills add https://github.com/sharpninja/mcpserver-copilot-plugin --skill workspace-initialization

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents duplicate or untrusted MCP workspace registration by verifying existing markers and only then initializing the workspace.

Core Features & Use Cases

  • Trusted workspace verification: Validates an existing target marker with full_bootstrap and ensures credentials only come from a trusted control workspace marker.
  • Workspace discovery and conditional creation: Lists workspaces, matches the target path case-insensitively after normalization, creates the workspace only if missing, and then initializes scaffolding.
  • Post-init validation and guarded writes: Re-validates AGENTS-README-FIRST.yaml and required bootstrapping steps before resuming session logs, TODO, and requirements writes.

Quick Start

Ask the assistant to initialize workspace at the target path you want to register, and it will verify markers, create if missing, run workspace init, and only then proceed with plugin bootstrap writes.

Frequently Asked Questions about Workspace Initialization

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

FAQPage Schema
How do I bootstrap an MCP workspace safely without registering duplicates?

To bootstrap an MCP workspace safely, the workspace path is discovered via Workspace.ListAsync and matched case-insensitively after normalization. This prevents duplicate registrations by verifying existing markers before initialization.

What is marker validation for MCP workspace initialization?

Marker validation for MCP workspace initialization is the process of verifying an existing target marker with full_bootstrap to ensure credentials only come from a trusted control workspace marker. This mechanism prevents untrusted workspace registration.

How do I initialize an MCP server workspace if the path is not already registered?

To initialize an unregistered MCP server workspace, the target path undergoes absolute path resolution, followed by conditional Workspace.CreateAsync if missing, and then Workspace.InitAsync to scaffold the environment.

Why does MCP workspace initialization require a Base64URL key?

MCP workspace initialization requires a Base64URL key computed from the exact absolute workspacePath to securely identify and validate the workspace during the registration and bootstrap lifecycle.

When should I not use automated MCP workspace initialization?

You should not use automated MCP workspace initialization if the target path cannot be resolved to an absolute path or if post-init AGENTS-README-FIRST.yaml verification fails, as guarded writes require successful validation first.

Can I write plugins immediately after running Workspace.InitAsync?

No, you cannot write plugins immediately after Workspace.InitAsync. The system must first re-validate AGENTS-README-FIRST.yaml and required bootstrapping steps before resuming session logs, TODO, and guarded plugin writes.