Developers
Everything in the dashboard, for agents and scripts too
Baseboard is an MCP server with 67 tools, a CLI and an SDK for your own endpoint. Agents get the same tools as the pages, held to the permissions of the member whose token they use.
MCP
Point any MCP client at your workspace
Make a token on the Agents & CLI page in workspace settings. Baseboard speaks Streamable HTTP with plain JSON replies, so Claude Code, Cursor and any other MCP client can use it.
Every other tool takes a projectId, which listProjects returns. Calls are in the audit log under token:<id>.
# Claude Code$ claude mcp add --transport http baseboard \ https://your-deployment.convex.site/mcp \ --header "Authorization: Bearer bb_…" # Any client: MCP over Streamable HTTPPOST https://your-deployment.convex.site/mcpAuthorization: Bearer bb_…
Tokens
A token gets a scope, or single tools
A token belongs to one workspace and acts as the member who made it. Give it a whole scope (including tools added to it later) or pick tools by name, and keep it to the projects it needs. Only a SHA-256 of each token is stored.
Readread
List projects and connections, and read customers, data, files, deployments and the rest.
42 tools
Change datachange
Make refunds, bans, rollbacks and other changes, where the token's member is allowed to.
17 tools
Set upsetup
Create projects, connect providers (sign-in links for one-click providers, the CLI for keys) and change dashboard pages.
8 tools
CLI
Connect providers without handing an agent the key
The baseboard-cli package reads the key at a hidden prompt, or from an environment variable or a file, and won’t prompt without a terminal. An agent can run it for you and still never see the secret.
One-click providers
An agent asking to connect Stripe or Vercel gets a sign-in link back for you to open. It can finish the connection once you’re done.
Key providers
The agent gets a CLI command to hand you. You run it in your own terminal and paste the key there.
$ export BASEBOARD_URL=https://your-deployment.convex.site$ export BASEBOARD_TOKEN=bb_… # Asks for the key at a hidden prompt$ npx baseboard-cli connect stripe --project k57abc # A second connection to the same provider$ npx baseboard-cli connect postgres --project k57abc --name analytics # From CI, without a prompt$ npx baseboard-cli connect resend --project k57abc --secret-env RESEND_KEY
Pages as code
Keep your dashboards in the repo
Every page is rows of blocks, and a page reads and writes as JSON. Export them, review changes in a pull request and apply them from CI. Pages left out of a file stay as they are.
101 block types: Connection health, Status beacon, Server map, Deployment map, Uptime status, Big number, Custom metric, Ship heatmap, Credit gauges, Recent deploys, App builds, Errors, Job runs, Data syncs, Uptime, Recent logs, Open pull requests, Recent commits, Sign-ups, Active users, Revenue and subscriptions, Plans, One-time purchases, Billing customers, AI spend, Emails, Users, Accounts, Billing, Subscriptions, Purchases, Across your tools, Organisation, Members, Database browser, File browser, Recurring revenue, Plan mix, Trials ending, Cancellations, Failed payments, New billing customers, Ended subscriptions, Top customers, Revenue by currency, Subscription states, User count, Newest users, Banned users, Recent sign-ins, Dormant users, Organisations, Largest organisations, Noisiest errors, Errors by level, Errors by state, Deploy cadence, Failed deploys, Live now, Host status, Store submissions, Failed builds, Job success rate, Runs by task, Job runs per day, Sync freshness, Response times, Incidents, Monitors down, Log levels, Noisiest services, Stale pull requests, Commits by author, AI tokens, AI budget, Prompt cache hits, Low balances, Mail health, Inbound mail, Mail outcomes, Recent uploads, SQL table, SQL chart, SQL number, Their errors, Their job runs, Their conversations, Their CRM record, Their feature flags, Their mail, Organisation revenue, Organisation errors, Note, Links, Embed, Image, World clocks, Countdown, Alerts, Connections, Team.
$ npx baseboard-cli pages export --project k57abc > pages.json$ npx baseboard-cli pages apply pages.json --project k57abc // pages.json{ "name": "Revenue", "rows": [ [{ "type": "revenue" }, { "type": "signups" }], [{ "type": "deploys", "options": { "productionOnly": true } }] ]}
Custom API
Serve your own data with one endpoint
Users, billing, tables, files, job runs, uptime checks or figures only your app counts can show up in Baseboard like any provider. Requests are signed as Standard Webhooks with the connection’s secret. Throw BaseboardError to show a member a message.
Claude Code skill
Set up Baseboard from your project
The setup-baseboard skill reads your manifests, deploy configs, CI workflows and the names (never the values) of your environment variables. It proposes one plan, then creates the project, connects each provider, links the connections and writes pages. Running it again only adds or updates.
Reference
All 67 tools
What an MCP client sees, by the scope that grants each one. Tools that change data run straight away where the token’s member is allowed to.
Read42
- listProjects
- List the workspace's projects (one per app). Every other tool takes a projectId from here.
- listConnections
- List a project's connections (Stripe, Postgres, Sentry…) with their settings. A provider can be connected more than once under different names; tools that take a `provider` need a connection's `key`.
- listProviders
- Every provider Baseboard can connect, what each offers, and whether it connects by signing in (oauth) or with a key through the CLI (cli).
- listBlockTypes
- Every kind of block a page can hold: what it shows, which connections it needs, its default size and its options as JSON Schema with defaults.
- listPages
- List a project's dashboard pages in order, the one it opens on first, with how many blocks each holds.
- getPage
- A dashboard page as a spec: its rows of blocks with their options and scopes. Edit it and pass it to applyPages to change the page.
- listCustomers
- List every customer, joining auth users and billing customers from every connected provider by email, and the organisations they belong to.
- getBillingSummary
- Monthly recurring revenue per currency (in minor units), subscription counts by state, live subscriptions per plan, the subscriptions at risk (failed payments, cancelling) with their customer, every billing customer with their subscriptions and monthly revenue, and one-time purchases (revenue net of refunds, per product, the newest ones), across every billing connection, or only `provider` when set.
- listInvoices
- List recent invoices for a billing customer.
- listTables
- List the tables (or collections) in a connected database, and whether read-only SQL (runQuery), any SQL (executeSql), cell edits (updateCell) and new rows (insertRow) are available.
- readRows
- Read one page of rows from a table.
- runQuery
- Run read-only SQL. The database refuses writes.
- listDeployments
- List recent deployments.
- listIssues
- List error-tracker issues. With `email`, the ones that customer hit, newest first; with email null, the project's unresolved issues with recent events.
- getActivity
- A customer's last activity, recent events and session replays.
- listFlags
- List feature flags and what a customer gets for each.
- getMailbox
- Emails sent to a customer, and any suppressions on their address.
- listEmails
- Every email the account sent or received, newest first, a page at a time. Null when the provider keeps no mail log.
- listConversations
- A customer's support conversations, newest first.
- getCrmRecord
- A customer's CRM contact: company, deal stage and owner.
- listBuilds
- Recent app builds and store submissions, newest first, with status, version and latest error.
- listJobRuns
- Recent background job runs, optionally only failed ones or only those tagged with an email.
- listSyncs
- Data syncs (pipelines between systems) with their status, last run and latest error.
- searchLogs
- Recent log lines, newest first. `text` matches anywhere in a line ('' for all); `email` keeps only lines about that customer.
- getUptime
- Monitor status and recent incidents.
- getCredits
- Credits left on a prepaid API account, whether it is live, on trial or suspended, and anything else the provider reports wrong.
- getSignups
- New users per UTC day from one sign-in provider, for the `days` days before `until` (YYYY-MM-DD, usually today).
- listUsers
- Every user in one sign-in provider (email, sign-up and last sign-in times, whether banned), and its organisations with their memberships where the provider has them.
- getActiveUsers
- Distinct active people per UTC day from one analytics provider, for the `days` days before `until` (YYYY-MM-DD, usually today).
- listMetrics
- The metrics a connection counts for itself (orders, queue depth and so on): each key, label and how its values read.
- getMetric
- One metric's value per UTC day for the `days` days before `until` (YYYY-MM-DD, usually today), with its definition. `metric` is a key from listMetrics, or '' for the first.
- getAiSpend
- Daily cost (in cents) and token use of an AI model provider for the `days` UTC days before `until` (YYYY-MM-DD, usually today), split by model, API key or project. Per customer where each customer has its own key or project.
- listCommits
- Recent commits on a branch, newest first. Leave `branch` null for the default branch.
- compareCommits
- What `head` has that `base` lacks (commits, branches or tags), and what it lacks that base has. With base the live deploy and head another deploy, that is what making it live would add and undo.
- listPullRequests
- Open pull requests, most recently updated first.
- getChecks
- CI results (check runs and commit statuses) for a branch or commit. Leave `ref` null for the default branch.
- getResources
- The infrastructure one connection reaches (an app, Worker, service, database, backend or bucket), each with an id that links refer to and where it runs: a region with map coordinates, 'edge' for a global network, or unknown where the provider doesn't say.
- getWiring
- Links between the project's resources found in hosts' settings: from each host to every database or backend its environment variables or bindings point at, with the names of those settings. Setting values are never returned. A connection that couldn't be read is listed in `problems`. These are suggestions; the project's links are made on the Infrastructure page.
- getOverview
- Health of every part of one connection at `now` (ms since epoch): the live deploy, failed jobs in the last 24 hours, monitors down, users, active subscriptions and so on. A part the provider fails to answer comes back with tone danger and its error.
- listBuckets
- List the storage buckets a connection can browse, and whether it can make download links and uploads.
- listObjects
- List one page of the files and folders directly under a prefix in a bucket.
- getDownloadLink
- Make a short-lived link that downloads one stored file.
Change data17
- banUser
- Ban an auth user so they cannot sign in.
- unbanUser
- Lift a ban on an auth user.
- cancelSubscription
- Cancel a subscription now or at the end of the billing period.
- refundInvoice
- Refund the full payment of an invoice.
- refundPurchase
- Refund what is left of a one-time purchase.
- executeSql
- Run one SQL statement of any kind, writes included, and return its rows (up to limit) and how many rows it changed.
- updateCell
- Change one cell of one row. The row is picked out by its key columns' values (readRows lists the key columns).
- insertRow
- Add one row to a table. Columns left out take the database default.
- promoteDeployment
- Make an earlier deployment serve production (roll back).
- setIssueStatus
- Resolve, ignore or reopen an error-tracker issue.
- setFlag
- Turn a feature flag on or off for one customer.
- removeSuppression
- Let the email provider send to an address again.
- retryBuild
- Run a failed or canceled build, or a failed store submission, again.
- replayRun
- Run a background job again with the same payload.
- startSync
- Start a run of a data sync now.
- uploadObject
- Start uploading one file: returns a short-lived request (url, method, headers, and formField when the file goes in a multipart form) that sends the file straight to the store.
- deleteObject
- Delete one stored file. It cannot be brought back from here.
Set up8
- arrangeConnections
- File a project's connections under groups (environments, regions, clients) and link their resources (a host and the databases and buckets its code reads; ids from getResources), all or none. Groups that don't exist yet are made, which needs a workspace owner. Pages can then be scoped to a group by name.
- applyPages
- Write dashboard pages from specs (the shape getPage returns), all or none. Each spec replaces the page with its name, or adds a new page; pages not listed stay as they are. Blocks come from listBlockTypes, scopes name groups and connection keys from listConnections. Needs permission to edit pages.
- deletePage
- Delete one of a project's dashboard pages. Needs permission to edit pages.
- createProject
- Create a project (a dashboard for one app) in the workspace. Returns its projectId.
- startConnect
- Start connecting a provider to a project. For a one-click provider it returns a sign-in URL: give it to the person to open and approve, then finish with listPendingConnections, listConnectChoices and finishConnect (or they can finish in the dashboard, where the URL lands). For a key provider it returns a CLI command for the person to run in their own terminal, where they paste the key at a hidden prompt. Never ask anyone to paste a key into the chat.
- listPendingConnections
- One-click connections you started whose sign-in is done but which aren't finished yet. They expire after 30 minutes.
- listConnectChoices
- What a pending connection can connect (a Supabase project, a Vercel site…). null means there is nothing to pick: finish with resourceId null.
- finishConnect
- Finish a pending connection with the chosen resource id (or null when there was nothing to pick). Give a name to add another connection to a provider the project already has; null replaces its unnamed one. Baseboard checks it works before saving.
Give your agent a read-only token first.
Every new token can start on the read scope. Add changes later, tool by tool.