Gapwise AI

Permissioned intelligence on top of deterministic Gapwise truth.

The provider-neutral Model Context Protocol (MCP) integration layer for public UTM campus intelligence and explicitly delegated Gapwise student context.

_{Next.js · TypeScript · MCP · OAuth · Supabase · Node · Vercel}

Gapwise · AI · Docs · Support · Status · MCP · Security

---

What Gapwise AI is

Gapwise AI is the provider-neutral AI integration layer of Gapwise, a campus-intelligence ecosystem created and engineered by Andrew Muratov.

The main gapwise platform owns canonical student state and deterministic campus calculations. Gapwise AI exposes a narrow remote MCP interface to that truth rather than becoming a second timetable, routing, or planning engine.

Gapwise owns the facts. Connected AI clients reason over deterministic public campus data and explicitly delegated private context.

There is no server-side LLM provider required by this repository. Compatible MCP clients supply the model/reasoning layer. Gapwise AI supplies schemas, deterministic context, authorization for private tools, and bounded mutation semantics.

---

Live MCP surface

Canonical endpoint:

https://ai.gapwise.ca/api/mcp

The release surface contains 17 tools.

Public, stateless UTM campus intelligence

These four tools require no private Gapwise account context:

• list_utm_buildings
• get_utm_building
• route_between_utm_buildings
• plan_utm_gap_window

They operate on deterministic public Gapwise campus data and never read a student's timetable, friends, precise location, or private sync state.

Permissioned private reads and planning

Nine tools operate only on the connected user's explicitly delegated context:

• get_ai_delegation_status
• get_my_day
• get_my_week
• get_my_gap_plan
• get_my_ai_preferences
• get_my_decision_context
• find_my_available_windows
• find_my_weekly_opportunities
• check_my_plan_feasibility

Permissioned private writes

Four tools can queue bounded user-authorized changes:

• create_personal_item
• update_personal_item
• delete_personal_item
• update_gap_preferences

Academic meetings remain source-backed and cannot be created, edited, or deleted by an AI client. Personal-item/preference writes are typed, permission-checked, revision-bound, idempotency-bounded, and queued for Gapwise rather than granting an assistant arbitrary access to canonical encrypted state.

For the exact behavioral contract, see docs/TOOL_CONTRACT.md.

---

Architecture and trust boundary

                         public campus request
MCP client ------------------------------------------+
                                                     |
                                                     v
                                               Gapwise AI
                                                     |
                                                     v
                                      deterministic Gapwise campus API

Gapwise browser / platform
  canonical timetable + deterministic campus state
                    |
                    | explicit minimized delegation
                    v
               Gapwise AI
            OAuth + MCP boundary
                    |
       encrypted snapshot / queued action
                    v
             Supabase Postgres
                    ^
                    |
          user-scoped OAuth token
                    |
               MCP client

Private delegated data excludes raw ACORN .ics, friend data, precise/live location, account credentials, primary private-data encryption keys, and unrelated browser state. Delegated snapshots and queued actions use a separate encryption domain at rest. This is not represented as zero-knowledge encryption: authorized plaintext exists transiently during an authorized tool request.

OAuth protected-resource metadata is published at the same first-party origin. Public tools intentionally carry no private OAuth requirement; private tools require the canonical resource-bound Gapwise OAuth flow and the relevant explicit delegation permission.

---

Release and directory posture

The server is intentionally provider-neutral. ChatGPT, Claude, and other compatible clients consume the same tools, schemas, and Gapwise authorization semantics.

Named-client support is evidence-gated. Gapwise does not describe ChatGPT or Claude as production-supported until the exact current client surface has passed the real OAuth/read/write/revoke and negative-path matrix in docs/CLIENT_VALIDATION.md.

The directory-review package is maintained in:

• docs/DIRECTORY_METADATA.md
• docs/REVIEWER_GUIDE.md
• docs/TEST_ACCOUNT_SPEC.md
• docs/SUBMISSION_CHECKLIST.md
• docs/RELEASE_RUNBOOK.md

---

Cost model

Gapwise AI does not require an OpenAI or Anthropic API key for normal connector operation. The connected client supplies model inference. The backend is deliberately designed around deterministic first-party logic, bounded requests/results, and hard-cost-conscious infrastructure. See docs/COST_MODEL.md.

---

Public developer platform

Applications that need conventional non-MCP UTM campus intelligence can use the canonical public API or first-party SDKs:

npm install @gapwise/sdk@0.1.1
# JSR: @gapwise/sdk@0.1.1
python -m pip install gapwise==0.1.0

• API: https://api.gapwise.ca/v1
• OpenAPI: https://api.gapwise.ca/openapi.json
• Docs: https://docs.gapwise.ca

The JavaScript/TypeScript SDK is published on npm and JSR; the Python SDK is published on PyPI. The public API/SDK surface does not grant access to delegated private AI context.

---

Gapwise ecosystem

Repository	Role	Primary surface
gapwise	Core web/PWA, canonical student state, deterministic campus engine, public API, and SDK source	gapwise.ca
gapwise-mobile	Native iOS and Android client	Native mobile app
gapwise-ai	Remote MCP layer for public campus intelligence and explicitly delegated student context	ai.gapwise.ca
gapwise-data	Open campus-data, provenance, schema, validation, and reuse portal	data.gapwise.ca
gapwise-docs	Canonical public developer documentation	docs.gapwise.ca
gapwise-status	Independent service-health monitoring and incident communication	status.gapwise.ca

All six repositories are owned by the Gapwise for UTM GitHub organization (Gapwise-for-UTM). Andrew Muratov remains the creator and primary maintainer.

---

Local development

Requirements: Node.js 24.x, npm, and a compatible Supabase project for authenticated/delegation flows.

git clone https://github.com/Gapwise-for-UTM/gapwise-ai.git
cd gapwise-ai
npm ci
cp .env.example .env.local
npm run check
npm run dev

Security-sensitive changes should preserve the documented authorization, encryption, grounding, schema, and mutation boundaries. See docs/THREAT_MODEL.md, docs/PRIVACY.md, and SECURITY.md.

---

Project relationship

Gapwise is an independent project created by Andrew Muratov. It is not an official University of Toronto service and is not affiliated with or endorsed by the University of Toronto.

License

MIT © 2026 Andrew Muratov.