Skip to main content
Glama
Bookipi MCP Server

Bookipi MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COTLET_API_KEYYesAPI key created in the Cotlet.dev console, used to authenticate with the Cotlet.dev MCP service.

Instructions

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

Bookipi through Cotlet.dev. Call bookipi_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
bookipi_guideA

How to work in Bookipi (manage invoices, customers and proposals): its screens and the sign-in link. Call this first.

bookipi_statusB

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

bookipi_openB

Open a Bookipi page in your signed-in Cloud Browser (default https://web.bookipi.com) to work with manage invoices, customers and proposals.

bookipi_readA

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

bookipi_clickB

Click a numbered element on the current Bookipi page.

bookipi_typeB

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

bookipi_closeA

Close the Bookipi 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 for instructions, status for readiness checks, open/close for session lifecycle, and read/click/type for page interaction. There is no meaningful overlap between tools, so an agent can select the right one from the name and description alone.

Naming Consistency5/5

All tools use the consistent `bookipi_` prefix followed by a short, lowercase verb or noun (`guide`, `status`, `open`, `read`, `click`, `type`, `close`). The pattern is predictable and easy to scan.

Tool Count5/5

Seven tools is a well-scoped set for a browser-automation workflow: one guide, one status check, session open/close, and the essential read/click/type interaction primitives. No tool appears redundant or missing for the stated purpose.

Completeness4/5

The core lifecycle and interaction loop is covered: open a session, read the page, click and type, then close to stop credits. Minor gaps exist for common browser automation needs such as waiting for page loads, scrolling, or taking screenshots, but the main invoice/customer/proposal workflows are supported.