mcp-server-creator

The McpServer Creator skill provides a structured workflow for defining Model Context Protocol (MCP) server configurations within the Stigmer ecosystem. It is designed for engineers, platform architects, and developers who need to bridge AI agents with external systems such as GitHub, Slack, databases, or proprietary APIs. By strictly adhering to the agentic.stigmer.ai/v1 API, this skill ensures that your resource definitions are syntactically valid, secure, and production-ready from the start.

The skill guides you through the entire lifecycle of an MCP resource, from selecting the appropriate transport layer—whether stdio for CLI tools or http for managed services—to defining robust environment variable contracts and human-in-the-loop safety policies. It eliminates common configuration errors like misconfigured secret handling, incorrect naming conventions, or missing tool validation steps, effectively streamlining the operational setup of agentic workflows.

• Define server transport types: Select between stdio (npx, uvx, binary) or http (API gateway, remote URL) to suit your backend infrastructure.

• Manage environment variables: Explicitly map sensitive credentials and configuration parameters with clear descriptions, preventing runtime errors.

• Implement security and safety: Configure default tool enablement and mandatory human approval chains to ensure sensitive operations remain controlled.

• Streamline agent integration: Learn how to bind your McpServer to specific Agent instances for modular and reusable tool access.

• Use this skill when you need to create or update an McpServer resource defined in YAML.

• Provide context on the target external system, preferred transport (stdio/http), and required tools to receive an optimized configuration.

• Pay close attention to the validation rules; ensure that secrets are never hardcoded and that approval messages use the correct placeholder syntax for dynamic context injection.

• After applying the generated YAML, use the stigmer discover mcp-server command to automatically update tool metadata.

• The output is expected to be a ready-to-deploy YAML file compatible with the stigmer apply command, focusing on clean separation of concerns between server configuration and agent usage requirements.