Installation is as short as it gets for a database server — `uvx mcp-server-iris` and the connection details, with no clone and no compile. The scope of what an agent can do is entirely the scope of the IRIS account and namespace you give it, so that choice is the whole security decision here.
An MCP server for InterSystems IRIS, the data platform used for interoperability and healthcare integration work. It connects to a running IRIS instance by host, port and namespace with a username and password, and exposes it to an MCP client — the README's screenshot shows it used for IRIS interoperability work from Claude.
A connection to one IRIS instance, addressed by `IRIS_HOSTNAME`, `IRIS_PORT` and `IRIS_NAMESPACE`, authenticated with `IRIS_USERNAME` and `IRIS_PASSWORD`. The namespace is the scope boundary that matters: whatever the account can reach in that namespace is what the client can reach, so pick both deliberately.
A running InterSystems IRIS instance and an account on it. Five environment values point the server at it — hostname, port, namespace, username and password — with the README's example using the defaults `localhost`, `1972` and the `USER` namespace. Install `uv` and run it as `uvx mcp-server-iris`; nothing to build.
One command — uvx mcp-server-iris