Skip to content

Guides

Install the connector

Add Dashies to Claude Code, Codex, Cursor, or Claude web and desktop, so your AI tool can publish dashboards and keep them refreshing.

Dashies is driven from the AI tool you already use. Installing the plugin is the supported path: it bundles the dashies authoring skill and the publish service together, and the skill is most of the product's behaviour.

A bare connector is not the same install

Adding only the MCP server gives your AI the publish tools and the service's own brief instructions, but not the dashies authoring skill, which is where the authoring behaviour is actually decided: how to design a cube, which materialization to pick, and when a measure is not safe to sum.

Install the plugin wherever your tool supports one. Use the connector-only path below only for surfaces that cannot install a plugin.

Pick your tool

Choose one install path for each tool. In particular, do not combine the Codex tab with the multi-client command under Any other tool. They install the same Dashies plugin through different marketplaces, which makes Codex show two install cards.

Run both commands in your shell. The first registers the Dashies marketplace, the second installs the plugin from it.

claude plugin marketplace add https://dashies.ai/marketplace.json
claude plugin install dashies@dashies --scope user

--scope user installs Dashies for you in every project, rather than into whatever directory you happen to be in. It is already this command's default, and it is written out because that one choice decides whether the dashies skill exists in your next repository. Pick a project or local scope only if you are deliberately checking Dashies into one repository for the people who work in it.

dashies@dashies is <plugin>@<marketplace>. Both are named dashies, which is correct and not a typo.

A shell command cannot reach a Claude Code session that is already running. Run /reload-plugins in it afterwards, or start a new session.

If you would rather stay inside Claude Code, the same install is two slash commands:

/plugin marketplace add https://dashies.ai/marketplace.json
/plugin install dashies@dashies

/plugin install takes no scope flag. It opens the plugin's details pane and asks where to install, so choose Install for you (user scope). The other two options bind Dashies to the directory you are in, and it will not be there when you open a different repository.

This bundles the dashies authoring skill and the publish MCP. Your first publish opens the browser to sign in, and there is no token to paste.

Run both commands in your shell.

codex plugin marketplace add Dashies-ai/dashies-plugin
codex plugin add dashies@dashies

Then sign in over OAuth:

codex mcp login dashies

This bundles the dashies authoring skill and the publish MCP.

If you already ran npx plugins add Dashies-ai/dashies-plugin, Codex is already set up as dashies@plugins-cli. Do not run the commands above afterward; the native route registers the same plugin separately as dashies@dashies.

Cursor takes two steps, because it installs the connector and the skill by different routes.

First, add the publish connector with the one-click install link:

Add to Cursor

That config value is base64 for {"url":"https://mcp.dashies.ai/mcp"} - the same endpoint as the manual mcp.json below.

Then add the authoring skill:

npx skills add Dashies-ai/dashies-plugin --global --agent cursor

--global installs at user level rather than into whatever directory you happen to be in. It writes ~/.agents/skills/dashies/SKILL.md, which is one of Cursor's user-level skill roots. It works whether or not the cursor shell command is on your PATH.

Restart Cursor once both are done. Your first publish opens the browser to sign in, and there is no token to paste.

If the one-click link does not land, add the connector by hand to ~/.cursor/mcp.json:

{
  "mcpServers": {
    "dashies": { "url": "https://mcp.dashies.ai/mcp" }
  }
}

Claude web, desktop, and Cowork add Dashies as a custom connector. A connector can only add the MCP server, so on these surfaces the dashies authoring skill is not installed. Publishing works; the authoring guidance that makes a dashboard correct does not come with it.

The connector URL is:

https://mcp.dashies.ai/mcp
  1. In Claude, open Settings, then Connectors.
  2. Click the plus button, then Add custom connector.
  3. Paste the URL above, then click Add.

Open Claude connectors

Sign-in opens once, and there is no token to paste.

One command auto-detects every plugin-capable AI agent on your machine and installs the Dashies plugin into each:

npx plugins add Dashies-ai/dashies-plugin

This always delivers the authoring skill, never a bare connector.

On Windows its agent detection is still maturing, so prefer the per-tool tabs above there.

When this command detects Codex, it installs dashies@plugins-cli. Use that or the Codex tab's native dashies@dashies route, never both.

Check it worked

Ask your AI tool to list your dashboards. In plain language:

List my Dashies dashboards.

Three things should happen, in order:

  1. Your tool calls the list_dashboards tool.
  2. A browser window opens once, asking you to sign in with Google and to pick the workspace the tool may publish into. In Claude Code the browser opens when you run /mcp, select dashies, and choose Authenticate. See Sign in and authorize.
  3. You get back a list, which is empty on a new account. An empty list is a pass. The tool call completing at all is the signal.

If your tool reports no Dashies tools

Two different things produce that, and only one of them is a failed install. Re-running the install commands repairs the first and reproduces the second, so find out which one you have before you re-run anything.

In Claude Code, ask your shell which installs exist:

claude plugin list

dashies@dashies is not listed. The install did not happen. Re-run the commands for your tab above, then restart the tool.

dashies@dashies is listed and its Scope reads project or local. The install worked and is bound to one directory. In every other repository the plugin is not loaded, the dashies skill does not exist, and asking for it answers Unknown skill: dashies. Nothing is broken, and installing it the same way again lands in the same place. Install it once at user scope instead, from any directory:

claude plugin install dashies@dashies --scope user

Then run /reload-plugins in Claude Code, or start a new session. Scopes coexist, so there is nothing to uninstall first. To clear a directory-bound record, run claude plugin uninstall dashies@dashies --scope project from that directory. Leaving it costs nothing. If that install command cannot find the marketplace, register it at user scope first with claude plugin marketplace add https://dashies.ai/marketplace.json, which has a scope of its own.

dashies@dashies is listed and its Scope reads user. The install is right and the session has not picked it up. Run /reload-plugins, or start a new session.

On the other tools, no Dashies tools means the install did not complete. Re-run the commands for your tab above and restart the tool.

A newly installed tool argument can be missing

An MCP client reads each tool's schema once, when the session connects. If you installed or upgraded Dashies inside a session that was already running, a newly shipped argument is simply absent, as if it had never been built. Start a new top-level session after installing.

Next