Crear paneles interactivos desde Claude con el conector MCP de Sprucely.io

Watch the Video

Dashboards created through the connector are regular Sprucely.io dashboards. This video gives a quick introduction to Sprucely.io and the kind of interactive dashboard Claude creates in your account. Detailed instructions follow the video.

Sprucely.io introduction and how an interactive dashboard is created and shared (1:25 mins)

What the Claude MCP Connector Does

MCP (Model Context Protocol) is the open standard Claude uses to work with external tools, and Sprucely.io provides a hosted MCP server for it — one of the few Claude MCP servers built for delivering results to people outside Claude. Once connected as a custom connector, Claude can call Sprucely.io directly from a conversation to:

• Create a dashboard from data in the conversation — Claude picks the chart types, layout, and titles, and returns a link that renders the finished dashboard. No SQL, no design work, no infrastructure to set up.

• Look up dashboards already in your account and fetch their details.

• Append new rows to an existing dashboard’s dataset, so a dashboard can grow over time — including from scheduled Claude agents that run while you are away from the keyboard.

The difference from a chart inside the conversation is persistence and reach. A chart or artifact belongs to the chat it was made in; a dashboard created through the connector lives outside it — hosted at a stable URL, persistent across sessions, and shareable with people who have no Claude account. Viewing it also consumes none of your Claude usage: you analyze once in Claude, and any number of stakeholders can open the result.

Dashboards created through the connector are regular Sprucely.io dashboards. They appear in your account next to any dashboard you built through the data-to-dashboard flow, and you can edit, restyle, share, and embed them exactly like any dashboard you created by hand.

Dashboards created from Claude are hosted and persistent — they outlive the conversation and stay interactive on any device.

Connecting Claude to Sprucely.io

The connector endpoint is https://www.sprucely.io/mcp. You add it to Claude as a custom connector, and there are two ways to authenticate: sign in with your Sprucely.io account, or use an MCP API key. The same MCP server works in Claude on the web, in the Claude desktop app, and in Claude Code.

Sign in with your Sprucely.io account (recommended)

Instructions:

1. Open the connector settings - In Claude (web or desktop), go to Settings Connectors and choose Add custom connector.
2. Paste the endpoint - Enter https://www.sprucely.io/mcp as the connector URL and confirm.
3. Sign in to Sprucely.io - Claude opens a Sprucely.io sign-in page. Sign in with your existing account — or, if you do not have one, create it right there in the flow. This path works on the free tier.
4. You are ready to go - The connection completes, and the first dashboard you ask Claude to create shows up in your account immediately.

Use an MCP API key

On any plan you can mint long-lived API keys from your profile page (Profile AI Model Context Protocol (MCP)). A key is shown once at creation and can be revoked at any time, and there is no limit on how many you create. Keys suit headless setups where a browser sign-in is impractical — for example an agent running on a server.

Claude Code

Developers using Claude Code can add Sprucely.io to their Claude Code MCP servers from the terminal:

claude mcp add --transport http sprucely https://www.sprucely.io/mcp

Authenticate when prompted, and the same dashboard tools become available in your Claude Code sessions. Among MCP servers for Claude Code, the practical difference here is where the output lands: as a shareable, hosted dashboard rather than terminal text.

Two Ways to Feed a Dashboard

How current your dashboard stays depends on where its data comes from. Sprucely.io supports two models, and it is worth choosing deliberately:

• Linked online source - A dashboard defined against a data source URL (for example a published spreadsheet or a data feed, optionally narrowed to a range or set of columns) is re-fetched every time someone opens it. It is always current, with no further work from you or from Claude. Today you configure a linked source in the Sprucely.io editor; support for creating linked-source dashboards directly from Claude is on the connector roadmap.

• Data sent by Claude - When Claude sends rows through the connector, Sprucely.io stores them as a dataset in your account’s file storage. The dashboard renders that stored dataset — it is fixed as of the moment it was created, and it changes only when a later connector call appends more rows. Nothing refreshes on its own.

In short: link a source when the data lives at a stable URL and should always be current; send the data when it was produced in the conversation itself — and let your Claude agent append new rows on whatever schedule you give it.

Creating a Dashboard from a Conversation

Once connected, dashboard creation is a plain request — no chart configuration and no query language. For example, after Claude has analyzed a spreadsheet you uploaded:

“Create a Sprucely dashboard from this analysis — monthly revenue as a line chart, revenue by region as a bar chart, and deal size versus close time as a scatter plot. Call it Q2 Sales Review.”

Claude structures the dataset, picks the columns for each chart, and calls the connector. You get back a link to the rendered, interactive dashboard. Six chart types are available — bar, line, area, dot (scatter), cell (heatmap), and hexbin — with aggregation (sum, average, count, median, min, max, standard deviation) and time-based grouping for date columns. A dashboard holds up to 40 charts, and a dataset up to 100 columns.

A single call carries up to 50,000 rows; for larger datasets, Claude sends an initial batch and appends the rest in follow-up calls automatically.

After creation, you can refine the result in the Sprucely.io editor like any other dashboard: rearrange the layout with drag and drop, apply one of the pre-defined color themes or your own palette, and reconfigure individual charts with the chart wizard.

Appending to a Dashboard Run After Run

The append capability is what turns a one-off chart into a living record — the “keep tracking this every week” pattern. Because a later conversation — or a scheduled Claude agent — can add rows to a dashboard created earlier, you can run a weekly pattern like this:

• Week 1 - “Analyze this week’s pipeline export and create a Sprucely dashboard tracking totals by stage.” Claude creates the dashboard; you share the link once.

• Every following week - “Analyze this week’s export and append the results to the pipeline dashboard.” Claude adds the new rows; the same link now shows the longer history.

If you use Claude’s scheduled agents, the weekly step runs without you: the agent performs the analysis and appends the fresh rows each run, and the dashboard’s audience keeps opening the same URL. The dashboard updates when — and only when — an agent run writes to it, so the cadence of your agent is the cadence of your report.

This pattern fits any recurring interactive report: weekly client reporting, sales pipeline reviews, support ticket trends, marketing campaign results, or operational KPIs. The analysis happens in Claude; the record accumulates in Sprucely.io.

Sharing and Embedding Your Dashboard

Ask Claude to share the dashboard and it returns a view link you can send straight to a client or colleague. Anyone with the dashboard link can open it in a browser — no account required, no login, on any device. Viewers get the full interactive experience, including cross-filtering on multi-dimensional charts.

From your Sprucely.io account you can also send a dashboard by email directly to recipients, and switch sharing off again at any time. Step-by-step sharing instructions are in our Excel to dashboard how-to.

Beyond links, dashboards embed wherever your audience already works: in a customer-facing website via iframe, in PowerPoint presentations, and in Google Docs and Slides through the add-ons listed on our connectors page.

Plans and Limits

The connector works on every plan — there is no tier gate on the feature itself. The one thing that scales with your plan is dataset storage: it is metered against your plan’s quota, and the connector reports remaining space clearly if a dataset would exceed it. You can mint MCP API keys and sign in with your account on any plan, including free, with no limit on the number of keys. See pricing for current storage quotas and plan details.

Conclusion

Claude does the analysis; Sprucely.io turns it into a persistent interactive dashboard your clients and executives open from a link or an email — no Claude account, no login, and none of your Claude usage spent on viewers. Connect the two once, and an insight produced in a conversation becomes a dashboard you can send, embed, and keep growing.

Add the Sprucely.io connector in Claude’s settings with the endpoint https://www.sprucely.io/mcp, or from Claude Code with claude mcp add. Then ask Claude for your first dashboard, refine it in the editor if you like, and share the link.

If you prefer to build dashboards directly from your files, our Excel to dashboard how-to covers the same result without Claude, and the PowerPoint dashboard how-to shows how to present the finished dashboard in your slides.

Sign up for free with Sprucely.io to get started. You can also check out our getting started guide or compare subscription plans first.

This article was first published 1st July 2026.

Frequently Asked Questions

Question: How do I connect Claude or Claude Code to the Sprucely.io MCP server?

Short answer: In Claude (web or the desktop app), go to Settings, then Connectors, choose Add custom connector, and paste https://www.sprucely.io/mcp. Claude opens a Sprucely.io sign-in page where you sign in or create a free account. In Claude Code, run claude mcp add --transport http sprucely https://www.sprucely.io/mcp and authenticate when prompted.

Question: How is a Sprucely.io dashboard different from a chart in the Claude conversation?

Short answer: Persistence and reach. A chart in a conversation belongs to that conversation; a dashboard created through the MCP connector is hosted at a stable URL, persists across sessions, can be appended to by later runs, and opens for people with no Claude account — without consuming any of your Claude usage.

Question: Do the people I share a dashboard with need a Claude or Sprucely.io account?

Short answer: No. Anyone with the view link can open the interactive dashboard in a browser — no Claude account, no Sprucely.io login, no software install, on any device. You can also send the dashboard by email from your account, and switch sharing off again at any time.

Question: Which chart types and dataset limits does the connector support?

Short answer: Six chart types — bar, line, area, dot (scatter), cell (heatmap), and hexbin — with aggregation (sum, average, count, median, min, max, standard deviation) and time-based grouping for date columns. A dashboard holds up to 40 charts, a dataset up to 100 columns, and a single call carries up to 50,000 rows; Claude appends larger datasets in follow-up calls automatically.

Question: Can a dashboard update itself after it is created?

Short answer: It depends on the data model. A dashboard defined against a linked online source is re-fetched every time someone opens it, so it is always current. A dashboard built from data Claude sent is fixed until a later connector call appends rows — which is exactly what a scheduled Claude agent can do run after run, keeping the same shared link up to date.

Question: Does the MCP connector work on the free plan?

Short answer: Yes. The connector works on every plan with no tier gate on the feature; only dataset storage is metered against your plan’s quota. You can sign in with your account or mint an unlimited number of MCP API keys on any plan, including free. See the pricing page for storage quotas.