ScalePad MCP

Your AI, wired into client success.

Connect Claude, Cursor, Copilot, or any MCP-compatible client to Lifecycle Manager, ControlMap, and Quoter. QBRs, assessments, compliance, quoting: one server, live data, no ETL. Setup takes about two minutes.

Browse RecipesJump to setup
ScalePad Built & Maintained
SOC 2 / ISO 27001 Compliant
Never Used for AI Training
Data Sovereignty by Region

What MCP unlocks

One connection for the workflows you already run.

ScalePad MCP gives AI tools a structured way to call ScalePad context and actions. Start with Recipes, then expand into product and integration workflows as your team standardizes how agents help with client success.

ScalePad MCP
AI tools connect once, then route work through ScalePad products, vendors, and recipes.

Lifecycle Manager

Roadmaps & GoalsPlanning & schedulingAssessmentsTemplates & scoringTasks & AgreementsAction items & contractsMeetings & DeliverablesQBRs & client reportsAssets & SaaSHardware & shadow IT/AI

ScalePad Surfaces

ScalePad PlatformRecipes, MCP access, and shared data across every productLifecycle ManagerRoadmaps, assessments, QBRs for client success deliveryControlMapCompliance frameworks, risk assessments, and evidenceQuoterQuotes, proposals, and payments from catalog to signed contractBackup RadarBackup monitoring and verification across every platform

Integrations

PSAConnectWise, Halo, Autotask, and moreRMM & BackupDatto, Acronis, Veeam, and moreDistributorsIngram, TD SYNNEX, and moreWorkflowsZapier, n8n, Rewst, and morePublic APIBuild your own

Connection paths

Choose the route that matches how your team wants to use AI.

Start directly in a desktop AI tool, connect an internal workflow, or build alongside ScalePad's platform and integration surface. Each path still points back to the same MCP server and Recipes model.

Direct tool setup

API key

Best for operators who want Claude, Cursor, VS Code, Microsoft Copilot, or another MCP-compatible client to call ScalePad workflows from the tools they already use.

Pick tool
Paste config
Run Recipe
Set up a tool

Platform workflow

ScalePad context

Use MCP as the AI-facing edge of broader client success workflows across Lifecycle Manager, ControlMap, Quoter, and integrations.

Client context
Product workflow
Next action
Explore Platform

Build with ScalePad

Partner-ready

For teams designing deeper integrations or agentic workflows, start with the Platform build surface and MCP documentation instead of a standalone partner detour.

Model workflow
Connect systems
Ship motion
Build on Platform

Three steps. That's the whole job.

01

Choose your MCP-compatible tool.

Claude Desktop is the quickest start, and the same setup model works for Cursor, VS Code, Windsurf, and compatible agent tools.

02

Update your config file.

Pick your tool below, copy the snippet, and drop it into the config file. Replace the API key with yours.

03

Browse Recipes and start prompting.

Recipes are ready-made prompts built for IT workflows. Pick one, copy the starter prompt, and paste it into your AI tool.

Configuration

Pick your tool, copy the snippet.

Replace YOUR_SCALEPAD_API_KEY with your actual key. Restart your AI tool after saving.

Read MCP Docs
claude_desktop_config.json
{
  "mcpServers": {
    "scalepad": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://developer.scalepad.com/mcp",
        "--header",
        "x-api-key: ${API_KEY}"
      ],
      "env": {
        "API_KEY": "YOUR_SCALEPAD_API_KEY"
      }
    }
  }
}
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

FAQ

A few practical MCP questions.

What is MCP?

Model Context Protocol is a standard way for AI tools to connect with external systems. For ScalePad, it gives supported tools a structured connection to Recipes and platform workflows.

Which tools can use the ScalePad MCP server?

The setup page includes Claude Desktop, Cursor, VS Code, and Windsurf. Other tools that support MCP over HTTP can use the same server details and ScalePad API key model.

Do I need a ScalePad API key?

Yes. The config snippets use a ScalePad API key so your AI tool can authenticate with the MCP server. Keep that key private and only add it to trusted local or managed tool configurations.

Where should my team start after setup?

Start with Recipes. They give your team reusable prompts for common MSP workflows, so the first MCP experience is guided instead of a blank chat box.

Can partners build deeper workflows with this?

Yes. Teams building deeper workflows should start with the ScalePad Platform and developer documentation, then align the MCP use case with the systems and products involved.

Recipes

What people run on day one.

Use featured Recipes as the first repeatable motions for MCP-connected AI tools, then adapt them to the clients, products, and systems your team works with every day.

Start with a Recipe, then make it repeatable.

Connect your tool, copy a starter prompt, and give your team a cleaner way to run client success workflows with AI.

Browse RecipesRead MCP Docs