APIForge MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFORGE_HOST | No | Host for SSE transport | |
| APIFORGE_PORT | No | Port for SSE transport | |
| APIFORGE_TRANSPORT | No | Transport type (stdio or sse) | |
| YANDEX_METRIKA_ROLE | No | Role for Yandex Metrika service | |
| APIFORGE_CONFIGS_DIR | No | Path to API configs directory | |
| APIFORGE_DEFAULT_ROLE | No | Default access role (readonly, readwrite, admin) | |
| YANDEX_METRIKA_API_KEY | No | API key for Yandex Metrika | |
| YANDEX_METRIKA_AUTH_PROVIDER | No | Authentication provider for Yandex Metrika (api_key or oauth) |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| yandex_metrika_counters_listA | List all Yandex Metrika counters |
| yandex_metrika_counter_statC | Get statistics for a counter |
| yandex_metrika_goalsC | List goals for a counter |
| yandex_webmaster_hostsA | List all verified hosts |
| yandex_webmaster_search_queriesC | Get search queries for a host |
| get_audit_logC | Get the access audit log showing recent API calls and denials. |
| list_servicesA | List all configured API services and their available resources. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| analytics_query | Prompt for querying analytics data. |
| troubleshooting | Prompt for troubleshooting. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| docs_guide | Complete guide for using MaisCP. |
| docs_access | Access control documentation. |
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: audit log, service listing, Yandex Metrika operations (list counters, get stats, list goals), and Yandex Webmaster operations (list hosts, get search queries). No overlapping functionality.
Naming conventions are inconsistent. Generic tools use verb_noun (get_audit_log, list_services) but Yandex tools use a reversed pattern (yandex_metrika_counters_list, yandex_metrika_counter_stat) with mixed singular/plural forms. Two distinct styles coexist.
With 7 tools, the count is appropriate for a focused server that combines generic API management with specific Yandex services. It's slightly limited but not excessive.
The tool surface is incomplete for the stated domain. Generic tools only provide audit and listing, missing CRUD operations. Yandex Metrika and Webmaster tools offer read-only operations (list, get stats, list goals) but lack create, update, delete, and other management actions.