From be-experts
Scaffold an MCP server with stdio/HTTP transports, resource/tool/prompt definitions with Zod schemas
npx claudepluginhub justn-hyeok/harness-for-yall --plugin be-expertsThis skill uses the workspace's default tool permissions.
Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Facilitates interactive brainstorming sessions using diverse creative techniques and ideation methods. Activates when users say 'help me brainstorm' or 'help me ideate'.
Build a Model Context Protocol server with proper transport, schema validation, and tool/resource definitions.
Architecture (be-architect): Design MCP server structure
.claude/specs/be-mcp-{name}.mdImplementation (be-implementer): Build the server
Validation (be-validator): Schema enforcement
Testing (be-tester): Contract tests
$ARGUMENTS.name — Server name$ARGUMENTS.capabilities — tools, resources, prompts (default: tools)$ARGUMENTS.transport — stdio, http, or both (default: stdio)import { McpServer } from '@modelcontextprotocol/sdk/server/mcp.js';
import { StdioServerTransport } from '@modelcontextprotocol/sdk/server/stdio.js';
import { z } from 'zod';
const server = new McpServer({
name: '$ARGUMENTS.name',
version: '1.0.0',
});
// Register tools
server.tool('tool-name', 'Description', {
input: z.object({ query: z.string() }),
}, async ({ input }) => {
// Implementation
return { content: [{ type: 'text', text: 'result' }] };
});
// Start server
const transport = new StdioServerTransport();
await server.connect(transport);
Start by spawning be-architect with:
Design an MCP server: $ARGUMENTS.name
Capabilities: ${ARGUMENTS.capabilities || "tools"}
Transport: ${ARGUMENTS.transport || "stdio"}
Requirements:
- Use @modelcontextprotocol/sdk
- Zod schemas for all tool inputs
- Proper error handling with MCP error codes
- pino logging (stderr for stdio transport)
Provide the server spec, then delegate:
1. be-implementer for server implementation
2. be-validator for input/output schemas (parallel)
3. be-tester for tool invocation tests