Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COTLET_API_KEYYesYour Cotlet.dev API key, obtained at https://cotlet.dev/app. Exported as COTLET_API_KEY and passed as a Bearer token / env variable to the local stdio server. Without it, tool calls respond: "Set COTLET_API_KEY. Get a key at https://cotlet.dev/app". Not needed when using the hosted connector with ChatGPT sign-in.

Instructions

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

Patreon through Cotlet.dev. Call patreon_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
patreon_guideA

How to work in Patreon (creator posts, members and tiers): its screens and the sign-in link. Call this first.

patreon_statusA

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

patreon_openB

Open a Patreon page in your signed-in Cloud Browser (default https://www.patreon.com) to work with creator posts, members and tiers.

patreon_readA

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

patreon_clickB

Click a numbered element on the current Patreon page.

patreon_typeC

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

patreon_closeA

Close the Patreon 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.6/5.0

Scored across 7 tools

Disambiguation5/5

Each tool maps to a distinct phase of the browser workflow: guide (instructions), status (account check), open/read/click/type (interaction primitives), and close (session cleanup). No two tools could reasonably be confused for one another.

Naming Consistency4/5

All tools share the patreon_ prefix with short, readable suffixes. The pattern mixes nouns (guide, status) with verbs (open, read, click, type, close), but this reflects a consistent auth/instruction vs. action split rather than random naming.

Tool Count5/5

Seven tools is tightly scoped for a browser-automation server: one orientation tool, one status check, four interaction primitives, and a cleanup tool. Every tool earns its place with no filler.

Completeness4/5

The core session lifecycle (open, read, click, type, close) is fully covered, enabling most post/member/tier tasks. Minor gaps exist—no explicit navigate/reload, scroll, or go-back primitive—but these are largely workable via open or read.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues