ChatGPT, Claude and MCP
Connect ChatGPT, Claude, Claude Code and any MCP client to one Aladia workspace, with the permissions of your role.
Tested in production on 29/09/2026
How the Aladia MCP server works
ChatGPT, Claude and the other AI assistants connect to Aladia through the Aladia MCP server (Model Context Protocol):
https://api.aladia.io/mcp- It works inside one workspace: the one you approve when you connect (an academy or your personal workspace). It never sees other workspaces.
- It has the permissions of your role in that workspace: what you cannot do in Aladia, the assistant cannot do either.
- Connecting creates an API key named <App> · MCP in Settings → API keys. Delete the key to disconnect: the connection stops at once.
- Every tool the assistant uses appears in the Activity log marked via MCP.
- An integration shows Connected when it made at least one request in the last 30 days.
What the assistant can do:
| Tool | What it does |
|---|---|
get_workspace | Who is connected and in which workspace |
list_courses | The courses you teach (or attend) |
get_course | Details and outline of a course |
list_course_students | The students of a course |
list_calendars, list_calendar_events | Calendars, events and lessons in a date range |
list_grading_queue | Assignments and tests waiting to be graded |
search_documents | Search the documents you can open |
create_calendar_event | Create an event in your calendar — the only tool that changes data; the assistant asks you to confirm first |
The whole workspace from Claude or ChatGPT (pilot)
In the pilot workspaces the MCP server exposes the same tools as ARIA, the assistant inside Aladia: about 240 tools instead of the nine above, so you can run your workspace from Claude or ChatGPT, settings included.
| Area (toolset) | What the assistant can do |
|---|---|
workspace | Spaces and folders, sidebar pins, find people, search the Aladia help center |
courses | Course drafts and texts, chapters and lectures, categories, language, settings, editions, price, cover, publication, exams in a course, work to grade |
people | Members and roles of courses, spaces and the academy, invitations and invite links |
calendar | Calendars and events, participants, weekly planning of lectures, closures, Google Calendar availability |
chat | Rooms, messages, sidebar sections, threads and the inbox |
documents | Documents, exam collections and exams, whiteboards |
library | Book libraries, books and companion volumes, members, books used in courses |
teaching | Subject areas, subjects and levels, their books and teachers |
social | Feed, posts and questions, comments and reactions, followers, your profile, stories and highlights |
branding | Name, colors, email sender and reply-to addresses, Marketplace storefront (carousels, categories, publishing), mobile app appearance |
domain | Website domain and email from your own domain: the DNS records to create, verification, removal |
forms | Forms (draft, blocks, design, publishing, archive), requests (read-only), attributes |
access | Custom roles and their permissions, teams and members, workspace SSO |
settings | Plan and usage (read-only), integrations status, API keys, webhooks, email templates |
events | Public events: page, free or paid tickets, publishing, cancelling, registrations |
academic_year | Academic year: creation, preparation of editions and lessons, issues to fix, publishing, closing |
- Same permissions as in the app: every tool runs with your role in the workspace. Tools reserved to a role (for example managing the academy members) do not even appear to people without that role, and in a personal workspace the academy tools are hidden.
- Confirmations: each tool tells the assistant whether it only reads, changes data or is destructive (deletes, removes, revokes, publishes, changes roles, permissions, prices, domain or SSO). Claude and ChatGPT ask you to confirm before changes; review destructive ones carefully.
- Plan: a feature that needs a higher plan (website domain, email from your domain, SSO, mobile app) answers that an upgrade is needed, with the link to Settings → Plans, as in the app. Reading, checking and removing a domain always work.
- Payments only on Stripe: plan, trial and usage can be read, not changed. To change plan or pay, the assistant sends you to Settings → Billing.
- No secrets: existing API keys show only their last four characters, SSO and app store credentials only whether they are connected, webhooks never their signing secret. A new API key (you need the permission to create keys) appears only once, in the answer that creates it: copy it right away.
- Images: logo, cover, favicon and app icons are uploaded from Settings in the app.
- Only some areas: many tools take space in the assistant's context. To connect only some areas add them to the URL, for example
https://api.aladia.io/mcp?toolsets=courses,calendar, or?toolsets=branding,domain,formsfor settings only. Settings → Integrations → Aladia MCP lists the tools you can use, by area. - In ARIA: in the pilot workspaces ARIA, the assistant inside Aladia, also has the settings, events and academic year tools, and asks you to confirm before every change.
- Not available outside Aladia: action plans confirmed in one click, the profile picture, and images attached to an ARIA conversation (the cover can still be generated with AI from
update_my_profile). In the full setsearch_documentsbecomeslist_documents.
To connect an assistant you need the Owner, Admin or Developer role in the workspace (the same permission as creating an API key).
Connect Claude
Settings → Integrations → Claude shows the server URL and these steps.
On claude.ai, the desktop app and mobile (Free, Pro and Max plans):
- In Claude open Customize → Connectors.
- Choose Add custom connector.
- Name it Aladia and paste
https://api.aladia.io/mcp. - Click Add, then Connect: Aladia opens. Sign in, check the workspace and click Allow.
- In a chat, open + → Connectors and turn Aladia on.
On Team and Enterprise plans an Owner adds the connector from Organization settings → Connectors → Add → Custom → Web; each member then clicks Connect with their own Aladia account.
Claude Code (terminal):
claude mcp add --transport http aladia https://api.aladia.io/mcpThe first /mcp opens the Aladia sign-in. Without OAuth, use an API key: add --header "Authorization: Bearer <API_KEY>".
Connect ChatGPT
ChatGPT connects Aladia as a developer-mode app (Plus, Pro, Business, Enterprise and Edu, on the web):
- Open Settings → Security and login and turn on Developer mode. In Business and Enterprise workspaces an admin enables it first.
- Go to ChatGPT apps and press + to create an app.
- Name it Aladia, add a description and, under Connection, paste
https://api.aladia.io/mcp. - Choose OAuth, create the app and sign in to Aladia: check the workspace and click Allow.
- In a new chat, add Aladia from the tools menu (Developer mode).
ChatGPT asks for confirmation before any tool that writes. When we add tools, open the app and use Refresh.
Other MCP clients and API keys
Settings → Integrations → Aladia MCP is for any other client (Cursor, your own agents, the Anthropic and OpenAI APIs):
- OAuth 2.1 with dynamic client registration and PKCE: clients that support it connect on their own from the URL.
- Or an API key as a Bearer token:
Authorization: Bearer <API_KEY>. Create MCP key creates a dedicated key and shows it once; copy it right away.
{
"mcpServers": {
"aladia": {
"url": "https://api.aladia.io/mcp",
"headers": { "Authorization": "Bearer <API_KEY>" }
}
}
}
Each key is limited to 120 requests per minute (20 changes per minute).