BI.P.EYE logo
Signup
Claude connector Read-only

Use BI.P.EYE in Claude

The BI.P.EYE connector lets you ask Claude questions about your BI.P.EYE data. Claude finds the right data model, BI.P.EYE builds and runs the query on your data, and Claude shows the answer with the decisions and assumptions behind it. The connector only reads data. It cannot change your data, models or dashboards.

Last updated

Before you connect

  • A BI.P.EYE account (any paid or trial plan) that is a member of at least one organization. Every role can connect, including Viewer.
  • A Claude plan that supports connectors.
  • At least one data model set to Available in Claude in that organization (see the next section).
  • On Claude Team and Enterprise plans, a Claude Owner adds the connector for the organization first. Each member then connects with their own BI.P.EYE account.

Choose which models Claude can use

Claude sees only the data models your organization makes available. Every model starts Off, including existing ones.

  1. Sign in to BI.P.EYE and open Models.
  2. On each model card, find Available in Claude.
  3. Select Everyone to make the model available to all members of the organization who connect Claude, or Off to hide it.

Owners, Modifiers and BI Engineers can change this setting. Other roles can see it but not change it. A change applies to the next request Claude makes; nobody needs to reconnect.

Connect

From the Claude directory

  1. In Claude, open Customize > Connectors, select Discover, and search for BI.P.EYE.
  2. Select Connect. On Claude Team and Enterprise, an Owner first selects Connect for your team; members then connect their own account.
  3. Sign in to BI.P.EYE if asked. You can use your password or Google sign-in.
  4. On the BI.P.EYE consent page, choose the organization to connect and select Allow. Each organization shows your role, its creation date, member count and the number of models available in Claude, so organizations with the same name are easy to tell apart.
  5. You return to Claude with BI.P.EYE connected.

As a custom connector

If your Claude plan lets you add custom connectors, you can also add BI.P.EYE by URL. In Claude, open Customize > Connectors, select Add custom connector, enter the URL below, leave the advanced settings empty, and select Add. Then select Connect and continue from step 3 above.

https://mcp.bipeye.com/mcp

One connection covers one organization. To switch organizations, disconnect in Claude and connect again.

Use it in a chat

Select + in the message box, open Connectors, and make sure BI.P.EYE is on. Then ask in plain language, in any language. Claude asks for your approval the first time it uses each tool.

Example prompts:

  • "What data do I have in BI.P.EYE?"
  • "Show monthly revenue by sales channel for 2026."
  • "How many orders did we have per week in the last 3 months?"
  • "Which 20 products had the most returns last quarter?"

Follow-ups such as "only the last 3 months", "add the customer name" or "make it weekly" refine the previous answer instead of starting over.

If your organization has more than one model available, each answer names the model it came from. You can name the model in your question to choose it.

What Claude can do

The connector has four tools. All of them are read-only.

Tool What it does
list_models Lists the data models available to you in Claude.
describe_model Shows a model's datasets, columns and the relationships between them.
query_model Answers a question about one model and returns the rows, the decisions (grain, measures, period) and the assumptions used.
get_query_result Returns the result of a question that took longer than about 50 seconds.

Results and limits

  • Results with up to 200 rows come back in full.
  • Larger results include the first 20 rows and a download link to the full table, for example to open in Excel. The link expires after 5 minutes; ask Claude for the result again to get a new one.
  • When a question takes longer than about 50 seconds, Claude receives a "running" status and collects the result with get_query_result.
  • Every answer lists what BI.P.EYE decided and assumed, such as which dataset and date column were used, so you can check how a number was calculated.

Who sees what

  • Claude sees only the models set to Available in Claude, in the organization you chose when connecting.
  • Each person signs in with their own BI.P.EYE account. Claude never receives your BI.P.EYE password.
  • Access follows your BI.P.EYE account and role, and is checked on every request. If you are removed from the organization or change your BI.P.EYE password, the connection stops and you need to connect again.
  • Questions and results become part of your Claude conversation. BI.P.EYE receives the questions Claude sends to the connector, not the rest of the conversation. See our privacy policy for what BI.P.EYE stores and for how long.

Disconnect

In Claude, open Customize > Connectors, select BI.P.EYE and select Disconnect. To stop Claude from using a specific model for everyone in your organization, set Available in Claude to Off on that model in BI.P.EYE.

Troubleshooting

Problem What to do
Claude says no models are available Ask an Owner, Modifier or BI Engineer to set Available in Claude to Everyone on the Models page.
A model you expect is missing It is set to Off, or you connected a different organization. Disconnect and connect again to choose another organization.
The organization you want is greyed out on the consent page That organization requires Google sign-in. Sign in to BI.P.EYE with Google and connect again.
"This sign-in request has expired" Start the connection again from Claude.
Claude reports that the connection stopped working You may have changed your password, left the organization, or your plan may have expired. Disconnect and connect again; if it still fails, contact support.
The download link shows Access Denied The link expired after 5 minutes. Ask Claude for the result again.

Support

Email [email protected]. We reply within a few hours on business days. Include the time of the request and the question you asked, if relevant. Never send passwords or API keys by email.