Does Vendizap have an MCP server?
Vendizap maintains an official MCP server.
- Access
- Remote server
- Endpoint
- https://api-docs.vendizap.com/mcp
- Category
- E-Commerce
A remote server run by Vendizap itself — nothing to install. Documented at registry.modelcontextprotocol.io.
Hosted by the vendor — no install, connect over HTTP with OAuth or a token.
Add it from the terminal, then restart your session:
claude mcp add --transport http vendizap https://api-docs.vendizap.com/mcpAdd --scope user to make it available in every project.
- Open Settings → Connectors
- Click Add custom connector
- Paste
https://api-docs.vendizap.com/mcp - Finish the sign-in prompt, then enable it in the chat's tools menu
Add to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for
every project:
{
"mcpServers": {
"vendizap": {
"url": "https://api-docs.vendizap.com/mcp"
}
}
}A green dot in Settings → MCP means it connected.
Add to .vscode/mcp.json:
{
"servers": {
"vendizap": {
"type": "http",
"url": "https://api-docs.vendizap.com/mcp"
}
}
}Then pick the server from the tools menu in Copilot's agent mode.
- Enable Developer mode under Settings → Apps & Connectors → Advanced
- Choose Create and paste
https://api-docs.vendizap.com/mcp - Complete sign-in, then enable the connector in a new chat
Does Vendizap have an official MCP server?
Yes. Vendizap maintains an official MCP server, hosted at https://api-docs.vendizap.com/mcp.
How do I connect Vendizap to Claude?
Add https://api-docs.vendizap.com/mcp as a custom connector under Settings → Connectors in Claude Desktop or claude.ai, or run "claude mcp add --transport http vendizap https://api-docs.vendizap.com/mcp" in Claude Code.
Do I need to install anything to use the Vendizap MCP server?
No. It is a remote server hosted by Vendizap, so your MCP client connects to it over HTTP. You authenticate with the vendor rather than installing a package.
How is this verdict verified?
The main evidence is the MCP Registry entry under Vendizap's verified namespace com.vendizap; no Vendizap page documents the server. The endpoint sits on Vendizap's API docs domain, serves OAuth protected-resource metadata, and answers MCP initialize with a Vendizap-authorization 401; the openapi.yaml published there carries x-mcp tool annotations. GitHub metadata is refreshed every six hours.
The main evidence is the MCP Registry entry under Vendizap's verified namespace com.vendizap; no Vendizap page documents the server. The endpoint sits on Vendizap's API docs domain, serves OAuth protected-resource metadata, and answers MCP initialize with a Vendizap-authorization 401; the openapi.yaml published there carries x-mcp tool annotations.
- github data refreshed 2026-09-29, then every 6 hours
- vendor docs verified on 2026-09-29
Spotted something out of date? Tell us — corrections ship same-day.