Every catalog and pathway.Open to your approved AI.And to no one else.
Kenii MCP will open your college’s Kenii system to the AI clients and developers you authorize over the Model Context Protocol. It will be built natively into the plugin, connecting your catalog, pathways, curriculum, and board records.
An unlimited protocol layer on the server.
Complete control over every connection.
Named connections.
Zero anonymous access.
Every client will connect using an issued, named key or a user-mapped Application Password. Your IT team will know exactly which assistant, script, or developer is connected, with the ability to revoke any single key instantly.
Staff directory
126 people · 18 departments
Read-only keys for AI.
Full write keys for staff.
Student-facing AI tools get read-only keys scoped strictly to published catalog and pathway data, with zero reach into private records or draft edits. Staff and developers connect with Application Passwords carrying their own role-gated authority.
Programs
48 programs in the catalog · 2026 to 2027
One tool registry.
Zero drift.
Every tool is registered from a single source of truth defining its schema, capabilities, and safety annotations. What the protocol exposes will follow your active catalog and module licensing, rather than a separate list maintained by hand.
Proposals
5 curriculum change proposals · 2026 to 2027
Modern HTTP transport.
Built for developers.
The planned transport is JSON-RPC 2.0 over Streamable HTTP, served through the WordPress REST API you already run. Your own engineers will build against the exact same open protocol our first-party tooling uses, with no proprietary client.
Find a program
12 of 48 programs match
Decisions locked. Nothing shipped yet.
Kenii MCP is specified, not released. There is no MCP server running at a college today and no date we are willing to put in writing. What is outlined here represents our locked architectural commitments, so you can evaluate our technical direction.
What the protocol will sit on top of.
Kenii MCP is designed to expose the modules you already license. These are the underlying systems it will read from and, for authorized staff keys, write to.
Digital catalog.
Expose active degree requirements, course descriptions, and catalog years to approved tools as browsable resources and read tools.
Guided pathways.
Ground student-facing tools in live interest matching, federal wage figures, and career outcomes already published on your program pages.
Curriculum governance.
Let authorized staff tools check proposal statuses, inspect voting records, and draft curriculum changes programmatically rather than by hand.
Kenii Assist.
Our own AI client is designed as a first-party consumer of this same layer, grounded on your core catalog database rather than a web scrape.
Tell us what you wouldbuild on day one.
There is no MCP demo to give you yet, and nothing to sign. If you want early access when it lands, tell us which tools your college would connect and what you want them to do, and we will bring you in as we build it.