plugins/kronen/skills/mcp-creator/SKILL.md
Create and configure MCP server integrations for Claude Code plugins. Use when adding external service connections, setting up .mcp.json, configuring stdio/SSE/HTTP/WebSocket servers, integrating MCP tools into commands and agents, debugging MCP server connectivity issues, adding tool annotations, or configuring OAuth and API key authentication for MCP servers.
npx skillsauth add hjemmesidekongen/ai mcp-creatorInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Create and configure MCP server integrations for Claude Code plugins.
.mcp.json configuration| Type | Transport | Best for | Auth method | |------|-----------|----------|-------------| | stdio | Child process (stdin/stdout) | Local tools, custom servers, NPM packages | Env vars | | sse | HTTP + Server-Sent Events | Hosted services, cloud APIs | OAuth (auto) | | http | REST requests | API backends, token auth | Bearer/API key | | ws | WebSocket | Real-time streaming, low-latency | Bearer/headers |
| Method | Location | When to use |
|--------|----------|-------------|
| .mcp.json | Plugin root | Multiple servers, clean separation (recommended) |
| mcpServers in plugin.json | .claude-plugin/plugin.json | Single server, simple plugins |
Format: mcp__plugin_<plugin-name>_<server-name>__<tool-name>
Pre-allow specific tools in command frontmatter via allowed-tools. Avoid wildcards.
Add hints so Claude reasons about safety: readOnlyHint, destructiveHint, idempotentHint, openWorldHint. After build + tests pass, create evaluation.xml with 10 read-only Q&A pairs. Full process: references/process.md.
development
Creates a brand from scratch through market research and interactive sparring. Runs competitive research via Perplexity, then guides the user through positioning, audience, voice, values, and content pillars. Produces the full brand guideline set at .ai/brand/{name}/. Use when building a new brand, defining brand strategy for a product, or when /våbenskjold:create is invoked.
testing
Loads brand guidelines from .ai/brand/{name}/ and makes them available to the current context. Progressive disclosure: L1 confirms brand exists, L2 loads summary, L3 loads specific files on demand. Use when a downstream skill or user needs brand context, or when /våbenskjold:apply is invoked.
documentation
Guided reinvention of an existing brand guideline. Loads current brand from .ai/brand/{name}/, identifies what to keep vs change, and walks the user through targeted evolution. Preserves brand equity while updating positioning, voice, or values. Use when refreshing a brand or when /våbenskjold:evolve is invoked.
development
Codifies an existing brand from materials, samples, and references. Analyzes provided content to extract voice patterns, values, and positioning. Produces the same guideline format as brand-strategy. Use when a brand already exists but isn't documented, or when /våbenskjold:audit is invoked.