Set Up Visier MCP

Set up the Visier Model Context Protocol (MCP) server as an administrator.

Overview

This article is for Visier administrators who are enabling Visier MCP. To use Visier MCP as a user, see Use Visier MCP.

The Model Context Protocol (MCP) is an open-source standard for connecting AI applications to external systems. MCP allows AI systems to access real-time information from various sources. Through MCP servers, organizations can expose their APIs and data in a standardized way, enabling more powerful and context-aware AI interactions.

Each AI application's output quality is client-dependent because different AI applications use different LLMs to interact with MCP. Visier MCP demonstrates successful results with Anthropic's Sonnet LLMs.

Prerequisites

An administrator must ensure the following prerequisites are met before continuing with MCP setup. Visier Query MCP Server requires:

• A Visier tenant with loaded data.
• Vee (Visier's conversational AI tool). See Vee for Partners.
• OAuth 2.0 client credentials for each AI agent you want to connect to Visier MCP. See Register a Client Application. Your agent must support OAuth 2.0 confidential clients (client ID and client secret).
• Your Visier Query MCP server URL: https://{vanity_name}.app.visier.com/visier-query-mcp.

  Tip: Replace {vanity_name} with your tenant name.

  To find your vanity name:

  • Go to the global workspace in Studio, click Settings > Single Sign-On. Then, under Single Sign-On, find your service provider endpoint; for example, https://jupiter.visier.com/VServer/auth. In this example, jupiter is the vanity name.
  • As an administrating tenant, go to the global workspace in Studio, click Settings > Partner Single Sign-On. Then under Bypass Users (Optional), find your service provider endpoint; for example, https://jupiter.visier.com/VServer/auth. In this example, jupiter is the vanity name.

Assign user access to MCP

To give your users access to Visier MCP, assign the following to their Visier user accounts:

• Custom profile with these capabilities: Data (Read, API), Legacy API Restricted, and Query MCP Server
• Permission with these capabilities: Vee Core if using Vee tools
• Data required: Access to the data that you request through the MCP server

Connect to a sample MCP client

Optionally, set up Visier Query MCP Server with a sample client provided by Visier. The sample client is a safe way to verify your MCP server connection before you connect to a full-package client like Claude. If you want to develop your own MCP client, Visier's sample client showcases working code using the LangChain MCP Adapters library based on the MCP Python SDK.

To use Visier's sample MCP client, see LangGraph MCP Client for Visier with Web UI.

Connect to MCP-compatible clients

This section describes the generic steps to set up Visier Query MCP Server with an MCP-compatible client. Your client may have similar but different configuration options. For a list of MCP-compatible AI applications, see MCP Clients.

1. Configure your client to connect to https://{vanity_name}.app.visier.com/visier-query-mcp.

   Tip: Replace {vanity_name} with your tenant name.

   To find your vanity name:

   • Go to the global workspace in Studio, click Settings > Single Sign-On. Then, under Single Sign-On, find your service provider endpoint; for example, https://jupiter.visier.com/VServer/auth. In this example, jupiter is the vanity name.
   • As an administrating tenant, go to the global workspace in Studio, click Settings > Partner Single Sign-On. Then under Bypass Users (Optional), find your service provider endpoint; for example, https://jupiter.visier.com/VServer/auth. In this example, jupiter is the vanity name.
2. Configure your client with the client ID and client secret you registered in Visier. For more information, see Register a Client Application.
3. Connect to Visier Query MCP Server according to your client's configuration options.
4. Authenticate your Visier account with OAuth 2.0.
5. Select the Visier tools to turn on for your client.

(Optional) Manually retrieve authorization server metadata

Visier MCP adheres to MCP Authorization, however, if your MCP-compatible client does not support Server Metadata Discovery and requires you to retrieve authorization server metadata such as OAuth 2.0 endpoint URLs, do the following:

1. In your browser, navigate to https://{vanity_name}.app.visier.com/.well-known/oauth-authorization-server/hr/oauth2.

   Tip: Replace {vanity_name} with your tenant name.

   To find your vanity name:

   • Go to the global workspace in Studio, click Settings > Single Sign-On. Then, under Single Sign-On, find your service provider endpoint; for example, https://jupiter.visier.com/VServer/auth. In this example, jupiter is the vanity name.
   • As an administrating tenant, go to the global workspace in Studio, click Settings > Partner Single Sign-On. Then under Bypass Users (Optional), find your service provider endpoint; for example, https://jupiter.visier.com/VServer/auth. In this example, jupiter is the vanity name.
2. On the page, retrieve your authorization_endpoint and token_endpoint values.
3. Configure your MCP-compatible client with the authorization_endpoint and token_endpoint URLs. The authorization code grant type requires these URLs to obtain a Visier access token.

For more information about authorization server metadata, see Authorization Server Metadata Response.

Connect to Claude

This section describes the steps to set up Visier Query MCP Server with Claude. Claude is an AI assistant built by Anthropic that, when connected to Visier Query MCP Server, can work with your integrated tools and Visier data all in one place.

When you or your team register a redirect URI for OAuth 2.0 in Visier, use Claude's callback URL: https://claude.ai/api/mcp/auth_callback,https://claude.com/api/mcp/auth_callback. For more information, see Building Custom Connectors via Remote MCP Servers.

A Workspace Owner or Primary Owner must add Visier Query MCP Server to your workspace's Claude connectors.

1. Open the Claude desktop application.
2. Navigate to Admin settings > Connectors.
3. Click Browse connectors.
4. Search for and select Visier.
5. Click Add to your team.
6. In Paste the Server URL here, type https://{vanity_name}.app.visier.com/visier-query-mcp.

   Tip: Replace {vanity_name} with your tenant name.

   To find your vanity name:

   • Go to the global workspace in Studio, click Settings > Single Sign-On. Then, under Single Sign-On, find your service provider endpoint; for example, https://jupiter.visier.com/VServer/auth. In this example, jupiter is the vanity name.
   • As an administrating tenant, go to the global workspace in Studio, click Settings > Partner Single Sign-On. Then under Bypass Users (Optional), find your service provider endpoint; for example, https://jupiter.visier.com/VServer/auth. In this example, jupiter is the vanity name.
7. In Paste the OAuth Client ID here, type the client ID you registered during Prerequisites.
8. In Paste the OAuth Client Secret here, type the client secret you registered during Prerequisites.
9. Click Continue.

   Result: Visier is now enabled in your list of connectors.

Troubleshoot your Claude connection

The following table describes possible errors and their solutions when using Visier MCP with Claude.

Description	Solutions
Visier Query MCP Server is not listed in Settings > Connectors.	Verify that Visier Query MCP Server was added to Claude correctly. For more information, see Connect to Claude.
After finding Visier Query MCP Server in Settings > Connectors and clicking Connect, the Visier sign-in page is not shown.	Check if there are connectivity issues with Visier or Claude: Visier Detailed Status and Claude Status .
After signing in to Visier, the sign-in page displays an access denied error.	Verify that the sign-in user's IP address is not restricted by the tenant's network access settings. For more information, see Set Up Network Access.
After signing in to Visier, the sign-in page spinner does not complete.	In Claude, navigate to Settings > Connectors and verify that you are connected to Visier Query MCP Server. If connected, ignore the spinner and close the sign-in page. Otherwise, check if there are connectivity issues with Visier: Visier Detailed Status.
After making a chat request, Claude returns an authentication error message.	Verify that the sign-in user and tenant have access to Visier Query MCP Server. For more information, see Prerequisites. If all prerequisites are met, in Claude, click Disconnect for Visier Query MCP Server and then Connect again.
After making a chat request, Claude returns a tool execution error message.	In the tool execution window, hover over the red icon to see the exact error. For tool parameter errors, ask Claude to provide the correct parameters for the tool and then try the same query again. For generic tool execution errors, check if there are connectivity issues with Visier: Visier Detailed Status. If servers are healthy, in Claude, click Disconnect for Visier Query MCP Server and then Connect again.

Claude keeps detailed logs for MCP server connections. You can review your server connection events, configuration issues, runtime errors, and message exchanges. For more information, see Viewing logs.

If you encounter connection errors, verify Claude's system availability. For more information, see Claude Status.

Connect to Gemini CLI

This section describes the steps to set up Visier Query MCP Server with Gemini CLI. Gemini CLI is an AI agent built by Google that, when connected to Visier Query MCP Server, can work with Gemini, your integrated tools, and Visier data all in one place.

When you or your team register a redirect URI for OAuth 2.0 in Visier, use Gemini CLI's callback URL: http://localhost:7777/oauth/callback. For more information, see Browser redirect requirements.

1. Add an mcpServers object to Gemini CLI's settings.json, as shown in the following sample.
   Copy

   Sample mcpServers object

   "mcpServers": {
       "visierQueryMcpServer": {
           "url": "https://{vanity_name}.app.visier.com/visier-query-mcp",
           "type": "http",
           "oauth": {
               "enabled": false,
               "clientId": "{The client ID you registered during Prerequisites}",
               "clientSecret": "{The client secret you registered during Prerequisites}",
               "authorizationUrl": "https://{vanity_name}.app.visier.com/hr/oauth2/authorize",
               "tokenUrl": "https://{vanity_name}.app.visier.com/hr/oauth2/token"
           }
       }
   }

   Tip: Replace {vanity_name} with your tenant name.

   To find your vanity name:

   • Go to the global workspace in Studio, click Settings > Single Sign-On. Then, under Single Sign-On, find your service provider endpoint; for example, https://jupiter.visier.com/VServer/auth. In this example, jupiter is the vanity name.
   • As an administrating tenant, go to the global workspace in Studio, click Settings > Partner Single Sign-On. Then under Bypass Users (Optional), find your service provider endpoint; for example, https://jupiter.visier.com/VServer/auth. In this example, jupiter is the vanity name.
2. Configure Gemini CLI. For more information, see How to set up your MCP server.
3. In a terminal, use the command gemini.
4. Authenticate with Gemini.
5. In a terminal, use the command /mcp auth visierQueryMcpServer.
6. Authenticate with Visier Query MCP Server.