Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COTLET_API_KEYNoAPI key created in the Cotlet.dev console, used for Codex, Claude Code, and the optional local MCP wrapper.

Instructions

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

ThriveCart through Cotlet.dev. Call thrivecart_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
thrivecart_guideA

How to work in ThriveCart (work with transactions, products, checkouts, subscriptions, affiliates and reports): its screens and the sign-in link. Call this first.

thrivecart_statusB

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

thrivecart_openB

Open a ThriveCart page in your signed-in Cloud Browser (default https://thrivecart.com) to work with work with transactions, products, checkouts, subscriptions, affiliates and reports.

thrivecart_readA

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

thrivecart_clickB

Click a numbered element on the current ThriveCart page.

thrivecart_typeB

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

thrivecart_closeA

Close the ThriveCart 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

Disambiguation4/5

Most tools are clearly distinct: open/read/click/type/close map to distinct browser actions. thrivecart_guide and thrivecart_status are somewhat close as onboarding/readiness helpers, but the descriptions make their roles separable.

Naming Consistency5/5

All tool names use a consistent thrivecart_ prefix followed by a short snake_case action verb. The pattern is predictable across the entire set.

Tool Count5/5

Seven tools is well-scoped for a browser-automation server: setup, page reading, interaction, and cleanup are each represented without excess. Each tool appears to earn its place.

Completeness4/5

The surface covers the core browser lifecycle: guide, status check, open session, read page, click, type, and close. Minor gaps like explicit scrolling or waiting could be worked around via clicking/reading, but are not directly exposed.