Probe Helpcenter
Auto Light Dark
Auto Light Dark

No AI assistant yet?

To ask Probe questions in plain language you need an AI assistant that supports MCP (Model Context Protocol). Probe itself contains no AI model: your assistant does the reasoning, and Probe gives it the board data. If your company has not chosen an assistant yet, these are the usual routes.

Options

Option

What you need

Good when

Claude Code (recommended for the evaluation)

A Claude account: Pro or Max for one person, Team or Enterprise for a company

You want the quickest start. It is the assistant we have tested with the evaluation server, and your welcome page gives ready-made commands.

GitHub Copilot in VS Code (not yet tested with the evaluation server)

A GitHub Copilot licence. On Business or Enterprise, MCP servers may need to be allowed by an administrator.

Your company already uses Copilot.

A local model, for example in LM Studio (not yet tested with the evaluation server)

A computer powerful enough to run a model with tool support

Design data may not be sent to a cloud model.

Another assistant

Support for remote MCP servers over HTTP with a custom header

Your company already has an approved assistant.

Setup for each is in Connect Claude Code to Probe and Connect another AI assistant.

Questions from IT

  • Where does design data go? From Probe to your assistant, and from your assistant to its model provider, under your company's own agreement with that provider. Nothing passes through E-Sharp's AI accounts. With a local model, nothing leaves your computer except the connection to your Probe server.

  • Training on our data? Business plans (Claude Team and Enterprise, the API, Copilot Business and Enterprise) do not train on your data by contract. On personal plans, turn off model training in the privacy settings before using real design data.

  • More in Data protection & security and How your data is handled during an evaluation.

Not sure?

Tell us what your company allows, and we will suggest the simplest route. Daniel Hansson, E-Sharp · daniel.hansson@esharp.se