Core Docs - Core Concepts - Set Up an MCP Agent

Rock Version: v20.0
Last Modified: 2026-05-26 1:09 PM

A Model Context Protocol (MCP) agent connects Rock to an external AI tool running on someone's computer, like Claude Desktop. Once it's set up, staff can use that tool to look up records, log notes and take actions in Rock without opening Rock in a browser.

An admin configures the connection once in Rock. Each staff member then connects their own external tool using the same endpoint and logs in with their own Rock credentials.

Set up the agent in Rock

Navigate to Admin Tools > Settings > AI Agents and select Agents. Add a new agent and set the Type to MCP. Configure the Audience, Role and Instructions the same way you would a Chat agent.

Save the agent. Rock will display the connection details you'll need in the next step.

MCP Security = Agent Security
If you're wondering how to set Agent security, it's easy. You can click ti ti-lock from the Agent screen and pick who has View, Edit or Administrate privileges. Note that by default, only the RSR - Rock Administrator role will have access. You must give View access to those you want to be able to use your Agent.

Get the connection URL

After saving, Rock provides an MCP endpoint URL. Copy this. You'll need it to configure the external tool. You can find this by clicking your profile, then My Settings, after that click MCP Servers.

Connect the external tool

In your external AI tool, add Rock as an MCP server using the endpoint URL from the previous step. When connecting for the first time, you'll be prompted to log in with your Rock credentials. Each staff member goes through this step once with their own login.

Once connected, the tool can work with Rock data using that person's permissions — the same access they have when logged into Rock directly.

Here's the Connector in action. Just describe what you need in plain language, and Claude will know when to reach for your Rock data automatically.

It really is that simple. You can build interactive charts, formatted files, custom skills and much more, all from a natural question. The example below shows Claude pulling up Ted Decker's profile.

What's different about MCP agents

A few things work differently compared to Chat agents.

No conversation history. The external tool manages conversation history, not Rock. This is normal for MCP. The tool handles context on its end.

Context anchors don't apply. Context anchors are a Chat-only feature. They have no effect on MCP agents.

The system prompt works differently. Chat agents receive your full organization context and agent instructions automatically. MCP agents don't get those by default — the external tool manages the conversation. You can account for this by writing thorough instructions on the agent and assigning the right skills.

Security

MCP agents follow the same security model as everything else in Rock. Each person authenticates with their own Rock login, so the agent can only access what that person is permitted to see. The Role field on the agent controls who can connect to it at all.

Sharing an Agent without a login
The public MCP endpoint does not require authentication. Anyone who connects is treated as an anonymous visitor, even if logged in. To use this, open the agent security and confirm All Users have View access. URL format: /api/v2/mcp/public/{agentname}. Only attach skills you would be comfortable sharing with someone you do not know.