Altegio Marketplace MCP
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the HTTP server. | 8094 |
| ALLOW_BACKOFFICE | No | Enable internal backoffice tools. Default false. | false |
| ALTEGIO_API_BASE | No | Altegio API base URL. | https://api.alteg.io/api/v1 |
| ALTEGIO_APP_BASE | No | Altegio app base URL. | https://app.alteg.io |
| ALTEGIO_USER_TOKEN | No | Optional for local stdio; only for a private local stdio process. | |
| ALTEGIO_PARTNER_TOKEN | Yes | Bootstrap partner token. | |
| ALTEGIO_ADMIN_USER_TOKEN | No | Admin user token required when ALLOW_BACKOFFICE=true. | |
| MARKETPLACE_MCP_STATE_DIR | No | Directory for marketplace MCP state. | .marketplace-mcp |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| marketplace_activate_installationC | Plan or perform step 2: activate a pending installation and configure entity webhooks/chat/tips/channels. Active state is treated idempotently. |
| marketplace_backoffice_delete_applicationB | Delete an application and partner-linked entities through the internal backoffice API. Disabled by default and highly destructive. |
| marketplace_backoffice_delete_offerC | Delete an internal Marketplace special offer. Internal API; disabled by default. |
| marketplace_backoffice_get_applicationB | Read internal Marketplace backoffice data. This is not a public API and is disabled by default. |
| marketplace_backoffice_list_offersA | List internal Marketplace special offers. Internal API; disabled by default. |
| marketplace_backoffice_set_commercialsC | Plan or set internal commission/boost values. Internal API; disabled by default. |
| marketplace_backoffice_set_publicationB | Plan or set/clear the internal moderated_at publication timestamp. Internal API; disabled by default. |
| marketplace_backoffice_upsert_offerB | Plan or create/update an internal Marketplace special offer. Internal API; disabled by default. |
| marketplace_create_applicationC | Plan or create a draft Marketplace application. Creation is naturally idempotent by slug within the developer account. |
| marketplace_create_developer_accountB | Plan or create a developer account. Any partner token returned upstream is redacted from the tool response. |
| marketplace_delete_developer_accountC | Delete a developer account. This is destructive and may orphan its management workflow. |
| marketplace_get_applicationB | Get one owned application by filtering the authoritative developer-account application list. |
| marketplace_get_catalog_metadataA | Get current Marketplace categories, channels, functionalities, and the general country dictionary used by application/account country IDs. |
| marketplace_get_conversion_statisticsC | Get application and category-average Marketplace funnel conversion series. |
| marketplace_get_installation_statusB | Get status, payments, and status-transition log for an owned application at one location. |
| marketplace_get_payment_linkB | Generate an Altegio-hosted Marketplace payment link for an installed location. |
| marketplace_get_statisticsB | Get owned-application views, pending grants, activations, new payments, and uninstalls for a date range. |
| marketplace_grant_location_accessA | Plan or perform step 1 of installation: location owner grants access, producing pending (or immediate active for eligible draft/private apps). Apply requires exact confirmation. |
| marketplace_install_sidebar_frameC | Install or remove an internal chat/waiting_list/task_tracker sidebar frame. These types are distinct from developer employee/client/visit frames. |
| marketplace_list_applicationsA | List applications in a developer account, including card configuration, permissions, system-user ID, short links, and moderation state. Secret fields are redacted. |
| marketplace_list_available_rightsB | Return the current hierarchical permission dictionary available to Marketplace system users. |
| marketplace_list_developer_accountsA | List developer accounts owned by the current Altegio user. Secret fields in partner-system metadata are redacted. |
| marketplace_list_entity_framesB | List declared employee/client/visit iframe definitions. Declarations are copied to a location only during a later application installation. |
| marketplace_list_installationsC | List locations connected to an owned application, with bounded pagination. |
| marketplace_list_reviewsB | List public reviews for a Marketplace application. |
| marketplace_list_tariffsB | List Marketplace billing tariffs and options for an owned application. |
| marketplace_notify_chat_messageC | Signal a new chat message so Biz.ERP highlights the chat frame and may create notifications/leads according to location settings. |
| marketplace_record_paymentB | Plan or record a successful external payment. This can unfreeze an installation. Requires a durable idempotency key and exact confirmation. |
| marketplace_refund_paymentB | Plan or report a Marketplace payment refund. Requires an exact confirmation phrase. |
| marketplace_replace_entity_framesA | Plan or replace the full employee/client/visit declaration set. Omitted slugs are deleted. Existing installations are not updated or backfilled. |
| marketplace_save_moderation_instructionsC | Plan or save connection and payment instructions before submitting an application for moderation. |
| marketplace_set_discountC | Plan or set the Marketplace payment discount for selected locations. |
| marketplace_set_sms_sender_namesC | Plan or publish 1-20 SMS sender names for a compatible installed application. |
| marketplace_submit_for_moderationC | Plan or submit a fully configured application for Marketplace moderation. |
| marketplace_toggle_sidebar_highlightB | Enable or clear the highlight on an already installed sidebar frame, optionally for one user. |
| marketplace_uninstallB | Plan or uninstall an application from a location. Requires an exact confirmation phrase. |
| marketplace_update_applicationB | Plan or replace the complete Marketplace card and technical settings. Apply requires exact confirmation because omitted collections are cleared. |
| marketplace_update_developer_accountB | Plan or replace developer-account details. Send the complete current account payload. |
| marketplace_update_notification_channelC | Plan or update SMS/WhatsApp channel availability for a compatible installed application. |
| marketplace_validate_lifecycle_callbackB | Validate and normalize an uninstall/freeze/payment callback payload against the owned developer-account token without revealing it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| marketplace_safe_draft_rollout | Drive a safe draft application rollout with plan/apply checkpoints and final cleanup. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| marketplace_internals | Source-referenced Biz.ERP architecture, state machine, payloads, frames, callbacks, billing, caches, gates, and limitations. |
| marketplace_safe_e2e | A plan-first end-to-end recipe for creating, configuring, installing, activating, checking, updating, and uninstalling a draft. |
| marketplace_tool_boundaries | Public, Developer Cabinet, restricted, and internal backoffice surface classification. |
TDQS
Scored across 40 tools
Tools are mostly distinct by resource and action, with clear prefixes separating internal backoffice APIs from public ones. A few pairs like get_statistics vs get_conversion_statistics and grant_location_access vs activate_installation could be confused without reading descriptions, but overall boundaries are clear given the detailed descriptions.
All tools use snake_case with a consistent verb_noun pattern and predictable marketplace_ or marketplace_backoffice_ prefixes. There are no deviations in style or convention.
40 tools is well above the suggested 3-15 range and feels heavy for the scope, even though the marketplace domain is complex. The fine-grained lifecycle operations increase cognitive load and may lead to selection errors.
The surface covers developer accounts, applications, installations, payments, moderation, frames, notifications, and statistics comprehensively. Minor gaps exist, such as no public delete_application (only backoffice) and no standalone payment listing, but core workflows are supported.