Skip to content
Dash
Get started for free Get started for free

Connect a custom MCP server

Dash connects to 1,000+ tools through its built-in catalog. But if you have your own MCP server, an internal API exposed as MCP, or a tool that isn’t in the catalog, you can connect it directly.

MCP (Model Context Protocol) is an open standard that lets AI agents call tools on a server. If your tool speaks MCP, Dash can use it.

What you need

Section titled “What you need”
  • The URL of your MCP server (must be HTTPS and publicly reachable, or reachable from Dash’s infrastructure).
  • An authentication method: static bearer token or OAuth 2.0.
  • Admin access to the Dash workspace.

Connect with a static bearer token

Section titled “Connect with a static bearer token”

This is the simplest path. Your server expects a fixed API key or token in the Authorization header.

  1. Go to app.dashpup.ai and open the Tools page.
  2. Click Add custom. The dialog opens on the MCP tab by default.
  3. Enter the server URL.
  4. Choose Bearer token as the auth method.
  5. Paste the token. Dash stores it encrypted and never exposes it after this step.
  6. Click Connect. Dash will probe the server, discover its tools, and list them.

You can also ask Dash in Slack or Teams:

@Dash connect a custom MCP server

Dash will walk you through the same steps via a link.

Connect with OAuth

Section titled “Connect with OAuth”

If your MCP server uses OAuth 2.0 (for example, it’s a SaaS product with per-user authorization), the flow is similar but adds a browser redirect:

  1. On the Tools page, click Add custom. The dialog opens on the MCP tab by default.
  2. Enter the server URL.
  3. Choose OAuth as the auth method.
  4. Fill in the OAuth client ID and client secret (if required, some servers use dynamic client registration and don’t need these).
  5. Click Connect. You’ll be redirected to the server’s authorization page.
  6. Authorize Dash. You’ll be redirected back, and the connection goes live.

What Dash discovers

Section titled “What Dash discovers”

Once connected, Dash reads the server’s tool catalog automatically. Each tool the server exposes appears on the Tools page under that connection, with its name and description. From there you can:

  • Set each tool’s run mode: auto, ask, or off. Write tools default to ask (requires approval). Read tools default to auto.
  • Set the access scope: workspace (everyone can use it) or private (only you and people you add).
  • Assign approvers per tool.

These are the same controls you get with any built-in tool connection. See How approvals work for details.

Branded MCP servers

Section titled “Branded MCP servers”

Some tools in Dash’s catalog are pre-configured MCP servers with a branded connect experience (one-click OAuth, no URL entry). These include integrations like Linear, Process Street, and Atlassian Rovo. They show up in the catalog alongside the standard OAuth tools. Connecting them works the same way as connecting your first tool.

Troubleshooting

Section titled “Troubleshooting”

“Connection failed” after entering the URL. Dash couldn’t reach the server. Check that the URL is correct, the server is running, and it’s reachable over HTTPS from the public internet.

No tools discovered. The server responded but didn’t list any tools. Make sure your server implements the MCP tools/list method.

Auth errors after connecting (static bearer). If the API key or token was rotated, open the connection on the Tools page and click Rotate key. Enter the new value and save. Your run-mode settings, access list, and approvers are all kept; only the stored credential changes. There is no need to disconnect and reconnect.

Auth errors after connecting (OAuth). If the OAuth grant was revoked, disconnect and reconnect to re-authorize.

What’s next

Section titled “What’s next”