# Monitor an MCP Server for Tool Changes

**Use case:** 

Detect tools added, removed or changed on an MCP server between runs. Schedule it and catch drift.

## Input

```json
{
  "url": "https://gozerai.com/mcp/library",
  "timeoutSecs": 30
}
```

## Output

```json
{
  "kind": {
    "label": "Change",
    "format": "string"
  },
  "tool": {
    "label": "Tool",
    "format": "string"
  },
  "detail": {
    "label": "Detail",
    "format": "string"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The MCP Server Diff Actor is ready to run with the inputs already set for "Monitor an MCP Server for Tool Changes". [Sign up or log in](https://console.apify.com/create-task-from-example/o0P3HGRlim16rpDgR) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Monitor an MCP Server for Tool Changes" task

The MCP Server Diff Actor will start running based on the input automatically. You can also change all the input fields, like MCP endpoint URL and request timeout (seconds), to match your specific use case.

### 3. Receive the "Monitor an MCP Server for Tool Changes" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as change, tool, and detail.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Monitor an MCP Server for Tool Changes" task via API](https://apify.com/conserving_mastodon/mcp-server-diff.md).

## About this Actor

This example demonstrates how to use [MCP Server Diff](https://apify.com/conserving_mastodon/mcp-server-diff.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/conserving_mastodon/mcp-server-diff.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/conserving_mastodon/mcp-server-diff.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).