Mailganer API MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| POSTMAN_API_KEY | No | API key for Postman (optional, for Postman integration) | |
| MAILGANER_API_KEY | No | API key for Mailganer live API calls (optional, for future use) | |
| MAILGANER_API_BASE_URL | No | Base URL for Mailganer API (default: https://mailganer.com/api) | https://mailganer.com/api |
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 | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_doc_statusA | Get sync status of cached Mailganer API docs and Postman collection |
| get_cache_healthA | Check whether docs/ cache is ready to use (empty after pip install without clone/sync) |
| sync_documentationB | Re-sync Mailganer API documentation from web sources into docs/ |
| list_api_docsB | List cached Mailganer API documentation pages, optionally by category |
| search_api_docsC | Full-text search in cached Mailganer API documentation |
| get_api_endpoint_docB | Get cached Mailganer API doc page with linked Postman requests |
| get_linked_postman_requestB | Get Postman request with related Mailganer documentation pages |
| check_doc_pageA | Compare a cached doc page with the live site and report differences |
| get_api_overviewA | Get Mailganer API overview: auth, limits, pagination |
| search_postmanC | Search Mailganer Postman collection requests by keyword |
| get_postman_requestA | Get a Postman request by partial name or exact API path (without related docs) |
| rebuild_doc_crosslinksB | Rebuild docs ↔ Postman crosslink index in docs/crosslinks.json |
| list_crosslink_gapsB | List docs and Postman requests without crosslinks, with documented reasons |
| get_api_credentials_statusA | Check whether MAILGANER_API_KEY is configured (without exposing the full key) |
| prepare_api_callC | Build method, path, auth mode and example body from cached docs by slug |
| call_mailganer_apiB | Execute a live HTTP request against Mailganer REST API |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| explore-endpoint | Найти документацию и Postman-запросы для метода API |
| call-endpoint | Подготовить и выполнить live-запрос по slug документации |
| sync-docs-review | Обновить кэш docs и показать статус / изменения |
| find-crosslink-gaps | Показать несвязанные страницы и Postman-запросы |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| api-overview | Авторизация, лимиты, пагинация |
| doc-cache-status | Дата sync, количество страниц, Postman, crosslinks |
| doc-cache-health | ready/warnings — достаточно ли docs/ для работы MCP |
| api-docs-index | Список всех endpoint-страниц из api-index.json |
TDQS
Scored across 16 tools
Most tools target distinct operations (sync, list, search, get, compare, rebuild), but get_doc_status and get_cache_health both report cache state, and search_postman/get_postman_request can overlap when locating a request. Descriptions generally clarify the boundary.
All tool names follow a clear snake_case verb_noun pattern (sync_, get_, list_, search_, rebuild_, call_). The verbs are consistently imperative and objects are specific, so the naming scheme is predictable across the set.
16 tools is slightly above the ideal 3-15 range, but each tool addresses a distinct documentation/Postman/API-call workflow. The count is acceptable for a server that manages cached docs, crosslinks, and live requests.
The set covers sync, cache status, searching/reading docs, Postman lookup, crosslink maintenance, credential checks, request preparation, and live API execution. Minor gaps exist, such as no explicit list-all-Postman-requests tool and no way to validate the API key beyond checking it is configured.