Connect an AI assistant (MCP)
Let Claude or another MCP client build courses in your institution directly.
What this is — and who it's for
KlickCourse runs an MCP server (Model Context Protocol), which lets an AI assistant you already use — Claude, or any MCP-capable client — build courses in your institution directly, using its own conversation as the interface.
This is the technical route, and it means editing a config file. If you just want AI to build you a course, use Build with AI inside the admin instead — same result, nothing to install.
This is the technical route, and it means editing a config file. If you just want AI to build you a course, use Build with AI inside the admin instead — same result, nothing to install.
Connecting
Point your client at your institution’s own address and authenticate with an ordinary API key. There is no separate MCP credential.
The key is a course:write key from Admin → API keys. It only ever reaches your own institution — a key minted for one institution simply finds nothing on another’s address.
{
"mcpServers": {
"klickcourse": {
"type": "http",
"url": "https://<your-institute>.klickcourse.com/mcp",
"headers": { "Authorization": "Bearer kc_…" }
}
}
}The key is a course:write key from Admin → API keys. It only ever reaches your own institution — a key minted for one institution simply finds nothing on another’s address.
What the assistant can do
Create and import courses, add modules and lessons, write module checks and the final quiz, set pass thresholds, and organize the catalog into categories. It can also read your existing courses back, so you can ask it to extend one rather than start over.
It is given the platform’s own course-design methodology and its constraints as reference material, so it builds to the same standard as the in-dashboard builder rather than guessing what KlickCourse accepts.
It is given the platform’s own course-design methodology and its constraints as reference material, so it builds to the same standard as the in-dashboard builder rather than guessing what KlickCourse accepts.
The limits, and why they exist
Drafts only. There is no publish tool, and every content change is refused on a course that is already live. An assistant cannot alter what your students are currently seeing, and it cannot put anything in front of them — publishing is yours, after you have read the draft.
It also cannot set prices, touch payments or refunds, see your roster or learner data, mint or revoke keys, or revoke certificates. Deleting is allowed for drafts only, and refused outright for a published course or one with enrolled learners — it exists because lessons keep the order they were created in, so rebuilding a badly-ordered draft is sometimes the only repair.
Everything the assistant does is recorded in your audit trail as API-key activity, the same as any other key.
It also cannot set prices, touch payments or refunds, see your roster or learner data, mint or revoke keys, or revoke certificates. Deleting is allowed for drafts only, and refused outright for a published course or one with enrolled learners — it exists because lessons keep the order they were created in, so rebuilding a badly-ordered draft is sometimes the only repair.
Everything the assistant does is recorded in your audit trail as API-key activity, the same as any other key.
Full reference
The developer portal documents every tool, its arguments, and the course specification format — alongside the REST Course Builder API, which the MCP server is a thin layer over.