This MCP server lets you research, explore, and validate the weclapp REST API v2 — both offline via a bundled OpenAPI spec and live against a real tenant.

Knowledge & Exploration (no credentials required)

• search_knowledge — Search across entities, fields, endpoints, and relationships by keyword or concept.

• explain_entity — Get a full breakdown of an entity: fields, endpoints, references, projections, and read notes.

• explain_endpoint — Look up details about a specific OpenAPI endpoint by path and HTTP method.

• get_relationships — Discover cross-schema relationships for an entity, including optional inbound references.

• plan_cross_entity_read — Generate an efficient read plan for fetching data across multiple entities using properties and includeReferencedEntities.

• explain_filter_syntax — Learn weclapp v2 filter syntax, projection options, and includeReferencedEntities with examples.

• compare_approaches — Compare a naive N+1 approach vs. the recommended efficient read plan for a given goal.

Live Probes (GET-only, requires API credentials)

• execute_read_plan — Run a read plan against your live tenant to validate knowledge-layer recommendations.

• probe_entity_sample — Fetch a bounded sample of a single entity from production for structure inspection.

• probe_list_query — Run a bounded (capped page size) list query against production.

Analysis & Validation

• analyze_response_structure — Analyze a JSON response: discover field paths, arrays, nulls, referenced entities, and types.

• compare_to_schema — Diff a live API response against the OpenAPI schema fields for an entity.

• explain_data_location — Find where a specific field lives in a response (top-level, nested, or referenced).

• validate_read_plan — Verify that a read plan resolved the expected cross-schema data in a response.

• validate_filter — Check filter shapes and field/operator names against the schema before using them in code or probes.

• diagnose_api_error — Explain common weclapp API errors and suggest likely fixes.

• check_field_presence — Confirm whether a field path exists in the OpenAPI spec and optionally in a live response payload.

1. Click on "Install Server".

2. Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.

3. In the chat, type @ followed by the MCP server name and your instructions, e.g., "@weclapp-api-knowledge-mcp Explain the article entity and its relationships."

That's it! The server will respond to your query, and you can continue using it as needed.

Here is a step-by-step guide with screenshots.