OpenCoreAgents & Actions

MCP Actions

View as Markdown

MCP Actions let an Agent use tools exposed by an MCP server. Admins can manage every server; Curators can create servers and maintain only the ones they created. Users authorize only the access prompts they receive, and the runtime calls tools only from the saved Action configuration.

How MCP Actions work

An MCP server publishes one or more tools that an Agent can use. OpenCore reads the configured server’s available tools, and an Admin or the Curator who owns the server selects which ones belong in an Action. The Agent can use those selected tools only when its configuration and the current run allow it.

Add an MCP server

  1. Sign in as an Admin or Curator and open MCP Actions.
  2. Add the approved MCP server using the deployment’s protected configuration fields.
  3. Review the tools discovered from the server and select only the tools required for the intended Agent workflow.
  4. Save the Action, attach it to an Agent, and publish the Agent only after review.

Admins can create or change any MCP server, select its tools, complete protected configuration, and attach its Action to any editable Agent. Curators can create MCP servers but can change only servers they created. This ownership rule is the same for Curators and Global Curators; Action ownership is not inherited from curated or member groups.

The server owner should record the intended tools and operating limits. Keep an Action narrowly scoped so that its configured tools match the Agent’s purpose. Ownership controls changes, deletion, and protected credential maintenance after creation.

A Curator can attach any currently available MCP Action to an Agent they can edit. Deployment-level model, integration, security, Index Settings, Usage, and organization configuration remain Admin responsibilities.

Authentication responsibility

Configure server authentication only through the protected Action settings available to the Admin or server owner. Do not place secrets in Agent instructions, user messages, source control, or shared documentation.

The server owner is responsible for configuring and rotating service credentials; an Admin can also maintain them. A user authorizing an Action run does not receive those credentials and cannot use that authorization to reconfigure the MCP server.

Verify tools

First verify as an Admin or as the Curator who owns the server that the intended tools appear after it is saved. Then run the attached Agent with a representative approved request and confirm that the expected tool is called, the result is usable, and users outside the shared scope cannot access the Agent.

At runtime, inspect the reported tool result or error rather than assuming a tool is available. Recheck the server connection, selected tool, Agent attachment, and applicable user authorization when a call cannot run.

Troubleshooting

If tools do not appear, confirm that the server configuration is complete and that the server can expose tools to the deployment. If a tool is present but fails at runtime, verify its service-side permissions and the inputs allowed by the server.

If a user cannot use an otherwise working Action, check the Agent’s sharing scope and any authorization prompt before changing server configuration. Re-test after each change with an approved request.