Skip to main content
Tools are external integrations that Agents can call when answering questions. They are built on the Model Context Protocol (MCP) — an open standard that lets AI models interact with outside systems: internal APIs, third-party services, custom scripts, or any HTTP/SSE endpoint you expose. When an agent needs information or capabilities that don’t exist in your connected databases, it can invoke a Tool to fetch or compute what it needs. Tools extend what agents can do without requiring you to load everything into a data source.
Not to be confused with connecting Supaboard to Claude. This page is about tools that Supaboard calls out to. If you want to query your Supaboard data from inside Claude, that’s the opposite direction — see Connect Supaboard to Claude.

​
The MCP & Tools Page

Navigate to MCP & Tools in the sidebar (or press Cmd+9) to see all tools registered in your workspace.

​
Display modes

Toggle between Card grid and Table view using the view switcher. Table view columns: Use the search bar to filter tools by name. Search is fuzzy — partial matches are included.

​
Refresh

Click the Refresh button in the topbar to reload the tools list from the server.

​
Adding a Tool

Click New Tool to open the Add New Tool form.

​
Required fields

​
Optional fields

Tools added here become selectable in Ask Analysts via + → Add Tool(s).

​
What happens when you save

  1. Supaboard pings the endpoint to verify it is reachable before creating the record.
  2. If the ping succeeds, the tool is created and appears in the list.
  3. If the ping fails, the tool is not saved — check the URL, token, and that the server is running.
The connectivity check at creation time prevents broken tools from appearing in the list. If your server is temporarily down during setup, wait for it to come back online before adding the tool.

​
Transport Types: HTTP vs SSE

MCP supports two transport mechanisms. Choose the one that matches how your server is built. If you are unsure, start with http. It works for the vast majority of integrations.

​
Tool Detail & Execution History

Click any tool in the list to open its detail page.

​
Execution history panel (left)

A chronological log of every time this tool was invoked. Each entry shows:
  • The tool name and icon
  • The exact timestamp of the execution
Click any entry to load the full execution detail on the right.

​
Execution detail panel (right)

All text fields have a copy button for easy sharing or debugging.
Execution history is your primary debugging surface. If an agent is giving unexpected answers when a tool is involved, check the Input Parameters and Final Output here to see exactly what was sent and received.

​
Testing Connectivity

You can test that a tool’s endpoint is reachable at any time without running a full invocation. Open the tool’s action menu (three-dot icon) and select Test Connectivity. Supaboard pings the configured URL and token and reports back:
  • Success: A toast confirms the endpoint is responding.
  • Failure: A toast shows the error — use this to diagnose network issues, expired tokens, or server downtime.

​
Access Control

By default, a tool is accessible to all workspace members. You can restrict it to specific users. Open the tool’s action menu and select Access Control. A list of all workspace members appears with toggle switches: Click Save Changes to apply. Changes take effect immediately.

​
Deleting a Tool

Open the tool’s action menu and select Delete Tool. The tool is removed immediately — no confirmation step. What happens on deletion:
  • The tool record and all its execution logs are removed.
  • Any agent that was invoking this tool will no longer be able to call it.
  • Active conversations that relied on this tool will receive errors if it is invoked again.

​
Permissions

Access to this section is controlled by the MCP and Tools feature flag on each user’s workspace membership — see Workspace — Feature Access.
Last modified on August 7, 2026