Scout MCP Server
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Scout MCP Server list my apps"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Scout MCP Server
An MCP (Model Context Protocol) server that wraps the Scout SDK, enabling AI agents to interact with Scout Live platform capabilities through standardized MCP primitives.
What is MCP?
The Model Context Protocol is an open protocol that enables seamless integration between LLM applications and external data sources and tools. It provides:
Resources: Context and data for AI models
Prompts: Templated messages and workflows
Tools: Functions for AI models to execute
Related MCP server: Enterprise MCP Gateway and Tool Registry
Features
This MCP server exposes Scout Live capabilities as:
Tools (Actions)
Tool | Description | Auth Required |
| List user's apps | User |
| Create a new app | User |
| Deploy app version | App (owner) |
| Get app logs | App |
| Get port adapter config | App |
| Set port adapter mapping | App (owner) |
Resources (Data)
Resource | Description | Auth Required |
| List of all apps | User |
| Available adapters | Public |
| App details | App |
Prompts (Workflows)
Prompt | Description |
| Create and deploy a new app |
| Investigate app errors |
Installation
# Clone the repository
git clone https://github.com/scoutos-labs/scout-mcp-server.git
cd scout-mcp-server
# Install dependencies
bun install
# Build
bun run build
# Run with stdio transport (local use)
bun run start
# Run with HTTP transport (server mode)
bun run start:httpConfiguration
Environment Variables
Copy .env.example to .env and configure:
Variable | Description | Required |
| Scout Live API key | Yes |
| API endpoint (default: https://scoutos.live) | No |
| Transport mode: | No (default: stdio) |
| HTTP server port | No (default: 3000) |
For Claude Desktop
Add to your Claude Desktop config:
{
"mcpServers": {
"scout": {
"command": "bun",
"args": ["run", "/path/to/scout-mcp-server/dist/index.js"],
"env": {
"SCOUT_API_KEY": "your-api-key"
}
}
}
}For Claude Code
{
"mcpServers": {
"scout": {
"command": "bun",
"args": ["run", "/path/to/scout-mcp-server/dist/index.js"],
"env": {
"SCOUT_API_KEY": "your-api-key"
}
}
}
}Development
# Run tests
bun run test
# Run tests in watch mode
bun run test:watch
# Run with coverage
bun run test:coverage
# Lint
bun run lintDeployment to scoutos.live
Prerequisites
DigitalOcean Container Registry access
kubectl configured for scout-live cluster
Scout Live namespace exists
Deploy
# Build and deploy
./deploy.sh v0.1.0
# Or manual steps:
# 1. Build
bun run build
# 2. Build Docker image
docker build -t registry.digitalocean.com/scout-live/mcp-server:v0.1.0 .
# 3. Push to registry
docker push registry.digitalocean.com/scout-live/mcp-server:v0.1.0
# 4. Apply Kubernetes manifests
kubectl apply -f k8s/deployment.yaml -n scout-live
kubectl apply -f k8s/ingress.yaml -n scout-live
# 5. Update deployment image
kubectl set image deployment/scout-mcp-server \
mcp-server=registry.digitalocean.com/scout-live/mcp-server:v0.1.0 \
-n scout-liveVerify Deployment
# Check pod status
kubectl get pods -n scout-live -l app=scout-mcp-server
# Check logs
kubectl logs -f deployment/scout-mcp-server -n scout-live
# Health check
curl https://mcp.scoutos.live/healthAccess Endpoints
After deployment, the MCP server is available at:
Endpoint | Description |
| Server capabilities |
| Health check |
| SSE transport endpoint |
Architecture
┌──────────────────────────────────────────────┐
│ MCP Host (Claude, etc.) │
└─────────────────────────┬────────────────────┘
│
▼
┌──────────────────────────────────────────────┐
│ Scout MCP Server (this repo) │
│ │
│ ┌─────────┐ ┌─────────┐ ┌─────────────┐ │
│ │ Tools │ │Resources│ │ Prompts │ │
│ └────┬────┘ └────┬────┘ └──────┬──────┘ │
│ │ │ │ │
│ └────────────┼──────────────┘ │
│ │ │
└────────────────────┼─────────────────────────┘
│
▼
┌──────────────────────────────────────────────┐
│ Scout Live API │
│ (scoutos.live) │
└──────────────────────────────────────────────┘API Reference
Tools
app_list
List all apps for the authenticated user.
{
"name": "app_list",
"arguments": {}
}app_create
Create a new app on Scout Live.
{
"name": "app_create",
"arguments": {
"name": "My App",
"slug": "my-app" // optional, auto-generated if not provided
}
}deploy
Deploy a new version of an app.
{
"name": "deploy",
"arguments": {
"slug": "my-app",
"files": {
"index.html": "<html>...</html>",
"style.css": "body { ... }"
}
}
}logs
Get recent logs for an app.
{
"name": "logs",
"arguments": {
"slug": "my-app",
"lines": 100 // optional
}
}Resources
scout://apps
List all apps.
scout://adapters
List available port adapters.
scout://app/{slug}
Get details for a specific app.
Prompts
deploy-new-app
Create and deploy a new app.
{
"name": "deploy-new-app",
"arguments": {
"name": "My App",
"type": "static" // optional: static, hono, express
}
}debug-errors
Investigate errors in app logs.
{
"name": "debug-errors",
"arguments": {
"slug": "my-app"
}
}License
MIT
Available Tools
6 toolsapp_createA
Create a new app on Scout Live
Inputs: name, slug.
app_listA
List all apps for the authenticated user
Inputs: no named parameters.
deployC
Deploy a new version of an app
Inputs: slug (required), files (required).
logsB
Get recent logs for an app
Inputs: slug (required), lines.
port_getC
Get port adapter configuration
Inputs: port (required), slug (required).
port_setC
Set port adapter mapping
Inputs: port (required), slug (required), adapter (required), config.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 6 tools
Each tool targets a distinct action: listing apps, creating apps, deploying, fetching logs, and getting/setting port configuration. There is no overlap or ambiguity between these operations.
Naming is mixed: some tools follow noun_verb (app_list, app_create, port_get, port_set), while others are bare verbs or nouns (deploy, logs). This is readable but lacks a consistent pattern.
With 6 tools, the server is well-scoped for app and deployment management. Each tool covers a core function and the count is appropriate for the stated purpose.
The surface covers app creation, listing, deployment, log retrieval, and port config. Minor gaps include no explicit app deletion, app details retrieval, or deployment status checks, but core workflows are reasonably covered.
Related MCP Connectors
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Your org's AI agents, tasks, runs, search, and brain files as MCP tools and resources.
Discover and call AI agents via MCP. Supports A2A agents and platform agents with async tasks.
Hosted MCP runtime where your agent publishes its own tools by tool call and keeps working.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables file system operations, web scraping, and AI-powered search through MCP tools for use by LLM agents.1-
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to discover and execute tools via a secure MCP server with JWT authentication, RBAC, rate limiting, and audit logging.1MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to access a unified catalog of tools from various APIs (OpenAPI, GraphQL, MCP, Google Discovery) through the MCP protocol.12 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to read and modify Mendix application models through MCP tools for creating modules, entities, pages, microflows, deploying, and querying runtime data.1ISC