Dealboard

com.getdealboardPublished by getdealboard.comOfficial publisherv1.0.35Updated Oct 25, 2026

Simple deal tracker with pipeline cards, notes, goals, reports, and AI-powered deal updates.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Dealboard is a remote MCP server for a simple deal tracker, letting an assistant work with pipeline cards, notes, goals, reports and AI-powered deal updates.

What you can do
Track deals on pipeline cards and move them through stages, as described for the tracker's pipeline view. Capture and review notes attached to deals. Work with goals and reports summarizing deal activity. Apply AI-powered deal updates to keep records current. The manifest lists no individual tools, so exact operations are not documented here.
When to use it
Use it when you want an assistant to help maintain a sales or deal pipeline in Dealboard: updating cards, keeping notes, and reviewing goals and reports without switching apps.
Requirements
A remote endpoint at app.getdealboard.com over streamable HTTP. OAuth authentication is required, so a Dealboard account and an OAuth sign-in flow are needed. No environment variables or headers are declared.
Before you install
The server requires OAuth access to your Dealboard account, so the assistant can read and likely change your deal data, notes, goals and reports. AI-powered deal updates may modify records; review changes before relying on them. Deal data is held by the third-party service.

Installation

In SourceWeft

  1. Open Dealboard in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.getdealboard%2Fdealboard/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "dealboard": {
      "type": "http",
      "url": "https://app.getdealboard.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.35LatestSep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.