CompSlate

com.compslatePublished by compslate.comOfficial publisherv1.0.0Updated Oct 24, 2026

Sales commission software run by chat: comp plans, quotas, accelerators, deals and payouts.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

CompSlate is a remote MCP server for sales commission software, letting an assistant work with comp plans, quotas, accelerators, deals and payouts through chat.

What you can do
  • Manage sales compensation plans and their rules, including accelerators.
  • Work with quotas and deal data used to calculate commissions.
  • Review and handle payouts tied to those deals.
  • No tool list is published, so the exact operations available are not documented here.
When to use it
Worth adding when a sales ops or finance team already uses CompSlate and wants an assistant to look up or adjust commission plans, quotas, deals and payouts in chat instead of the web app.
Requirements
A remote MCP endpoint at compslate.com over streamable HTTP. OAuth authentication is required, so a CompSlate account with the appropriate access is needed. No environment variables or headers are declared.
Before you install
The server handles compensation and payout data, so treat plan, quota, deal and payout changes as sensitive and financially consequential. OAuth grants the assistant access to your CompSlate account; review the scopes and confirm whether actions write or only read before connecting.

Installation

In SourceWeft

  1. Open CompSlate 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.compslate%2Fcompslate/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": {
    "compslate": {
      "type": "http",
      "url": "https://compslate.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.0LatestSep 27, 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.