Skip to main content
Glama
Procured MCP Server

Procured MCP Server

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.

Instructions

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

Procured through Cotlet.dev. Call procured_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
procured_guideA

How to work in Procured (manage quotes, invoices, crew visits, job photos, inventory and business reports): its screens and the sign-in link. Call this first.

procured_statusB

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

procured_openB

Open a Procured page in your signed-in Cloud Browser (default https://app.procured.us/login) to work with manage quotes, invoices, crew visits, job photos, inventory and business reports.

procured_readA

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

procured_clickB

Click a numbered element on the current Procured page.

procured_typeB

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

procured_closeA

Close the Procured 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 has a clearly distinct role: guide, readiness check, open session, read page, click, type, and close. The browser interaction tools are separated by action, and the setup tools target different concerns.

Naming Consistency4/5

All tools use a consistent procured_ prefix and snake_case single-word names. The only minor inconsistency is that guide and status are noun-like while the others are verbs, but the pattern remains predictable.

Tool Count5/5

Seven tools is well scoped for a browser-session wrapper around a web app. Each tool covers a necessary part of the lifecycle: setup, opening, reading, interacting, and closing.

Completeness4/5

The surface covers the core browser automation lifecycle and readiness checks. Minor gaps exist around advanced page interaction such as scrolling, waits, or selecting dropdown options, but agents can likely work around them via read/click/type.