MCP Server
The AI Rule Engine can act as a Model Context Protocol (MCP) server, so an AI client — such as Claude, Cursor, or VS Code — can connect to your environment, run your rule sets, and read selected files and logs.
What it lets you do
Once connected, an AI client sees your rule sets as tools it can run on your behalf, and it can read the files and execution logs you have allowed. That lets an assistant trigger your automations, inspect what happened, and use the results as part of a larger task — all without you copying data back and forth by hand.
Enabling the server
The MCP server is off until an administrator turns it on for the environment. Once enabled, you create a connection token that a client uses to identify itself. As with an API key, the token value is shown only once when you create it, so copy it right away. Creating or deleting tokens requires an administrator role, and deleting a token immediately cuts off any client using it.
Scoping a connection
A connection token is the security boundary: a client can only see and do what the token allows. When you create one you choose:
- Rule sets — every rule set in the organization, or a specific allow-list.
- File access — off, all stored files, or only files under a chosen folder.
- Log access — whether execution logs can be read.
- Expiration — an optional expiry date.
Connecting a client
The MCP screen helps you wire up popular clients: it offers one-click setup for tools like Cursor and VS Code, a ready-to-paste command for Claude, and the configuration details you need for any other MCP-capable client. In each case you point the client at your environment and give it the connection token.
Authorizing without pasting a token
Instead of pasting a token, a client can ask for access through a guided authorization flow: it sends you to a consent screen where you approve the connection and choose its scope, and the client receives its own access automatically. You stay in control of what it can reach, and you can review or revoke it at any time.
Approving and revoking connected clients is covered in OAuth & App Authorizations.