Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COTLET_API_KEYYesYour Cotlet.dev API key, used to authenticate with the hosted Sleeper MCP server. Get a key at https://cotlet.dev/app.

Instructions

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

Sleeper through Cotlet.dev. Call sleeper_guide first. Set COTLET_API_KEY (https://cotlet.dev/app).

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
sleeper_guideA

How to work in Sleeper (leagues, lineups, waivers and trades): its screens and the sign-in link. Call this first.

sleeper_statusB

Check that your Cotlet.dev account and Sleeper are ready: account, credits and Sleeper connection.

sleeper_openA

Open a Sleeper page in your signed-in Cloud Browser (default https://sleeper.app) to work with leagues, lineups, waivers and trades.

sleeper_readA

Read the current Sleeper page: its text and numbered buttons, links and fields.

sleeper_clickB

Click a numbered element on the current Sleeper page.

sleeper_typeC

Type text into a numbered field on the current Sleeper page.

sleeper_closeA

Close the Sleeper browser session when the work is done, so credits stop running.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.7/5.0

Scored across 7 tools

Disambiguation5/5

Each tool maps to a distinct action: open/close session, read page, click element, type text, check status, read guide. The browser-automation verbs are unambiguous and there is essentially no overlap between click, type, and read.

Naming Consistency5/5

All seven tools share the sleeper_ prefix followed by a single clear verb (open, close, read, click, type, status, guide). The pattern is uniform and highly predictable.

Tool Count5/5

Seven tools is well-scoped for a browser automation server, with each tool earning its place across the session lifecycle. Nothing feels padded or bloated.

Completeness4/5

The set covers a coherent session lifecycle: guide, status, open, read, click, type, close. Minor gaps exist for common browser interactions like scrolling, navigation/back, or waiting on dynamic content, but core workflows are fully supported.