topmate-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HEADLESS | No | Set to false on initial run or session expiration to input OTP in browser. Switch to true once storage-state.json is generated. | true |
| TOPMATE_EMAIL | Yes | Topmate account login email (used for OTP sign-in) | |
| TOPMATE_BASE_URL | No | Base URL for Topmate (default: https://topmate.io) | https://topmate.io |
| TOPMATE_USERNAME | Yes | Topmate creator username (topmate.io/your_username) | |
| TOPMATE_API_BASE_URL | No | API base URL (default: https://api.galactus.run) | https://api.galactus.run |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_profileA | Fetch the current Topmate profile: name, title, bio, and the full list of existing services. Call this before drafting a new service so tone and style match what's already on the profile. |
| list_servicesA | List all services currently live on the Topmate profile, with their IDs, titles, descriptions, pricing, and intake questions. |
| get_serviceA | Fetch full details for one Topmate service by its ID. |
| create_serviceA | Create a new service on the Topmate profile. Pass fully-drafted, final content — write a polished title and description and good intake questions yourself first (using get_profile/list_services as style reference), then call this with the finished result. |
| update_serviceA | Update an existing Topmate service. Only pass the fields that should change — omitted fields are left as-is. Pass final, polished content, not rough notes. |
| update_profileA | Update the creator's Topmate profile title (tagline) and/or bio. Only pass the fields that should change — omitted fields are left as-is. Pass final, polished content, not rough notes. |
| delete_serviceA | Delete a service from the Topmate profile. Destructive and irreversible — set confirm=true only after you've told the user exactly which service (by title) you're about to delete and they've agreed. |
| update_questionsA | Replace the intake questions asked to buyers of a specific Topmate service. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Most tools are clearly separated by resource and action: profile vs. service, read vs. write. The one point of ambiguity is update_questions, which overlaps with update_service since service updates may also include intake questions.
All tool names follow a consistent verb_noun snake_case pattern: get_, list_, create_, update_, delete_. The naming clearly distinguishes collection reads (list_services) from single-item reads (get_service).
Eight tools is well-scoped for managing a Topmate profile and its services. Each tool covers a distinct core operation, and none feels redundant or unnecessary.
The set provides full coverage for profile viewing/updating and service lifecycle management: create, read, list, update, delete, plus question-specific updates. There are no obvious dead ends or missing operations for the stated domain.