Connected services
Connect services such as Jira, HubSpot or Fullstory over MCP, so the analyst and your dashboards can read what lives only there, and change things only when you allow each call.
Some of what you need lives outside your database: tickets in Jira, deals in HubSpot, sessions in Fullstory. Owners and admins connect such services as MCP servers, and the analyst can then read them beside your data, and dashboards can show them.
Add a server
Under Settings → Connections, press Add an MCP server and enter its address. OpenDash checks that it speaks MCP and how it signs in (OAuth sign-in, an API key, or no sign-in), and registers itself where the server allows it.
Then choose whose account it uses:
| Account | What people see |
|---|---|
| Each person's own (recommended) | Everyone connects their own account and sees only what it can see. |
| One account for everyone | One shared account, connected by an admin. Everyone sees the same data. |
Tools
Once connected, the server lists its tools. Each is marked Reads or Changes things, and an admin sets each one to:
- Always: used without asking;
- Ask first: each call is shown to the person before it runs;
- Blocked: never used.
Separate switches decide what dashboards may use: Dashboards may read with it, and for a tool that changes things, whether a dashboard may offer it as a row's button.
Your connections
Settings → My connections lists every server, grouped into Needs you, Yours, Not connected yet and Shared with everyone. Connect your own account to a server here, or disconnect it.
What the analyst may do
- Read with the tools an admin allowed, as you: with your own account, or the shared one.
- Change things only when you allow it. The call is shown exactly as it would be sent, and runs only when you press Allow once. Not now skips it. A change is sent at most once, even across a restart.
- Never delete or overwrite. A tool that may do either (the server says so, or doesn't say it doesn't) is never called.
- Routines, runs nobody is watching, and dashboards only read. A dashboard's row buttons are the exception: each press is confirmed by the person pressing it, with their own account.
From Slack, the analyst uses only servers shared with everyone. A call that needs a sign-in or an approval asks you to allow it in OpenDash.
Turning it off
On a self-hosted instance, OPENDASH_MCP=0 turns connected services off: Settings hides them, the analyst isn't offered them, and nothing calls a server. See Configuration.
Dashboards
Describe who a dashboard is for and what they do with it. The analyst plans it, builds it while you watch, and every number on it stays a query you can open.
Routines and insights
Make things happen on their own. Ask a question every Monday, get what OpenDash found, or watch your metrics and get told what moved and why.