Connect the MCP Server
Install and connect the BEEM MCP server to Claude, GitHub Copilot, ChatGPT, or any MCP-compatible AI assistant.
Connect the BEEM data platform to AI assistants. Explore workspaces, query datasets, build SQL views, monitor pipelines, and manage dashboards — all through natural language.
Quick StartIn Claude, open the BEEM listing in the connectors directory and click Connect.
In another assistant, paste this in:
Add the BEEM MCP server with URL
https://mcp.beemdata.com/mcpusing HTTP transport at user scope. It uses OAuth — I'll authenticate when prompted.
Server URL
https://mcp.beemdata.com/mcp
Setup by Client
Open the BEEM listing and click Connect, or find it from inside Claude:
- Select Customize in the sidebar, then Connectors
- Click the + button next to Connectors
- Search for BEEM and select it
- Click Connect and sign in with your BEEM account
Turn BEEM on or off for a given chat from the + button in the message box, under Connectors.
An admin enables BEEM once for the organization, then each member connects their own BEEM account.
Admin setup:
- Go to Organization settings → Connectors
- Click Browse connectors at the bottom of the page
- Find BEEM in the directory and click Add to your team
Enabling BEEM makes it available to your team — it doesn't sign anyone in. Each member still authenticates with their own BEEM account, so BEEM permissions are always per-user.
Member setup:
- Select Customize in the sidebar, then Connectors
- Find BEEM in the list
- Click Connect and sign in with your BEEM account
On Team plans, members who can't enable connectors themselves see a Request button on the BEEM listing. Clicking it sends the request to your admins.
Open the BEEM listing and click Connect, or find it from inside Claude:
- Select Customize in the sidebar, then Connectors
- Click the + button next to Connectors
- Search for BEEM and select it
- Click Connect and sign in with your BEEM account
Your connectors are shared across Claude.ai, Claude Desktop, and the mobile apps — connect once and BEEM is available everywhere you're signed in.
Run this in your terminal:
claude mcp add --transport http --scope user beemdata https://mcp.beemdata.com/mcpThe --scope user flag makes BEEM available in all your projects. A browser window opens to authenticate on first use.
Add to your VS Code settings JSON:
{
"mcp": {
"servers": {
"beemdata": {
"type": "http",
"url": "https://mcp.beemdata.com/mcp"
}
}
}
}Or create a .vscode/mcp.json in your project:
{
"servers": {
"beemdata": {
"type": "http",
"url": "https://mcp.beemdata.com/mcp"
}
}
}Restart VS Code. Copilot will prompt you to authenticate on first use.
- Go to Settings → MCP Servers
- Click Add Server
- Enter the server URL:
https://mcp.beemdata.com/mcp - Authenticate with your BEEM account when prompted
Any client that supports Streamable HTTP transport will work.
| Server URL | https://mcp.beemdata.com/mcp |
| Auth | OAuth 2.0 with PKCE (authorization code flow) |
| Discovery | https://mcp.beemdata.com/.well-known/oauth-authorization-server |
| Registration | Dynamic client registration supported |
Examples
"Show me the datasets in my workspace and query the first one"
Retrieves your workspaces, lists available datasets, fetches details including SQL and schema, then queries content and returns sample rows.
"Create a dataset called 'Monthly Revenue' that aggregates revenue by month, then deploy it"
Creates a new dataset, saves SQL as draft, previews results, then deploys it as a live Redshift view with scheduling.
"Check if any of my data pipelines failed in the last 24 hours"
Lists recent pipeline events filtered by failure status, identifies affected datasets and sources, shows error details and DPU usage.
Troubleshooting
BEEM isn't showing in your connectors list
Add it with the server URL instead. Go to Customize → Connectors, click Add custom connector, enter name BEEM and URL https://mcp.beemdata.com/mcp, then click Add. On Team and Enterprise plans, an admin does this from Organization settings → Connectors → Add → Custom → Web.
Session terminated / Session expired
Your session may have been lost after a server update. Simply retry — the client will re-authenticate automatically.
Authentication fails or loops
Make sure you're signing in with a BEEM account that has access to at least one workspace. Try disconnecting and reconnecting the MCP server.
Tool returns 'not found' errors
The MCP server uses your BEEM permissions — you can only access resources your account has access to. Verify you have access to the workspace or dataset in question.
Need help? Contact [email protected]
Updated about 1 month ago
