Thought Industries MCP Connector

Overview

The MCP Connector exposes your academy to AI assistants through the Model Context Protocol (MCP). An admin connects an assistant once by signing in on the academy, and the assistant then calls connector tools as that admin. The connector never grants more than the admin’s own Thought Industries role allows. For how sign-in, tokens, and scopes work, see Authentication & security.

Before you start

• The connector is enabled for your academy. It is off by default. Your Thought Industries contact turns it on.
• You have an admin account on the academy, one that can open the admin UI. Learner accounts can’t connect.
• Your client supports remote MCP servers with OAuth. On Claude Team and Enterprise plans, only an organization Owner can add a custom connector. Members then connect to it.
• Each admin can have up to 20 connected assistants per academy.

Connector URLs

Replace your-instance.thoughtindustries.com with your academy’s domain. Custom domains work too. Every admin uses the same URL: what the assistant can reach comes from the account that signs in, not from the URL.

Both URLs, with setup snippets to copy, are on the MCP Connector page of the admin UI (/learn/manager/mcp-connector). To keep a read-only connection alongside a full-access one, add both as separate connectors.

Connect a client

No client needs an OAuth client ID or secret. Starting the sign-in opens a browser window where you sign in to your academy the way you usually do (password, single sign-on, or two-factor) and approve the connection.

Claude (web and desktop)

1. Go to Customize → Connectors, select + Add, then Add custom connector. On Team and Enterprise plans, an Owner does this under Organization settings → Connectors (Add → Custom → Web).
2. Enter a name, such as Thought Industries, and the connector URL, then select Continue.
3. Keep the detected authentication settings, with Use Claude’s published identity selected under OAuth client, and select Add.
4. On Team and Enterprise plans, each member then goes to Customize → Connectors and selects Connect on the connector.
5. On the consent page, review what the assistant may do, grouped by area such as users, courses, and enrollments. Everything your role allows is ticked. Untick anything the assistant shouldn’t do, then select Allow.

Other clients

claude mcp add --transport http thought-industries https://your-instance.thoughtindustries.com/v3/mcp

• Claude Code: run the command, adding --scope user to use the connector in every project (the default covers the current project only). Then run /mcp, select thought-industries, and choose Authenticate.
• Cursor: add the entry in the MCP section of Cursor Settings, then select Connect next to thought-industries.
• VS Code: run MCP: Open User Configuration from the Command Palette, or use .vscode/mcp.json for one workspace. Add the entry, select Start above it, and allow VS Code to sign in when it asks.
• Other clients: the mcp-remote bridge is for clients that only run local (stdio) servers. It needs Node.js 18 or later. Add the entry and restart the client.
• Read-only: use the read-only URL under a separate key, such as thought-industries-readonly.

Verify the connection

Ask the assistant to run whoami, for example: “Use the Thought Industries connector to tell me who I’m connected as.” It reports your user, academy, role, and the portals you can work in. Then ask it to list your portals and check the names match what you expect.