Skip to main content
Glama
Pixifi MCP Server

Pixifi MCP Server

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
COTLET_API_KEYYesYour Cotlet.dev API key. Get it at https://cotlet.dev/app and export it as COTLET_API_KEY.

Instructions

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

Pixifi through Cotlet.dev. Call pixifi_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
pixifi_guideA

How to work in Pixifi (photography studio clients, leads, proposals, contracts, events and invoices): its screens and the sign-in link. Call this first.

pixifi_statusA

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

pixifi_openA

Open a Pixifi page in your signed-in Cloud Browser (default https://www.pixifi.com/admin/) to work with photography studio clients, leads, proposals, contracts, events and invoices.

pixifi_readA

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

pixifi_clickC

Click a numbered element on the current Pixifi page.

pixifi_typeC

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

pixifi_closeA

Close the Pixifi 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 in the browser workflow: guidance, readiness check, session opening, page reading, clicking, typing, and closing. There is little risk of confusing one tool for another, especially because read/click/type operate on numbered page elements.

Naming Consistency5/5

All tools use a consistent pixifi_ prefix followed by a short snake_case action or state label. Although guide and status are noun-like rather than pure verbs, the overall naming convention is predictable and easy to scan.

Tool Count5/5

Seven tools is well-scoped for a browser-automation surface: guide and status support setup, open/read/click/type cover the core interaction loop, and close handles cleanup. No tool appears redundant.

Completeness4/5

The set covers the essential browser lifecycle and interaction primitives needed to work inside Pixifi. Minor gaps exist, such as explicit navigation, scrolling, select/dropdown handling, or upload/download support, but most workflows can be worked around via read/click/type.