Vapi MCP

🚀 Vapi MCP Implementation for Cursor

This project implements a Model Context Protocol (MCP) server that integrates Vapi's voice AI capabilities with Cursor.

🚀 Quick Start

Project Structure

The structure of the Vapi MCP server is as follows:

• vapi-mcp-server/ - Main server code
  • src/ - TypeScript source files
  • dist/ - Compiled JavaScript output
  • .env - Environment variable file (for API keys)

Environment Configuration

Create a .env file in the vapi-mcp-server directory with the following variables:

# Vapi API keys
VAPI_ORG_ID=your-org-id
VAPI_PRIVATE_KEY=your-private-key
VAPI_KNOWLEDGE_ID=your-knowledge-id
VAPI_JWT_PRIVATE=your-jwt-private

# Environment configuration
NODE_ENV=development

Server Building

To build the server:

cd vapi-mcp/vapi-mcp-server
npm install
npm run build

Configuration in Cursor

⚠️ Important Note

When configuring the Vapi MCP server in Cursor's MCP settings, please note the following important points:

1. Working Directory: The cwd parameter is required to ensure the server runs in the correct directory and can access the .env file correctly.
2. Environment Variables: Even if a .env file exists, you must explicitly provide the environment variables in the configuration.
3. Module Type: Since the server uses ES modules, "type": "module" must be included in package.json.

Here is an example of the correct .cursor/mcp.json configuration:

"Vapi Voice AI Tools": {
  "command": "node",
  "type": "stdio",
  "args": [
    "/Users/matthewcage/Documents/AA-GitHub/MCP/vapi-mcp/vapi-mcp-server/dist/index.js"
  ],
  "cwd": "/Users/matthewcage/Documents/AA-GitHub/MCP/vapi-mcp/vapi-mcp-server",
  "env": {
    "VAPI_ORG_ID": "your-org-id",
    "VAPI_PRIVATE_KEY": "your-private-key",
    "VAPI_KNOWLEDGE_ID": "your-knowledge-id",
    "VAPI_JWT_PRIVATE": "your-jwt-private",
    "NODE_ENV": "development"
  }
}

📚 Documentation

Troubleshooting

"Client has closed" Error in Cursor

If you see "Client has closed" in Cursor's MCP tool panel:

1. Check Working Directory: Ensure the cwd parameter is set correctly in your mcp.json.
2. Verify Environment Variables: Confirm that all required environment variables are passed through the configuration.
3. Check Module Type: Ensure package.json contains "type": "module".
4. Check Permissions: Ensure the dist/index.js file has executable permissions (use chmod +x dist/index.js).
5. Test the Server Directly: Try running the server manually to check for errors:

cd vapi-mcp/vapi-mcp-server
node --trace-warnings dist/index.js

"Error: Cannot find module"

If you encounter "Error: Cannot find module":

1. Check Working Directory: Are you running in the correct directory?
2. Rebuild: Try rebuilding the project with npm run build.
3. Dependencies: Ensure all dependencies are installed (use npm install).

Available Tools

The tools provided by the Vapi MCP server include:

• vapi-mcp-server/src/index.ts - The main server file for listening and handling requests.
• vapi-mcp-server/dist/index.js - The compiled main executable file.

💡 Usage Tip

1. Ensure all environment variables are set correctly, and the .env file is located in the project root directory.
2. Before using it in a production environment, ensure the server has been fully tested and configured with appropriate error handling and logging mechanisms.
3. If you encounter any issues or have further questions, refer to Vapi's official documentation or contact the support team.

By following the above steps, you can successfully integrate Vapi's voice AI capabilities with Cursor and use the MCP protocol for data interaction.