FAQ: Valsight MCP integration

It lets you connect your own external AI client — such as Claude — to Valsight over the Model Context Protocol (MCP), an open standard for connecting AI clients to tools and data. The connected client can then explore and, in write mode, change your models from outside the Valsight app, always within your own permissions.

The in-app Assistant is a conversational assistant you use inside Valsight, aimed at all users. The MCP integration lets you drive Valsight from your own external AI client or agent, and is aimed at technical users. Both build on the same model context and both act only within your Valsight permissions.

Any AI client that supports MCP. There is no single, standard way to configure an MCP server, so the exact steps depend on the client — follow that client’s own MCP setup instructions. Guides for specific clients may be provided over time.

Point your AI client at your instance’s MCP endpoint and sign in when prompted, using your normal Valsight login. There is no single, public endpoint: the address is specific to your Valsight instance. Your instance must also have the MCP integration enabled (see prerequisites).

• Your Valsight instance must have the MCP integration enabled. It is a premium feature, opted into per customer (see “What does it cost?” below).
• A compatible Valsight version — available from Valsight 7.3.0.
• An AI client that supports MCP.

The MCP integration is a premium feature, available from Valsight 7.3.0. Through 31 December 2026 it is included for all customers at no additional cost, so you can connect your own AI client, work with your real models, and see what it adds before deciding to keep it. From January 2027 it becomes a paid add-on. It is opted into per instance and needs some setup, so it is not enabled by default. To turn it on, or to talk through whether it fits your team, write to support@valsight.com or contact your Customer Success representative.

You authenticate with your normal Valsight sign-in, and the integration acts only within your permissions — it cannot see or do more than you can. Each connection runs as a session whose scope you control: which projects it can touch, whether it is read-only or write, and whether it can see numeric values. Connections are only accepted for recognized Valsight instances, and activity is logged.

Yes, when the session is connected in write mode. You control the session’s access level (read-only or write) and its data access (restricted or full), as well as which projects are in scope. Connect read-only if you only want it to explore.

Session scope is set when you connect, and you can also steer it by asking the agent in plain language or through the session-management page. It covers the target instance, the projects in scope, the access level, and data access; deleting whole projects and changing access rights are separate, off-by-default options.

A session ends after a period of inactivity, when access is revoked, or when an administrator ends it. Your Valsight sign-in stays valid for 12 hours, after which you sign in again.