Vapi MCP Server

Created By
andyciggya year ago
Overview

what is Vapi MCP Server?

Vapi MCP Server is a server that allows integration with Vapi APIs through function calling, enabling developers to create and manage assistants and calls using the Model Context Protocol.

how to use Vapi MCP Server?

To use the Vapi MCP Server, set up the Claude Desktop application, configure it with your Vapi API key, and follow the provided instructions to create and manage assistants and calls.

key features of Vapi MCP Server?

  • Integration with Vapi APIs for creating and managing assistants.
  • Function calling capabilities for scheduling and initiating calls.
  • Support for Server-Sent Events (SSE) for remote connections.

use cases of Vapi MCP Server?

  1. Creating virtual assistants for customer support.
  2. Scheduling calls for appointments or inquiries.
  3. Integrating with existing Vapi tools for enhanced functionality.

FAQ from Vapi MCP Server?

  • What is the Model Context Protocol?

The Model Context Protocol is a framework for integrating various AI models and services, allowing for seamless communication and function calling.

  • Is there a cost to use Vapi MCP Server?

The Vapi MCP Server is free to use, but may require a valid API key from the Vapi dashboard.

  • Can I run tests on the Vapi MCP Server?

Yes, the project includes unit tests and end-to-end tests to ensure functionality.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
andyciggy
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago