MCP Server Triggers

Create a Trigger

MCP triggers can be created to run any time a client connects to the MCP server. This is useful for dynamic updating of server or tool instructions, as well as restricting tools based on the connecting user.Click the ⋮ icon in the top-right corner of your MCP server and select Triggers.Click Add Trigger to create a new MCP server trigger.

MCP servers currently only support one trigger per server.

Trigger Information

Give your trigger a name, description, and tags to help you identify it later. When you’re ready, click Save.

Select your newly created trigger to edit it.

Trigger Inputs

MCP Server triggers offer the following inputs: toolset
Contains the server information, such as the name and instructions.

{
  "id": 1,
  "name": "Server Name",
  "instructions": "Server Instructions"
}

tools[]
An object array that contains each tool.

[
  {
    "id": 1,
    "name": "Tool Name",
    "instructions": "Tool Instructions"
  },
  {
    "id": 2,
    "name": "Another Tool",
    "instructions": "Another Tool Instructions"
  }
]

prompts[] and resources[]
The prompts and resources attached to the server. Each prompt has id, name and description; each resource also has uri.auth
On a server with OAuth sign-in, the signed-in user’s {dbo, id, extras}. null on a server without sign-in.You can modify the tools or toolset by building logic in the trigger to do so. To narrow prompts or resources, return a prompts or resources list: only the IDs you return are offered, and a description you return replaces the stored one. Leave a key out to keep the full list, so existing triggers are unaffected.

Build

Test & Deploy

Team Collaboration

Integrations

Security

Tutorials

Enterprise

Agencies

Account and Settings

Legal