Short answer (updated November 17, 2026)
Cubite LMS's Growth plan at $290 a month (or $2,900 a year) lets you use your own AI assistant (Claude or ChatGPT) through its MCP server, with no AI credits to buy. Press Add to Claude on cubite.io/mcp, or add https://cubite.io/api/mcp/mcp in Claude as a custom connector, then sign in to Cubite, tick the site or sites you administer and keep only the permissions you want. Claude then gets the Cubite tools those permissions allow (the server has 142) and works only on the sites you ticked. There is no API key to copy.
Claude's steps follow Claude's help center, Claude's connector documentation and Claude Code's documentation, read November 17, 2026.
Cubite's MCP server and every toolRun your LMS from Claude and ChatGPT, step by step
Anyone who administers a Cubite site can connect it: the Cubite sign-in lists the sites you administer, and you tick one or several. One address serves every site, because the site comes from your sign-in, not from the URL.
With several sites, Claude works on the site you picked first unless it names another connected site by its domain, and Cubite refuses any site outside the connection. To keep a connection to one site, tick only that site.
When Claude connects, it asks for every permission Cubite's server lists (Claude's connector documentation, read November 17, 2026), so the Cubite sign-in shows all 37, each its own checkbox, ticked to start. Untick anything you do not want to grant: the connection gets only what stays ticked, and Claude sees only the tools those permissions allow.
To start read-only, keep only site:read, pages:read, courses:read and reports:read: site settings, pages, courses and the aggregate reports, which never return a learner's name or email. Permissions that reveal learner names and emails, create accounts or upload content that runs in a browser on your domain are highlighted before you approve.
The permissions are the scopes an API key carries too, such as courses:read, enrollments:write and reports:read, each listed on the API reference.
After Claude creates or changes a page, a blog post, a course, the homepage or a header or footer link, Cubite's reply says where it is live now, at its address on your own domain when that domain is serving the site, or says it is hidden and how to publish it.
If a block Claude wrote will not display the way it meant, such as text placed before a course's first unit, where learners never see it, or a style that block type does not have, the reply lists the problem. The content is saved as sent, so Claude can fix it and save again.
Cubite also tells Claude that grading, issuing certificates and approving applications email real learners, so it should confirm with you before doing them in bulk. Claude can also ask you to approve a tool before using it, and Allow always lets that tool run without asking again (Claude's help center, read November 17, 2026).
In Cubite, open Admin, your site, Integrations, AI assistants (MCP). Connected AI assistants lists each connection with its permissions, the sites it covers, who authorized it and when it was last used. Disconnect stops its access to every site it covers at once; nothing it already created is removed.
In Claude, you can also remove the connector under Customize, then Connectors. Each Cubite access token lasts an hour and is renewed with a refresh token; Cubite revokes the whole connection if an old refresh token is replayed, and when the person who connected it deletes their Cubite account.
No. Claude connects to Cubite LMS through a browser sign-in (OAuth), so there is no key to copy. API keys are for scripts and server-to-server clients that cannot open a browser: a site admin creates one in Admin, under Integrations, API keys, and the client sends it as a bearer token to the MCP server.
No. The MCP server is part of Cubite LMS Growth, at $290 a month or $2,900 a year, whose plan lists "Headless API, webhooks and MCP server". There is no separate MCP price and no AI credits to buy; Claude itself runs on your own Claude account.
Yes, for Cubite LMS sites you administer: tick each one on the Cubite sign-in. Claude works on the site you picked first unless it names another connected site by its domain, and Cubite refuses any site outside the connection.
On a Cubite LMS site, Claude changes only what the permissions you granted allow, and sees only the tools for them. Read permissions let it look; write permissions let it create and change courses, pages, enrollments, certificates and grades, each one separately. Webhooks, API keys, the site's domain and its payment, email-provider and sign-in keys stay in Admin.
Send us a message and we'll get back to you shortly.