Platform documentation
Build with facoolta
Operational reference for the facoolta tRPC API, LMS connectors, ginny MCP server, and provider webhooks.
Choose a path
Call the platform API
Check service health, configure a typed client, and attach a bearer access token.
Open quickstart →Connect an LMS
Plan an administrator-reviewed Moodle or Blackboard connector using supported APIs.
Review LMS setup →Connect an MCP client
Use Streamable HTTP, OAuth, runtime tool discovery, and approval-gated writes.
Configure ginny MCP →Review provider callbacks
Understand the current LiveKit and Stream acknowledgement endpoints and their limits.
Read webhook status →Service endpoints
- tRPC API
https://api.facoolta.com/trpc- HTTP health check
https://api.facoolta.com/health- ginny MCP
https://mcp.facoolta.com/mcp
Treat these origins as separate security boundaries. API bearer tokens belong in the
Authorization header; MCP credentials follow the MCP OAuth flow and must not be
embedded in JSON-RPC parameters.
Status language
- Live
- The checked-in server has an implementation for the operation.
- Stub
- The path is stable, but the handler returns
NOT_IMPLEMENTED.
- Campus-managed
- An institution administrator must provision or approve the integration.
Support
Send integration questions to support@facoolta.com. Include the service, procedure or connector, UTC timestamp, and request ID if one was returned. Never include access tokens, LMS secrets, or student records.