Server Information
Server: VapiAI/vapi-mcp-server
Connection Type: Local (via Smithery hosted toolbox)
Description
The Smithery-hosted connection for this MCP server fails to initialize with a 400 error, and the Smithery toolbox UI never surfaces a config field to supply the required Vapi API key/token.
Steps to Reproduce
Step 1: On smithery.ai, add "Vapi MCP Server" (VapiAI/vapi-mcp-server) to a toolbox.
Step 2: Server immediately shows state "error" with message: "Initialization failed with status 400".
Step 3: Try "Reconnect" from the toolbox connection menu - it clears stored credentials but does not prompt for any new config/API key, and the connection returns to the same error.
Step 4: Disconnect and re-add via "Add to toolbox" on the server page - it reconnects immediately with zero config prompt, landing directly back in the error state.
Step 5: The server's own "Integrate" tab on its Smithery page does not render any content when clicked (only updates the URL hash to #api, tab content stays on Overview).
Expected Behavior
Adding the server to a Smithery toolbox should prompt for the required Vapi API key/config before attempting to connect, so a valid key can be supplied and the server can initialize successfully.
Actual Behavior
No config UI is ever shown. The connection goes straight to an "Initialization failed with status 400" error with no way to supply an API key through the Smithery toolbox UI.
Additional Context
Server is tagged "Local" on its Smithery page, suggesting it may be intended to run via npx with env vars (e.g. VAPI_TOKEN) rather than as a hosted remote server - this may be the root cause of the missing config step in the hosted toolbox flow.
Server Information
Server: VapiAI/vapi-mcp-server
Connection Type: Local (via Smithery hosted toolbox)
Description
The Smithery-hosted connection for this MCP server fails to initialize with a 400 error, and the Smithery toolbox UI never surfaces a config field to supply the required Vapi API key/token.
Steps to Reproduce
Step 1: On smithery.ai, add "Vapi MCP Server" (VapiAI/vapi-mcp-server) to a toolbox.
Step 2: Server immediately shows state "error" with message: "Initialization failed with status 400".
Step 3: Try "Reconnect" from the toolbox connection menu - it clears stored credentials but does not prompt for any new config/API key, and the connection returns to the same error.
Step 4: Disconnect and re-add via "Add to toolbox" on the server page - it reconnects immediately with zero config prompt, landing directly back in the error state.
Step 5: The server's own "Integrate" tab on its Smithery page does not render any content when clicked (only updates the URL hash to #api, tab content stays on Overview).
Expected Behavior
Adding the server to a Smithery toolbox should prompt for the required Vapi API key/config before attempting to connect, so a valid key can be supplied and the server can initialize successfully.
Actual Behavior
No config UI is ever shown. The connection goes straight to an "Initialization failed with status 400" error with no way to supply an API key through the Smithery toolbox UI.
Additional Context
Server is tagged "Local" on its Smithery page, suggesting it may be intended to run via npx with env vars (e.g. VAPI_TOKEN) rather than as a hosted remote server - this may be the root cause of the missing config step in the hosted toolbox flow.