resend.send_email
Needs approval
to: 14 recipients (this week's verified signups)
from: "[email protected]"
subject: "Welcome to Northwind, <first_name>"
body: personalized per recipient · tailored to features set up
MCP connectors
Connect any app.
Take action anywhere.
Basedash already reads from your databases and SaaS tools. Plug in an MCP server and it can act on them too — email signups, file issues, update leads, anywhere the agent can reach.
14-day trial. No credit card required.
Chats / Weekly signup welcome
Resend · MCP
Email this week's signups a personalized welcome based on the features they actually set up.
Read this week's signups from Production DB
Read activation events to find features used
Send a personalized email via Resend
Ask the agent…
Connect any app
If it speaks MCP, it works.
Plug Linear, HubSpot, Slack, Resend, Notion, GitHub, or any other remote MCP server into Basedash — including your own internal one.
Linear
mcp · linear.app
HubSpot
mcp · hubspot.com
Slack
mcp · slack.com
Resend
mcp · resend.com
Notion
mcp · notion.so
GitHub
mcp · github.com
Stripe
mcp · stripe.com
Intercom
mcp · intercom.com
Bring your own
Point Basedash at any remote MCP server — streamable HTTP or SSE, OAuth if required.
https://your-mcp.example.com/mcp Examples
Read your data. Act in another app.
Ask the agent to do something that joins what's in your database with an action somewhere else.
"Email this week's signups a personalized welcome based on the features they actually set up."
Reads
Production DB Product events
Acts via
Resend · send_email
"File a Linear bug from this support ticket and link the user record."
Reads
Intercom Production DB
Acts via
Linear · create_issue
"Update the HubSpot lead for everyone who hit the paywall this week."
Reads
Production DB
Acts via
HubSpot · update_lead
Approval gating
Trust the tools you've vetted. Gate the rest.
Every synced tool gets an access mode. New tools default to needs approval — flip them to always allow once you trust them, or block them entirely.
Always allow
Trusted tools run without interruption — read-only lookups, well-scoped helpers, anything you've vetted.
Needs approval
Higher-stakes actions pause for a human review with the full payload before they run. New tools start here.
Blocked
Anything you don't want the agent to touch — flip a tool off and it disappears from the available toolset.
Workspace access
Scope each connector to the right people.
Connectors carry their own audience. Open them up to the whole org, restrict them to a team, or hand them to a single operator.
Everyone in the org
Make a connector available to all members when the underlying app is for general use.
Specific groups
Scope connectors to a team — only Support sees Intercom, only Growth sees HubSpot.
Specific members
Hand a connector to one or two operators when the action is sensitive or scoped to a role.
Stacks with automations
Run the same flow on a schedule.
Any tool an MCP connector exposes is available to Automations too. Turn a one-off agent run into a daily welcome email, a weekly HubSpot refresh, or a real-time bug-filing pipeline.
Daily ICP welcome
Trigger Every weekday at 09:00
Tools
send_email update_lead create_issue
Last run · 09:00
Sent · 14 emails
MCP connectors FAQ
What is an MCP connector in Basedash?
An MCP connector lets you plug an external Model Context Protocol server — Linear, HubSpot, Slack, Resend, Notion, GitHub, an internal one, or any other — into your Basedash workspace. Once connected, the tools that server exposes become available to the Basedash agent inside chat, so it can take actions in those systems alongside reading from your data sources.
Which apps work with MCP connectors?
Any app that exposes a remote MCP server. Common connectors include Linear, HubSpot, Slack, Resend, Notion, GitHub, Stripe, and Intercom, but any service that speaks streamable HTTP or SSE MCP can be added. You can also point Basedash at your own internal MCP server.
How do I add an MCP connector?
Open the command menu, go to Data sources, choose Add MCP server, and enter a name plus the remote MCP server URL. Add any required headers, save, and complete the OAuth flow if the server prompts for it. Basedash then syncs the tools the server exposes.
How is this different from the Basedash MCP server?
The Basedash MCP server lets external AI clients (Claude Code, Cursor, ChatGPT, etc.) read your Basedash data. MCP connectors go the other direction: you plug external MCP servers into Basedash so the Basedash agent can use their tools. Most teams use both.
Can I control which tools the agent is allowed to use?
Yes. Every synced tool has an access mode: Always allow, Needs approval, or Blocked. New tools default to Needs approval — the agent has to ask before it runs, so you see the exact payload first. Once you trust a tool you can flip it to Always allow, or block it entirely.
Who in my workspace can use a connector?
Connector access is configurable at the workspace level. You can make a connector available to everyone in the organization, restrict it to specific groups, or scope it to individual members. This keeps sensitive connectors — Stripe, customer data tools — in the hands of the people who should be using them.
Do MCP connectors work with Automations?
Yes. Any tool an MCP connector exposes is also available to scheduled Automations, so the same flow that runs once on demand can run every weekday at 9am. Pair MCP connectors with Automations to turn one-off agent runs into recurring workflows.
Get started in under 30 minutes
We can help you migrate your data and dashboards from any other tool.