ℹ️ What is the MCP Server?¶
Info
New in Atfinity 17.
MCP, the Model Context Protocol, is how an AI tool talks to another system. The Atfinity MCP server gives such a tool the configuration of one tenant, to read and, where you allow it, to build on.
The tool acts as the person who signed in and granted it access, and can do nothing that person could not do themselves. Only a user who may change the configuration can grant access at all.
A tool asks either to read the configuration, or to read and change it, and you can hold a tool that asked for both to reading only.
Changes land in the draft, so you review them and put them live yourself. Release notes are the exception, since a tool with change access publishes those directly.
A tool also reaches the draft cases you test a configuration with, including the values in their fields. Live cases, their instances and their values are out of reach of a tool you connect, and stay with the Atfinity API. Atfinity Intelligence is the exception, since it works inside Atfinity rather than over this endpoint, and reaches live cases where you allow it.
What a tool reaches¶
A tool reads the whole configuration, and writes most of it: information and its structures, rules and their actions, documents with their boxes and files, ADX templates, pages with their widgets, columns and filters, tabs and process layouts, workflow states and transitions with their permissions, taxonomy options, RuLa functions, translations, assets and user roles. It also reports the configuration's errors and its pending changes, which is how it checks its own work.
It creates most of the skeleton too: an ontology, a process and a workflow, which is what a new area is built out of. A new workflow arrives with the same draft, approved and declined states the application gives one, and a new ontology and a new process arrive empty, so give them their fields and their layout in the same session. Changing or deleting those three stays with you. An ontology role and a shared taxonomy still have to exist before a tool can fill them in, so create those yourself and let it work inside them.
The server hands the tool Atfinity's own documentation for RuLa and ADX, so an expression it writes is built against the real function list rather than guessed.