feat: restructure as Claude Code plugin

Add plugin manifest (.claude-plugin/plugin.json) and bundled MCP
server config (.mcp.json) so users get both the skill and MCP server
in one install. Move skill files to skills/vapi/ to match the plugin
convention and remove the manual MCP install step from the workflow.

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>

Author: lukatmyshu

.claude-plugin/plugin.json

@@ -0,0 +1,15 @@
+{
+  "name": "vapi",
+  "description": "Build AI voice assistants and phone agents with Vapi",
+  "version": "0.0.10",
+  "author": {
+    "name": "Vapi AI",
+    "url": "https://vapi.ai"
+  },
+  "homepage": "https://github.com/VapiAI/mcp-server#readme",
+  "repository": "https://github.com/VapiAI/mcp-server",
+  "license": "MIT",
+  "keywords": ["vapi", "voice", "ai", "phone", "assistant", "mcp"],
+  "mcpServers": "./.mcp.json",
+  "skills": "./skills/"
+}

.mcp.json

@@ -0,0 +1,8 @@
+{
+  "mcpServers": {
+    "vapi": {
+      "command": "node",
+      "args": ["${CLAUDE_PLUGIN_ROOT}/dist/index.js"]
+    }
+  }
+}

package.json

@@ -49,7 +49,9 @@
     "dist",
     "dist/**/*.d.ts",
     "dist/**/*.d.ts.map",
-    "skill"
+    ".claude-plugin",
+    ".mcp.json",
+    "skills"
   ],
   "dependencies": {
     "@modelcontextprotocol/sdk": "^1.12.3",

skill/PROMPT_GUIDE.md skills/vapi/PROMPT_GUIDE.mdskill/PROMPT_GUIDE.md renamed to skills/vapi/PROMPT_GUIDE.md

@@ -11,27 +11,17 @@ Build AI-powered voice assistants, phone agents, and conversational AI applicati
 
 When a user wants to build a voice assistant or phone agent, follow these steps:
 
-### Step 1: Check if Vapi MCP is Installed
-
-First, check if the Vapi MCP server is available by looking for `vapi_` tools. If not available, tell the user to run:
-
-```bash
-claude mcp add vapi -- npx -y @vapi-ai/mcp-server
-```
-
-Then restart Claude Code and continue with Step 2.
-
-### Step 2: Authenticate with Vapi
+### Step 1: Authenticate with Vapi
 
 If the user hasn't authenticated yet (tools return auth errors):
 
 1. Call `vapi_login` to start the OAuth flow
 2. Tell the user to open the provided URL and sign in
 3. Once authenticated, proceed with their request
 
-### Step 3: Build the Voice Assistant
+### Step 2: Build the Voice Assistant
 
-Before creating an assistant, read the prompt engineering guidelines from the MCP resource `vapi://prompt-guide` (available from the Vapi MCP server).
+Before creating an assistant, read the prompt engineering guidelines from the MCP resource `vapi://prompt-guide` from server `plugin:vapi:vapi` (use `ReadMcpResourceTool` with server `plugin:vapi:vapi` and uri `vapi://prompt-guide`).
 
 Use these guidelines to craft effective voice assistant prompts based on what the user wants to build.
 
@@ -70,19 +60,18 @@ Use these guidelines to craft effective voice assistant prompts based on what th
 **User:** "I want to build a voice assistant that can schedule appointments"
 
 **Claude should:**
-1. Check for Vapi MCP -> install if needed
-2. Authenticate if needed
-3. Read the prompt guide resource for best practices
-4. Ask about their business to understand context
-5. Create an assistant with a scheduling-focused prompt
-6. Offer to set up a phone number
-7. Help create calendar integration tools if needed
+1. Authenticate if needed
+2. Read the prompt guide resource for best practices
+3. Ask about their business to understand context
+4. Create an assistant with a scheduling-focused prompt
+5. Offer to set up a phone number
+6. Help create calendar integration tools if needed
 
 **User:** "Make me a phone bot that answers questions about my business"
 
 **Claude should:**
-1. Ensure Vapi MCP is installed and authenticated
-2. Fetch the prompt guide for best practices
+1. Authenticate if needed
+2. Read the prompt guide resource for best practices
 3. Ask about the business: name, services, hours, common questions
 4. Craft a system prompt following the guidelines
 5. Create the assistant

skill/SKILL.md skills/vapi/SKILL.mdskill/SKILL.md renamed to skills/vapi/SKILL.md

@@ -136,7 +136,7 @@ function createMcpServer() {
     'vapi://prompt-guide',
     { description: 'Voice assistant prompt engineering guide with best practices for crafting Vapi assistant prompts', mimeType: 'text/markdown' },
     async (uri) => {
-      const guidePath = join(__dirname, '..', 'skill', 'PROMPT_GUIDE.md');
+      const guidePath = join(__dirname, '..', 'skills', 'vapi', 'PROMPT_GUIDE.md');
       const content = readFileSync(guidePath, 'utf-8');
       return {
         contents: [{ uri: uri.href, text: content }],