Skip to main content
Glama
scoutos-labs

Scout MCP Server

Official
by scoutos-labs

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoHTTP server port (default: 3000)
MCP_TRANSPORTNoTransport mode: stdio or http (default: stdio)
SCOUT_API_KEYYesScout Live API key
SCOUT_API_URLNoAPI endpoint (default: https://scoutos.live)

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}
prompts
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
app_listA

List all apps for the authenticated user

app_createA

Create a new app on Scout Live

deployC

Deploy a new version of an app

logsB

Get recent logs for an app

port_getC

Get port adapter configuration

port_setC

Set port adapter mapping

Prompts

Interactive templates invoked by user choice

NameDescription
deploy-new-appCreate and deploy a new app on Scout Live
debug-errorsInvestigate errors in app logs

Resources

Contextual data attached and managed by the client

NameDescription
Apps ListList of all apps for the authenticated user
Available AdaptersList of available port adapters

TDQS

A3.5/5.0

Scored across 6 tools

Disambiguation5/5

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 Consistency3/5

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.

Tool Count5/5

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.

Completeness4/5

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.

Maintenance

ActivityInactive
ResponsivenessSyncing