ScalePad MCP
The ScalePad Model Context Protocol (MCP) server lets compatible AI clients connect directly to the ScalePad API reference and, when configured with authentication, make live API calls — all from within your favorite AI-powered editor or assistant.
What the ScalePad MCP server can do
The ScalePad MCP server is powered by ReadMe and exposes the following capabilities to supported AI clients.
Authentication
ScalePad MCP Server URL
Client setup
Choose your AI client below and follow the setup instructions.
Add to ~/.cursor/mcp.json:
{
"mcpServers": {
"scalepad": {
"url": "https://developer.scalepad.com/mcp",
"headers": {
"x-api-key": "SCALEPAD_API_KEY"
}
}
}
}Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"scalepad": {
"serverUrl": "https://developer.scalepad.com/mcp",
"headers": {
"x-api-key": "${env:SCALEPAD_API_KEY}"
}
}
}
}Create .vscode/mcp.json in your workspace:
{
"inputs": [
{
"type": "promptString",
"id": "scalepad-api-key",
"description": "ScalePad API key",
"password": true
}
],
"servers": {
"scalepad": {
"type": "http",
"url": "https://developer.scalepad.com/mcp",
"headers": {
"x-api-key": "${input:scalepad-api-key}"
}
}
}
}Claude Desktop use the Developers UI for remote MCP servers.
claude_desktop_config file rather than using the custom connector flow.- Open Settings → Developer
- Click Edit Config
- Open claude_desktop_config.json
- Enable the connector in the conversation where you want to use it
Local Claude Desktop config for remote MCP server (macOS / Linux):
{
"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"
}
}
}
}On Windows, npx resolves to npx.cmd, which Claude Desktop's process launcher can't execute directly — leaving the command as "npx" fails with spawn npx ENOENT. Wrap it with cmd /c:
{
"mcpServers": {
"scalepad": {
"command": "cmd",
"args": [
"/c",
"npx",
"mcp-remote",
"https://developer.scalepad.com/mcp",
"--header",
"x-api-key: ${API_KEY}"
],
"env": {
"API_KEY": "YOUR_SCALEPAD_API_KEY"
}
}
}
}macOS / Linux — run the following command:
claude mcp add --transport http scalepad https://developer.scalepad.com/mcp \
--header "x-api-key: YOUR_SCALEPAD_API_KEY"On Windows, the trailing \ line continuation isn't valid in PowerShell or Command Prompt. Run it as a single line instead (this also works in any shell):
claude mcp add --transport http scalepad https://developer.scalepad.com/mcp --header "x-api-key: YOUR_SCALEPAD_API_KEY"Verify your .claude.json contains:
{
"mcpServers": {
"scalepad": {
"url": "https://developer.scalepad.com/mcp",
"headers": {
"x-api-key": "SCALEPAD_API_KEY"
}
}
}
}Add the ScalePad MCP server as a tool in Microsoft Copilot Studio.
- Open Microsoft Copilot Studio
- In the left navigation, select Agents, then choose the agent you want to configure
- Navigate to the Tools page for your agent (from the top nav or by scrolling down)
- Select Add a tool → New tool → Model Context Protocol
- Fill in the required fields:
- Server name:
ScalePad - Server description:
ScalePad API and documentation - Server URL:
https://developer.scalepad.com/mcp
- Server name:
- For authentication, select API key, then configure:
- Type:
Header - Header name:
x-api-key
- Type:
- Select Create, then Add tool
- When prompted, enter your ScalePad API key value
- The available tools (e.g.
list-endpoints,search,execute-request) are discovered automatically from the MCP server - Test the connection in the Test your copilot panel by asking something like "List all available ScalePad API endpoints"
For full details, see Microsoft's documentation:
Configure via the Roo Code sidebar:
- Open the Roo Code panel in the VS Code sidebar
- Click the MCP Servers icon (server plug icon at the top of the panel)
- Click Edit MCP Settings to open
mcp_settings.json - Add the following configuration:
macOS / Linux:
{
"mcpServers": {
"scalepad": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://developer.scalepad.com/mcp",
"--header",
"x-api-key: YOUR_SCALEPAD_API_KEY"
]
}
}
}On Windows, npx resolves to npx.cmd, which can't be spawned directly — leaving the command as "npx" fails with spawn npx ENOENT. Wrap it with cmd /c:
{
"mcpServers": {
"scalepad": {
"command": "cmd",
"args": [
"/c",
"npx",
"-y",
"mcp-remote",
"https://developer.scalepad.com/mcp",
"--header",
"x-api-key: YOUR_SCALEPAD_API_KEY"
]
}
}
}Add to ~/.codex/config.toml:
[mcp_servers.scalepad]
enabled = true
url = "https://developer.scalepad.com/mcp"
[mcp_servers.scalepad.env_http_headers]
x-api-key = "SCALEPAD_API_KEY"Testing your MCP setup
Once configured, try any of these prompts in your AI client to verify the connection:
Notes
Updated 1 day ago
