Skip to main content
Glama
SimplyWise Cost Estimator MCP Server

SimplyWise Cost Estimator MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COTLET_API_KEYYesCotlet.dev API key used as a bearer token to authenticate with the hosted Cotlet MCP server (https://cotlet.dev/mcp/v1). Create a key in the Cotlet console and keep it in your local environment, 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.

SimplyWise Cost Estimator through Cotlet.dev. Call simplywise_cost_estimator_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
simplywise_cost_estimator_guideA

How to work in SimplyWise Cost Estimator (estimates, line items, discounts, fees and tax): its screens and the sign-in link. Call this first.

simplywise_cost_estimator_statusB

Check that your Cotlet.dev account and SimplyWise Cost Estimator are ready: account, credits and SimplyWise Cost Estimator connection.

simplywise_cost_estimator_openA

Open a SimplyWise Cost Estimator page in your signed-in Cloud Browser (default https://www.simplywise.com/login) to work with estimates, line items, discounts, fees and tax.

simplywise_cost_estimator_readA

Read the current SimplyWise Cost Estimator page: its text and numbered buttons, links and fields.

simplywise_cost_estimator_clickB

Click a numbered element on the current SimplyWise Cost Estimator page.

simplywise_cost_estimator_typeC

Type text into a numbered field on the current SimplyWise Cost Estimator page.

simplywise_cost_estimator_closeA

Close the SimplyWise Cost Estimator 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 targets a distinct phase of a browser workflow: guide (instructions), status (readiness), open (launch), read (perceive page), click/type (interact), close (teardown). The descriptions make the boundaries explicit, e.g. guide says "call this first" while read says "read the current page," so an agent can select correctly.

Naming Consistency5/5

All seven tools use the same snake_case pattern of simplywise_cost_estimator_ plus a single verb (guide, status, open, read, click, type, close). The shared prefix is verbose but perfectly predictable.

Tool Count5/5

Seven tools is a tight, well-scoped set for a browser-automation wrapper: instructions, health check, open/read/act/close. Every tool earns its place with no padding or redundancy.

Completeness4/5

The set covers the core perceive-act loop (open, read, click, type, close) plus onboarding, so basic estimate/line-item/discount/fee/tax work is achievable. Minor gaps remain: no explicit navigation to a specific URL, no select/dropdown handling, no wait or scroll, which could force workarounds on richer form flows.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues