weclapp-api-knowledge-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_HOST | No | SSE bind host | 0.0.0.0 |
| MCP_PORT | No | SSE bind port | 8080 |
| MCP_TRANSPORT | No | stdio or sse | stdio |
| WECLAPP_API_KEY | No | Read-only API token | |
| WECLAPP_BASE_URL | No | Tenant API base, e.g. https://your-tenant.weclapp.com/webapp/api/v2 | |
| WECLAPP_AUTH_HEADER | No | Auth header name | AuthenticationToken |
| WECLAPP_OPENAPI_PATH | No | Path to OpenAPI spec | data/openapi_v2.json |
| WECLAPP_MAX_PAGE_SIZE | No | Max rows for list probes | 10 |
| WECLAPP_REQUEST_TIMEOUT_SECONDS | No | HTTP timeout for live probes | 30 |
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 |
|---|---|
| search_knowledgeC | Search weclapp API knowledge across entities, fields, endpoints, and relationships. |
| explain_entityA | Explain one weclapp entity: fields, endpoints, references, projections, and read notes. |
| explain_endpointB | Explain one OpenAPI endpoint by path and method. |
| get_relationshipsC | Return cross-schema relationships discovered from x-weclapp.entity references. |
| plan_cross_entity_readC | Plan an efficient read using properties and includeReferencedEntities where possible. |
| explain_filter_syntaxC | Explain weclapp v2 filters, projection, includeReferencedEntities, and examples. |
| compare_approachesC | Compare naive N+1 API research with the recommended efficient read plan. |
| execute_read_planC | Execute a GET-only read plan against production to validate a knowledge-layer recommendation. |
| probe_entity_sampleC | Fetch one bounded sample from production for structure research and validation. |
| probe_list_queryB | Probe a bounded list query against production. GET-only, capped page size. |
| analyze_response_structureC | Analyze live or sample JSON: paths, arrays, nulls, referencedEntities, and types. |
| compare_to_schemaC | Compare a live payload with the OpenAPI schema fields for an entity. |
| explain_data_locationC | Find where a field appears in a response and whether it is nested or referenced. |
| validate_read_planC | Validate that a read plan produced the expected cross-schema resolution. |
| validate_filterC | Validate filter shape and field/operator names before probing or coding. |
| diagnose_api_errorC | Explain common weclapp API errors and likely fixes. |
| check_field_presenceC | Check whether a field path exists in OpenAPI and optionally in a live payload. |
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 17 tools
Each tool has a clearly distinct purpose, covering analysis, validation, querying, and explanation. There is minimal overlap, e.g., execute_read_plan vs validate_read_plan are differentiated by execution vs validation.
All tool names follow a verb_noun pattern in snake_case (e.g., analyze_response_structure, validate_filter). The naming is consistent and predictable across the entire set.
With 17 tools, the server covers a comprehensive range of API knowledge tasks without being excessive. Each tool serves a specific need in exploring and validating the weclapp API.
The tool surface covers major operations: analysis, schema validation, query planning, relationship discovery, and error diagnosis. It lacks some bulk or batch operations, but core workflows are well-supported.