ChipsAI MCP Server vs MCP Server

A side-by-side look at the ChipsAI MCP Server and MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

ChipsAI MCP Server logoChipsAI MCP ServerConversational AI · Local subprocess (stdio)MCP server for ChipsAI — manage chatbots, conversations, and AI models47FairAuth: not declaredMCP Server logoMCP ServerConversational AI · Local subprocess (stdio)Build AI voice assistants and phone agents with Vapi through the Model Context Protocol68GreatAuth: api key required

Verdict: choose ChipsAI MCP Server for conversational ai work as a local process; choose MCP Server for conversational ai as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

ChipsAI MCP Server logoChoose ChipsAI MCP Server when

  • You need dedicated capabilities in the Conversational AI domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: CHIPSAI_API_KEY, CHIPSAI_API_URL, CHIPSAI_USERNAME, CHIPSAI_PASSWORD.
  • You want tools like list_chatbots, get_chatbot, create_chatbot.
Explore ChipsAI MCP Server

MCP Server logoChoose MCP Server when

  • You need dedicated capabilities in the Conversational AI domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: API key required.
  • You have the keys it needs: VAPI_TOKEN.
  • You want tools like list_assistants, create_assistant, get_assistant.
Explore MCP Server

Feature & specification comparison

Rows where the two servers differ are marked.

SpecChipsAI MCP Server logoChipsAI MCP ServerMCP Server logoMCP Server
CategoryConversational AIConversational AI
Quality signal47/100 · Fair68/100 · Great
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredAPI key required
PricingNot declaredBYOK (pay the provider)
Required env varsCHIPSAI_API_KEYCHIPSAI_API_URLCHIPSAI_USERNAMECHIPSAI_PASSWORDVAPI_TOKEN
Verified ownerCommunity listingCommunity listing
GitHub stars058
Directory activity 1 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools2513

Tools & capabilities

ChipsAI MCP Server tools 25

  • list_chatbotsList all chatbots for the authenticated user
  • get_chatbotGet full chatbot details (prompt, model, colors, etc.)
  • create_chatbotCreate a new chatbot (returns embed script tag)
  • update_chatbotUpdate chatbot fields (name, prompt, model, theme, colors, etc.)
  • delete_chatbotSoft-delete (deactivate) a chatbot
  • get_chatbot_configGet public widget configuration
  • get_chatbot_analyticsGet analytics: messages, sessions, daily stats, devices, countries
  • upload_documentUpload PDF/DOC/DOCX to a chatbot's knowledge base (LlamaParse)
  • list_conversationsList conversations, optionally filtered by chatbot
  • create_conversationCreate a new conversation
  • get_conversationGet conversation details
  • update_conversationUpdate conversation title
  • +13 more on the listing page

MCP Server tools 13

  • list_assistantsLists all Vapi assistants
  • create_assistantCreates a new Vapi assistant
  • get_assistantGets a Vapi assistant by ID
  • update_assistantUpdates an existing Vapi assistant
  • list_callsLists all Vapi calls
  • create_callCreates a outbound call
  • get_callGets details of a specific call
  • list_phone_numbersLists all Vapi phone numbers
  • get_phone_numberGets details of a specific phone number
  • list_toolsLists all Vapi tools
  • get_toolGets details of a specific tool
  • create_toolCreates a new Vapi tool
  • +1 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

ChipsAI MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "chipsai-mcp-server": {
      "command": "uvx",
      "args": [
        "chipsai-mcp"
      ],
      "env": {
        "CHIPSAI_API_KEY": "YOUR_CHIPSAI_API_KEY_HERE",
        "CHIPSAI_API_URL": "YOUR_CHIPSAI_API_URL_HERE",
        "CHIPSAI_USERNAME": "YOUR_CHIPSAI_USERNAME_HERE",
        "CHIPSAI_PASSWORD": "YOUR_CHIPSAI_PASSWORD_HERE"
      }
    }
  }
}

MCP Server

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "vapi-ai-mcp-server": {
      "command": "npx",
      "args": [
        "-y",
        "@vapi-ai/mcp-server"
      ],
      "env": {
        "VAPI_TOKEN": "YOUR_VAPI_TOKEN_HERE"
      }
    }
  }
}

Frequently asked questions

ChipsAI MCP Server is categorized under Conversational AI and uses a local stdio subprocess. MCP Server belongs to Conversational AI and uses a local stdio subprocess. Pick ChipsAI MCP Server for conversational ai work and MCP Server for conversational ai.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

ChipsAI MCP Server has no declared pricing — check the project's own site. MCP Server is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add chipsai-mcp-server and vapi-ai-mcp-server as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, ChipsAI MCP Server has a quality signal of 47/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. MCP Server has 68/100 (Great) with 2 views, 0 installs and 58 GitHub stars.