Add Plexus to Claude
Plexus has a connector for Claude. Once it is connected, you can ask Claude about your devices, build and change dashboards, set up monitors and on-call, acknowledge alerts and look after your workspace, in plain words.
It works in Claude on the web, the desktop app and Claude Code. You need a Plexus account; the Free plan is enough to start.
Connect
Claude on the web or the desktop app
- Open Customize → Connectors.
- Choose Add custom connector.
- Paste this address:
https://app.plexus.company/mcp- Click Connect. Your browser opens Plexus: sign in, check what Claude is asking to do, and approve.
On a Team or Enterprise plan, an owner adds the connector under Organization settings → Connectors, and each person then clicks Connect.
Claude Code
Run this once in your project's terminal:
claude mcp add --transport http plexus https://app.plexus.company/mcpThe first time Claude uses it, your browser opens for the same sign-in.
Other tools
Plexus is a standard MCP server, so it is not only for Claude. Any tool that
can connect to a remote MCP server and sign in through the browser can use it,
with any model. The address is always https://app.plexus.company/mcp.
OpenCode. Add this to opencode.json, then run opencode mcp auth plexus:
{
"mcp": {
"plexus": { "type": "remote", "url": "https://app.plexus.company/mcp" }
}
}Codex. Run this once. It opens your browser for the sign-in:
codex mcp add plexus --url https://app.plexus.company/mcpCursor. Add this to .cursor/mcp.json, then sign in when Cursor asks:
{
"mcpServers": {
"plexus": { "url": "https://app.plexus.company/mcp" }
}
}The sign-in, the ticks on the approval screen and everything below are the same in every tool.
What you approve
Signing in lets Claude work in the workspace you approve it in. The approval screen lists eighteen areas, each with a tick. Untick the ones this connection should not have.
Only an admin or editor of the workspace can approve. Claude never moves money and never deletes an account.
Things to ask
Set up Plexus in this project.Sends your first reading from the project you have open and gives you the dashboard link. (Claude Code.)
Which of my devices have stopped sending, and when did each last report?Build a dashboard for rover-01: battery voltage, motor temperature and GPS fix, last 24 hours.Alert me when motor temperature on any pump goes above 80 degrees.What alerts are open right now? Acknowledge the one on ups-a and note that I'm looking at it.Turn this Grafana dashboard into a Plexus one.Paste the Grafana export after that last one.
Make an on-call ladder with me first and Priya second, and have the pump temperature monitor call it.Make a public share link for the rover-01 dashboard.Invite sam@example.com as an editor.When you ask for something Plexus does not offer, for example a chart colour that is not in the palette, Claude shows you what is available and asks, rather than picking for you.
What it can do today
| Area | You can ask Claude to |
|---|---|
| Overview and setup | See your plan, devices, connections and when data last arrived. Set up a project and send its first reading. |
| Devices | Add, change and remove devices. Group them into fleets. Describe a metric (unit, expected range). Set how long a device keeps its readings. |
| Connections | Connect a database you already run (Postgres, TimescaleDB, QuestDB, MySQL, ClickHouse, InfluxDB), test it, list its tables and columns, run a read-only query, and choose which tables are telemetry. |
| Dashboards | Create and change dashboards and any panel. Import a Grafana dashboard. Duplicate and delete dashboards. Create or turn off a public share link. Publish a panel for embedding. See who viewed a shared dashboard. |
| Data | Read readings, device events and the activity feed. Export readings (Claude returns the size and a download link). Import readings. Add notes to charts. |
| Runs | Start, label, close, edit and delete runs. Compare two runs. |
| Monitors and alerts | Create, change and remove monitors. List alerts. Acknowledge or resolve one with a note, or acknowledge all. Silence a monitor for a while. Delete an alert. |
| Alert delivery and on-call | Choose which Slack channels and email addresses a monitor posts to, and which on-call ladder it calls. Add an alert email address. Choose what a Slack channel hears. Create and change on-call ladders. See who can be on call. |
| Commands | List a device's commands and their history. Run a command on a connected device. |
| Video | List recordings. Start, stop and delete one. |
| Team and keys | See members and roles. Invite someone, change a role, remove a member. Create and change custom roles. List, create and revoke API keys. |
| Workspace and billing | Rename the workspace. Change your timezone. See the plan, usage and this month's estimated bill. Set the bill-alert amount. |
Some things need you in a browser, so Claude hands you a link instead: connecting Supabase by sign-in, connecting a new Slack channel, adding and verifying your own phone number, upgrading, changing the card, cancelling, switching workspace and deleting an account. A command the device marks critical is not run by Claude either: it hands you the Commands page.
How it behaves
Claude acts as the person who approved the connection, with that person's role. Changes Claude makes are real changes to your workspace, and each one appears in the workspace's Activity under your name.
Anything destructive, or that changes who is told or called, or makes data public, is shown to you first and done only after you say yes. Every tool that changes something is labelled as such, and you can ask Claude to show what would change before it does it.
Disconnect
In Claude, remove the connector under Customize → Connectors. In Plexus, revoke its key on the API Keys page: the connection stops at once.
If something goes wrong
- The browser does not open, or sign-in loops. Sign in to app.plexus.company first, in the same browser, then connect again.
- "You need to be an admin or editor." Ask an admin of the workspace to approve, or to change your role.
- Claude says a tool was refused for your plan. Monitors and alerts need Pro. See pricing.
- It connected to the wrong workspace. Disconnect, switch workspace in Plexus, and connect again.
Still stuck? Write to info@plexus.company.