Connect

The server speaks two transports:

• Hosted Streamable HTTP for production usage (public or partner)
• Local stdio for development and self-hosting

In both cases, the client entry name can be whatever your MCP client expects. Common choices are visamundi for the public route and visamundi-partner for the partner route.

Hosted (Streamable HTTP)

Production hosting exposes two URLs on the same host:

Route	URL	Auth
Public	https://mcp.visamundi.io/	None — read-only Connect reference tools (visa products, requirements, vaccines, customs).
Partner	https://mcp.visamundi.io/partners	Authorization: Bearer with a partner MCP key from the portal.

Public example

{
  "mcpServers": {
    "visamundi": {
      "url": "https://mcp.visamundi.io/"
    }
  }
}

Partner example

Partners create an MCP credential in the partner portal, then connect with a bearer token:

{
  "mcpServers": {
    "visamundi-partner": {
      "url": "https://mcp.visamundi.io/partners",
      "headers": {
        "Authorization": "Bearer vm_mcp_your_key_here"
      }
    }
  }
}

The partner route is authenticated:

• missing, revoked, or unknown keys return 401
• each key exposes only the tools you enabled for it in the portal
• reads are scoped to the company behind that credential

You can register both servers in the same client if you want public reference data alongside partner-scoped tools.

Local (stdio)

Run the server as a local process over stdio — useful for development or a self-hosted setup. Build it first (npm install && npm run build), then point your client at the built entry file:

{
  "mcpServers": {
    "visamundi-partner": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-server/dist/index.js"],
      "env": {
        "CONNECT_API_MCP_KEY": "your_connect_token"
      }
    }
  }
}

Self-hosted HTTP mode uses the server’s own configuration for Connect access, partner authentication, and host protection. See the MCP server repository for environment variables and deployment notes.

Once connected, see Tools for the partner-visible tool surface.