Athena
Guide · AI connectors
Connect Muvia to Claude, ChatGPT and other assistants
Your AI assistant reads Muvia's data and proposes changes with your account, never beyond your role. It takes one address: the assistant brings you to Muvia to sign in and decide what it may do.
MCP server address
https://api.muviabi.com/mcp/v1/It works with or without the trailing slash. Never paste a password or a key into the assistant: access goes through Muvia's sign-in, with OAuth.
- MCP over HTTP
- OAuth 2.1
- One person, one company, one assistant
Before you start.
All four are needed. If one is missing, Muvia's page tells you which.
01
A Muvia account
You connect as yourself, with the user you sign in to Muvia with, and the second factor if your company asks for it.
02
The AI connectors module
It is part of your company's plan. If it is not there, ask your Muvia contact for it.
03
The administrator's switch
An administrator turns it on in Settings → AI connectors → "Enable AI connectors". While it is off, no assistant can connect.
04
An admitted assistant
By default a company admits only the assistants Muvia has verified: Claude, ChatGPT and Visual Studio Code. An administrator can admit others on the same page.
Each person connects their own account. A connection is always one person, one company and one assistant: the assistant works as you, in the company you choose.
Connect your assistant.
The protocol is the same for all of them: only the place where you paste the address changes. Either way you reach Muvia's consent page, described below.
Claude
claude.ai and Claude Desktop
- Open Settings → Connectors. If Muvia is in the connectors directory, add it from there; otherwise choose "Add custom connector" and paste the server address.
- Leave the OAuth client fields empty: Claude registers itself.
- Press "Connect": Muvia's consent page opens.
- In a chat, ask "Who am I on Muvia?": the assistant answers with your name, the company and the permissions you granted.
Custom connectors need a paid Claude plan; on Team and Enterprise plans an administrator may have to enable them.
Claude Code
In the terminal
- Add the server with the command below.
- In Claude Code type /mcp, choose "muvia" → Authenticate: Muvia's consent page opens in the browser.
claude mcp add --transport http muvia https://api.muviabi.com/mcp/v1/ChatGPT
chatgpt.com
- Open Settings → Apps and connectors and turn on developer mode.
- Create a connector: the address above as the MCP server URL, OAuth as the authentication.
- ChatGPT registers itself and opens Muvia's consent page.
Visual Studio Code
From the command palette
- Run "MCP: Add Server" and choose HTTP.
- Paste the server address and confirm.
- When VS Code asks, sign in to Muvia and approve.
Other assistants
Any MCP client that supports OAuth, such as Codex, Gemini, Cursor or Microsoft Copilot, connects to the same address if the administrator admits "All registered assistants" or picks it by name. The steps are the generic ones: add a remote MCP server, paste the address and sign in to Muvia when the client asks. On the consent page it appears under the name it gave itself, without the "Verified" mark. A script or an integration with no person in front of it uses a connector key instead.
The consent page: you decide what to grant.
The assistant never sees your password. It opens a Muvia page where you:
- sign in to Muvia, with the second factor if your company asks for it;
- check the company the assistant will work in and, if needed, press "Change company";
- tick the permissions you want to grant;
- press "Allow" and go back to the assistant, now connected.
The permissions
The page offers only the permissions your role lets you give. The ones the assistant asks for start ticked; nodes and tags, data sources and alarm notifications always start unticked.
| Permission | What it allows | On the page |
|---|---|---|
| Readmuvia.read | Read projects, signals, alarms, flows, analyses and documents. | Default |
| Write proposalsmuvia.write | Run flows and write their functions, create analyses and dashboards, attach notes and documents, update the project; also delete datasets, queries, notebooks, dashboards and analyses, change who can see an analysis, create and revoke public links, and send reports by email, wherever your role allows it. | Ticked if the assistant asks |
| SQL readsmuvia.sql | Run read-only SQL queries on the projects' data. | Ticked if the assistant asks |
| Nodes and tagsmuvia.nodes | On Muvia Industrial: declare and withdraw tags, edit a node's configuration. Publishing it to the node, commands, software and data limits always wait for your confirmation in Muvia. | Always ticked by hand |
| Data sourcesmuvia.sources | Connect databases and accounts, create, update and run sources and their loads. Deleting a source, a load, a connection or an account always waits for your confirmation in Muvia. | Always ticked by hand |
| Alarm notificationsmuvia.alarms | Edit channels and subscriptions, take alarms in charge and add notes to them. | Always ticked by hand |
Never beyond your role. A granted permission only sets a ceiling: on every call Muvia works out again what you may do, in that company, at that moment. If a role is taken from you, the assistant loses it on its next call.
What the assistant can do.
It reads what you see. When it writes, it proposes: a person decides, in Muvia.
Read
With the read permission, whatever your role sees in the projects you are assigned to:
- projects, with their rules and documents
- datasets and queries, with their columns and data
- signals and analyses
- dashboards and widgets
- reports
- flows, their runs and their functions
- alarms
- nodes, on Muvia Industrial
Long answers come in pages: the assistant asks for the next one or narrows its search. A project of another company, or one you are not assigned to, answers as if it did not exist.
Propose
With the write proposals permission, every write the assistant makes becomes a proposal and changes nothing until a person approves it.
- The assistant shows you the link to the proposal.
- Open it, or go to Lab → To approve: the assistants' proposals sit beside Athena's, with the assistant's name and the person who connected it.
- Check the preview and press "Approve" or "Discard". The person who connected the assistant decides, or an administrator.
The assistant sees the outcome: applied, discarded, stale (what it was based on changed in the meantime), expired after seven days without a decision, or failed, with the reason.
Autonomy, if the administrator chooses it
In Settings → AI connectors → Autonomy an administrator chooses, kind of change by kind, "Ask for confirmation" (the default) or "Run at once". Even when run at once, the change stays in "To approve", marked as applied. Actions on machines, and the changes Muvia always has confirmed, always wait for a person.
Try these.
A few requests to start with. Replace the names with those of your own projects.
Request
“Who am I on Muvia?”
Checks the connection: person, company, permissions and assistant.
Request
“List my projects, then the datasets of the Sales project.”
Read.
Request
“In the Sales project, who were the ten customers with the highest revenue in 2025? Show me the query too.”
Needs the SQL reads permission.
Request
“Which dashboards and which reports are in the Sales project?”
Read.
Request
“Create a dashboard with monthly orders by region.”
Needs the write proposals permission: you get a proposal to approve in Muvia.
See and revoke connections.
- Your connections
- In Settings → AI connectors, under "My connections", you see the assistants you connected, with their permissions, the date and their last use, and you can revoke them.
- The whole company's
- On the same page an administrator sees every assistant connected in the company, who connected it and whether it is verified, and can revoke any of them.
- Revoking is immediate
- The assistant loses access on its next call and has to be connected again to be used. The proposals it left waiting are discarded.
- After 90 days unused
- A connection that goes unused for 90 days is revoked on its own.
- Connectors switched off
- If the administrator switches the AI connectors off, connections are not revoked: every call is refused with a message until they are switched back on.
How Muvia handles the connector's data.
What the assistant reaches, what Muvia records, and what it does not.
- What it reaches
- Only the data your role and the granted permissions reach, in the company chosen on the consent page and in the projects you are assigned to. The company comes from the connection, never from the assistant's request.
- What Muvia records
- Every call the assistant makes, with the assistant's name and the connection that made it, in a call ledger. Every applied change in the company's activity log, under your name and with the assistant's. Connections created, updated and revoked, with the reason, in the security journal.
- What it does not read
- The conversation stays with the assistant. Muvia receives only the requests the assistant makes to it, with their arguments, and answers those.
- Where the answers go
- Muvia's answers go to the assistant you connected and, from there, to its provider, under the terms of its service.
- Credentials
- Your password never passes through the assistant. The assistant receives an access token valid for one hour and a refresh token valid for 30 days, replaced on every use. Muvia stores them only as hashes.
Personal data is handled as the privacy policy describes.
If something goes wrong.
| What you see | Why, and what to do |
|---|---|
| The assistant says it cannot reach the server. | Check that you pasted exactly the address at the top of this page. If it is right and the problem stays, write to us. |
| The consent page says the assistant is not verified. | Your company admits only verified assistants: Claude, ChatGPT and Visual Studio Code. An administrator can admit all registered assistants, or pick one, in Settings → AI connectors. |
| The consent page says AI connectors are not in the plan, or are switched off. | The AI connectors module is missing, or the administrator has not enabled them (see "Before you start"). If you work for several companies, "Change company" lets you pick one that has them. |
| "This connection to Muvia is no longer valid." | The connection was revoked, or your user was disabled, removed from the company or left without a role. Connect the assistant again. |
| "This connection cannot do that: it needs the … permission." | Your role does not allow it, or you did not grant the permission it needs (for example write proposals, nodes and tags, data sources or alarm notifications). Ask an administrator for the role, or connect the assistant again ticking the permission. |
| A request is refused with a message, but the connection stays. | After you connected, your company's module, switch or admitted assistants changed. Ask an administrator: there is no need to connect again. |
| Running a flow is refused: an administrator must approve it. | The flow is not approved yet. An administrator approves it in the Lab first. |
| The assistant cannot register: too many requests. | Muvia limits how many new assistants register per hour. Try again later. |
Need help?
Write to us from the contact form: say which assistant you use and what you see. The protocol, security and the administrator's controls are explained on the page for technical teams.