Connect Claude to Cubite LMS: add the connector, pick sites and permissions, and what Claude can do

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.

Add Cubite to Claude

  • Press Add to Claude on cubite.io/mcp, or in Cubite under Admin, your site, Integrations, AI assistants (MCP). Claude opens its Add custom connector dialog with Cubite's name and address filled in; review them and continue.
  • Or add it by hand: in Claude, open Customize, then Connectors, choose + Add, then Add custom connector, name it Cubite, paste https://cubite.io/api/mcp/mcp and continue. On a Claude Team or Enterprise plan, an owner adds the connector under Organization settings, then Connectors, and each member then connects to it under Customize, then Connectors. Claude's Free plan allows one custom connector.
  • Keep the sign-in settings Claude marks Detected. Where the dialog shows an OAuth client setting (in some layouts under Advanced), choose Register automatically: Cubite's sign-in registers Claude automatically and does not support Claude's published identity. Then choose Add.
  • Press Connect, sign in to Cubite, tick the site or sites the connection may act on, review the permissions and approve. In a chat, switch the connector on from the + button, under Connectors.
  • Claude Code: run claude mcp add --transport http cubite https://cubite.io/api/mcp/mcp, then type /mcp inside Claude Code and finish the same sign-in in your browser.

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

One site or several

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.

Permissions

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.

Every permission and endpoint

What Claude can do on your site

  • Build courses: create a course, write its sections and units (in course content, H2 headings become sections and H3 headings units), add quizzes and question banks, and upload SCORM or xAPI packages.
  • Publish pages and posts: page_create makes a page, an FAQ page or a video page and keeps it hidden unless you ask Claude to publish it (a hidden page is unlisted and not indexed, but anyone with its address can open it); blog_create publishes a post unless you ask for a hidden draft.
  • Add a link to the site's header or footer with nav_link_add, which adds one link and leaves the others as they are.
  • Manage learners: invite or create learners, enroll one or many, and manage groups and learning paths.
  • Run the site: issue and revoke certificates, grade assignments and open responses, moderate discussions, review applications, post announcements and read form responses.
  • Read your numbers: site, course and learner reports, and Search Console data where your site has connected it, each behind its own permission.
  • Search and read your site's courses, pages, posts and learning paths.

What Cubite tells Claude after a change

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).

What Claude cannot do through Cubite

  • Reach a site you did not tick, or one you do not administer.
  • Set up webhooks, create API keys or approve other assistant connections: those stay in Admin. With the webhooks permission, Claude can read your webhook subscriptions and their delivery log.
  • Change your site's address or custom domain, its payment, email-provider or sign-in provider keys and settings, its custom CSS, its footer HTML or its tracking tags.
  • Delete SCORM or xAPI packages, or list and delete uploaded images and files.
  • See learner names or emails without a permission that grants them.
  • Spend AI credits: your own Claude does the AI work, and Cubite sells no AI credits.

Disconnect

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.

Does Claude need an API key to connect to Cubite LMS?

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.

Does connecting Claude to Cubite LMS cost extra?

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.

Can one Claude connection manage several Cubite LMS sites?

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.

What can Claude change on a Cubite LMS site?

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.

Talk to a person

Book a 30-minute call, or email amir@cubite.io.

Support

How can we help?

Send us a message and we'll get back to you shortly.

We typically respond within 24 hours