Connect Claude to the Valsight MCP server
Goal
You will have Claude connected to the Valsight MCP server, so it can read — and, in a write session, change — data in your Valsight projects on your behalf. Setup takes about five minutes and works both on claude.ai and in Claude Code (the terminal). Both use the same server, the same sign-in, and the same permissions.
Prerequisites
- A Valsight account with administrator permissions
- Network access to your Valsight instance
The MCP server must also be enabled for your Valsight instance — it is a premium feature, opted into per customer (see availability and pricing). The server is remote, so there is nothing to install; Claude connects to it over the internet.
Your MCP server address
The address is your instance’s URL carried as a query parameter on the shared MCP server host:
https://mcp.valsight.ai/mcp?monolithUrl=https://<your-instance>.valsight.com
It is one continuous address with no spaces — select and copy it in one piece. Replace <your-instance>.valsight.com with your own Valsight instance URL; if you are unsure of it, ask your Valsight admin.
Steps
Connect on claude.ai
- Open the connector settings: your initials (bottom left) → Settings → Connectors.
- Click Add custom connector and name it
Valsight. - Paste your MCP server address. Leave Advanced settings (Client ID / Secret) empty — registration is automatic.
- Click Add, then Connect. The login window opens (see The sign-in flow).
- Once the connector shows Connected, enable Valsight from the tools menu (the sliders icon) in any new chat.
The connector settings live under your initials in the bottom-left of claude.ai. After Connect, a browser window handles the sign-in; when it reports success the connector turns green and reads Connected. Add screenshots into
./images/next to this file.Connect with Claude Code
For working in the terminal — same server, same login, same permissions.
The sign-in flow
Sign-in is one-time. Afterwards the connection stays active and tokens refresh automatically.
- The browser opens id.valsight.com — Valsight’s own identity service. This window is expected.
- Approve the authorization request (“MCP Client requests access”). This authorizes Claude to act with your permissions.
- Log in with your existing Valsight account — your work e-mail and Valsight password. Never click Register; your account already exists.
Verify
- On claude.ai: the connector shows a green Connected, and Valsight appears in the tools menu of a new chat.
- In Claude Code:
claude mcp listshowsvalsightas connected. - End to end: ask Claude something that needs live project data (for example, to list your projects). A grounded answer confirms the bridge works.
Control the session
By default an MCP session can write — it can change your models. Scope it deliberately. Use the session-management page to set the active session to read-only or restrict it to specific projects:
https://mcp.valsight.ai/management/
Session scope, access level, and data access, and their defaults, are covered in Session scope and permissions. Your Valsight sign-in stays valid for 12 hours, after which you sign in again.
Help
Login trouble, or projects missing after you connect? Contact your Valsight admin.
Related
- Valsight MCP integration: what the server is, its capabilities, and how session scope keeps a connection contained.
- FAQ: Valsight MCP integration: connecting, security, and prerequisites.
- Valsight AI: overview of both ways to use Valsight AI.