Connect an MCP client

Works with any MCP client, including:

Claude Cursor Windsurf

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 — reference tools (visa products, requirements, vaccines, customs) and visa application submission. 200 reference lookups per client per day.
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.

Refreshing tools after portal changes

When you enable or disable tools on an MCP credential in the partner portal, the hosted server picks up the new list immediately. Your AI client may not. Many clients cache the tool list until they treat the MCP entry as new configuration.

This is client behavior — Visamundi does not control it, and there is no separate “force refresh tools” action in the portal. Plan on reconnecting or re-registering the server in the client after you save tool changes.

Cursor

In Cursor today, these actions aim at invalidating the server entry or forcing rediscovery — not only signing out of MCP:

Action	Usually refreshes tools?
MCP Logout → Login (same config)	Often no
Reload window	Often no
MCP server Off → wait → On	Sometimes
Remove server from MCP list → add again	Yes
Edit mcp.json (URL, headers, server name, or any harmless field)	Yes
Fully quit Cursor and reopen	Sometimes

Practical guidance after saving tool toggles: do not assume MCP logout alone is enough. Turn the Visamundi server off and on in Cursor settings, or remove and re-add the MCP entry. Editing and saving mcp.json (even a small change) also works reliably.

When Cursor does run a full reconnect, the server can advertise that your enabled tools changed (for example in server metadata shown during initialize). That only helps if the client re-reads that information — which logout may not trigger completely.

Other MCP clients may behave differently; if tools look stale after a portal change, use that client’s equivalent of disabling the server or editing its configuration so it reconnects.

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 public and partner tool surface. Browser agents do not need this setup: see WebMCP.