Magentrix includes an MCP (Model Context Protocol) server. AI tools that support MCP can connect to your portal, read your records and, if your admin allows it, create and update them. Each person signs in with their own Magentrix account, so the AI works within that person's permissions.
Each person signs in to Magentrix with OAuth.
The MCP server gives AI tools a set of named actions for working with your portal. Most of them appear only when the matching Magentrix module is licensed.
The AI runs a query across the records you can see and answers in the chat.
Create, update or delete records from the chat, if your admin allows it.
Create wiki pages and blog posts as drafts, then publish them with the same version history as the portal.
Create Document Library files, or turn HTML into a PDF and attach it to a record.
Add lessons and quizzes to courses, assign courses to users and check your team's progress.
Check tier criteria, deal registration forms, deals close to expiring and referral links.
You set up the connection inside the AI tool by adding your portal's MCP URL. Each vendor's steps change often, so follow their current guide.
Each AI tool connects as one user, through that user's security role. Admin settings for AI can narrow that access further.
The first time an AI tool connects, Magentrix shows a sign-in screen listing what the tool is asking for: read access, write access or both.
External AI tools can't connect until an admin enables MCP for external AI assistants in AI Settings.
Allow record changes for all users or only for specific security roles.
Turn Insert, Update and Delete on or off separately. Turn all three off for read-only access.
Admins can see every connected AI tool and revoke one, which disconnects every user signed in through it.
When the AI publishes a wiki page or blog post, it uses the publish tool, so the version history is kept.
Both use the same security underneath. The MCP server adds a narrower layer of admin controls on top.
| Question | MCP server | REST API |
|---|---|---|
| How it signs in | OAuth, as the signed-in user | API key tied to the user's role |
| What it can call | A set list of named tools | Any entity, query or file endpoint |
| Extra admin limits for AI | Yes | No, role permissions only |
| Publishing steps enforced | Yes | No, writes go straight through |
| Bulk delete and upsert | No | Yes |
| Built for | An AI assistant taking actions you control | A program you trust with full entity access |
You can also give an AI tool a Skill.md file that describes the Magentrix REST API, as an alternative to the MCP server.
See the MCP server working with your own AI tools in a demo.