Skip to main content
Glama
QuoteNest MCP Server

QuoteNest MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COTLET_API_KEYYesYour Cotlet.dev API key, created in the Cotlet.dev console. Used as a Bearer token in the Authorization header (e.g. "Authorization": "Bearer ${COTLET_API_KEY}") or exported as an environment variable for the local stdio bridge. Keep your key out of source control.

Instructions

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

QuoteNest through Cotlet.dev. Call quotenest_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
quotenest_guideA

How to work in QuoteNest (cleaning and pressure washing quotes, proposals, invoices and repeat bookings): its screens and the sign-in link. Call this first.

quotenest_statusA

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

quotenest_openA

Open a QuoteNest page in your signed-in Cloud Browser (default https://app.getquotenest.com) to work with cleaning and pressure washing quotes, proposals, invoices and repeat bookings.

quotenest_readA

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

quotenest_clickB

Click a numbered element on the current QuoteNest page.

quotenest_typeC

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

quotenest_closeA

Close the QuoteNest 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 clearly distinct step in a browser automation workflow: onboarding, readiness, opening, reading, clicking, typing, and closing. The only mild overlap is quotenest_guide versus quotenest_status, but one is documentation and the other is an account/credit check, so agents can tell them apart.

Naming Consistency4/5

All tools use a consistent quotenest_ prefix and snake_case naming. Most are action verbs, though quotenest_guide and quotenest_status are noun-like, which is a minor deviation but still highly readable and predictable.

Tool Count5/5

Seven tools is well-scoped for a browser-based QuoteNest assistant. Each tool covers a distinct lifecycle step, and none feels redundant or missing at this granularity.

Completeness4/5

The set covers the full browser session lifecycle: guide, status, open, read, click, type, and close. Minor gaps remain, such as explicit arbitrary navigation, waiting, or scrolling, but agents can work around these through links and page reads.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues