Overview
External-facing modules that expose your QUESTPIE app to tools and API consumers through MCP and OpenAPI.
Integrations are modules you add to surface what your app already knows to external consumers. Register one, run codegen, and the integration introspects your existing collections, globals, and routes, no decorators, no hand-written spec, no separate build step. These pages cover external protocols and API documentation surfaces. For framework modules such as admin and workflows, use Admin and Extend.
Available integrations
| Integration | What it does |
|---|---|
| MCP | Add mcpModule and your app becomes a Model Context Protocol server, collections, globals, and opted-in routes become tools an AI client can call, gated by your access rules. |
| OpenAPI and Scalar | Add @questpie/openapi and your whole API documents itself, an OpenAPI 3.1 spec at /api/openapi.json plus interactive Scalar docs at /api/docs. |
Related
- Routes, how routes opt into MCP tool exposure and shape their OpenAPI metadata.
- Collections · Globals, the surfaces both integrations introspect.
- Access control, the rules that gate every exposed operation.
Multi-tenancy
Serve many tenants, organizations, properties, cities, from one app by deriving the active scope from the request, isolating data with access rules and scoped globals, and letting admins switch tenants from the sidebar.
MCP
Add the mcpModule and your QUESTPIE app exposes a Model Context Protocol server, collections, globals, and annotated routes become tools an AI client can call, gated by your existing access rules.