# Apify MCP Server Scraper (`parseforge/apify-mcp-server-scraper`) Actor

Extract structured metadata from the Apify MCP Server API endpoint. Pulls server details, available tools with their titles and descriptions, authentication schemes, and transport configuration. Ideal for developers building MCP client integrations or monitoring server capabilities programmatically.

- **URL**: https://apify.com/parseforge/apify-mcp-server-scraper.md
- **Developed by:** [ParseForge](https://apify.com/parseforge) (community)
- **Categories:** Developer tools, AI
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $3.40 / 1,000 result items

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-event

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.

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 examples already wired to this Actor's own input schema, see the [API](#api) section below.

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`).

# README

[![ParseForge](https://raw.githubusercontent.com/ParseForge/apify-assets/main/banner-v4.webp)](https://apify.com/parseforge?fpr=vmoqkp)

### Apify MCP Server Scraper

**Scrape the full Apify MCP Server catalog: every tool, transport, and authentication scheme in one flat dataset.** Get the server metadata, all available tools with their annotations, and endpoint details. Export to CSV, JSON, Excel, or XML.

The Apify MCP Server exposes dozens of tools for web scraping and automation, but browsing them through an MCP client gives you one tool at a time. This Actor reads the complete server card from the official API endpoint and returns every tool, its description, its destructive and idempotent hints, and its authentication requirements in a single structured dataset. No MCP client setup, no manual discovery.

| Who uses it | What they scrape Apify MCP Server for |
|---|---|
| AI agent developers | Audit which MCP tools are available before integrating them into an agent loop. |
| Platform engineers | Document the full tool surface of the Apify MCP Server for compliance and change tracking. |
| Technical writers | Generate up-to-date tool lists and parameter tables for internal documentation. |
| Security reviewers | Inspect authentication schemes and destructive tool annotations across the entire server. |

### What it does

This Actor collects the full Apify MCP Server catalog, including server metadata, transport configuration, and every listed tool with its annotations, and returns each tool as a flat row.

- **Tool annotations:** each row includes read-only, destructive, and idempotent hints so you know what a tool can change.
- **Authentication audit:** see which schemes each tool requires and whether headers carry secrets.
- **Flat row per tool:** every tool becomes one row with its title, description, and server context, ready for spreadsheets.
- **Single API call:** the Actor hits the official server card endpoint once and unpacks the nested JSON for you.

Results export to CSV, JSON, Excel, or XML, or straight from the API.

### What you can do with Apify MCP Server data

**Populate an agent tool registry.**

An AI platform team runs this Actor weekly to refresh the list of available Apify MCP tools their agents can call, ensuring no tool is missed.

**Generate a compliance report.**

A security engineer scrapes the full tool list with destructive and authentication annotations to review which tools need approval before production deployment.

**Build internal API docs.**

A technical writer exports the dataset to Markdown and publishes an always-current reference page of every Apify MCP Server tool and its parameters.

**Monitor server changes.**

A DevOps engineer schedules daily runs and diffs the output to detect new, removed, or re-annotated tools in the Apify MCP Server.

### Why choose this scraper

| | What you get |
|---|---|
| **Full tool catalog** | Every tool the Apify MCP Server exposes, in one dataset |
| **Annotation hints** | Read-only, destructive, and idempotent flags per tool |
| **Authentication details** | Required schemes and whether headers contain secrets |
| **Transport info** | Endpoint URL and transport type for direct connection |
| **Server metadata** | Name, version, icon, and documentation links |

### What a Apify MCP Server record looks like

Every record returns as one flat JSON row. Here is a real one from a run:

```json
{
 "imageUrl": "https://apify.com/favicon.ico",
 "name": "com.apify/apify-mcp-server",
 "title": "Apify MCP Server",
 "description": "Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡",
 "version": "0.16.0",
 "websiteUrl": "https://docs.apify.com/integrations/mcp",
 "repositoryUrl": "https://github.com/apify/apify-mcp-server",
 "repositorySource": "github",
 "iconSrc": "https://apify.com/apple-icon.png",
 "iconMimeType": "image/png",
 "remoteType": "streamable-http",
 "remoteUrl": "https://mcp.apify.com/",
 "remoteHeaderName": "Authorization",
 "remoteHeaderDescription": "Apify API token for authentication with Apify platform services. For example 'Bearer <apify-api-token>'",
 "remoteHeaderRequired": true
}
```

Every value above comes from a real run. A field a record does not have comes back as `null`.

### Configure the run

Set a maximum number of tools to return. The Actor reads the full server card and stops after reaching your limit. The Input tab lists every parameter.

A first run with the defaults:

```json
{
 "maxItems": 10
}
```

A larger pull:

```json
{
 "maxItems": 200
}
```

### Free users

Free-plan runs return up to 10 results as a preview. [Upgrade your Apify plan](https://console.apify.com/sign-up?fpr=vmoqkp) to collect more results per run.

### Run it

1. [Create a free Apify account](https://console.apify.com/sign-up?fpr=vmoqkp).
2. Set your inputs and any filters, then click **Start**.
3. Export the results as CSV, Excel, JSON, or XML from the **Dataset** tab.

Run it programmatically through the [Apify API](https://docs.apify.com/api/v2) (`run-sync-get-dataset-items`) or the [ApifyClient](https://docs.apify.com/api/client/js) for JavaScript and Python.

### Use with AI agents (MCP)

Give an AI agent live access to Apify MCP Server through the Model Context Protocol. Add the Actor to Claude, Cursor, or any MCP client:

```bash
```

Then prompt it in plain language to run the scraper and read back the results.

### Troubleshooting

**Why am I getting fewer results than expected?**

Check the Max Items setting in your input. Free users are limited to 10 items. If you are a paid user, increase the maxItems value.

**The dataset is empty or the run failed.**

The server card endpoint may be temporarily unavailable. Retry the run after a few minutes. If the problem persists, check the Apify status page for incidents.

**Some tool fields are null or missing.**

Not every tool includes all optional fields like annotations or authentication schemes. Null values mean the field is not present in the server card for that tool.

**Can I get the output in a nested format instead of flat rows?**

The Actor flattens the server card into one row per tool by design. If you need the raw nested JSON, download the run's raw output from the Storage tab.

### FAQ

| Question | Answer |
|---|---|
| What is the Apify MCP Server? | It is Apify's Model Context Protocol server that exposes web scraping and automation tools to MCP-compatible AI clients. This Actor scrapes its full tool catalog from the official server card endpoint. |
| Do I need an MCP client to use this Actor? | No. The Actor calls the public server card API directly and returns the data as a flat dataset. You do not need an MCP client, Claude Desktop, or any other MCP host. |
| What data does each row contain? | Each row represents one tool and includes its name, title, description, annotation hints (read-only, destructive, idempotent), the server name and version, transport endpoint, and authentication requirements. |
| How often is the server card updated? | The server card reflects the live Apify MCP Server. Run the Actor on a schedule to capture changes as new tools are added or existing ones are modified. |
| Can I filter which tools are returned? | The Actor returns tools in the order they appear in the server card. You can set a maximum number of items to limit the output, then filter further in your downstream processing. |
| Does this Actor require authentication? | The server card endpoint is public. The Actor does not need an API token or login to fetch the tool catalog. |
| What export formats are supported? | You can export the dataset to CSV, JSON, Excel, or XML from the Apify platform. |
| Is there a limit on how many tools I can scrape? | Free users can scrape up to 10 tools as a preview. Paid users can scrape more items. |
| Can I use this to call the tools themselves? | No. This Actor only scrapes the tool metadata. To invoke the tools, connect an MCP client directly to the Apify MCP Server endpoint. |
| What is the transport type of the Apify MCP Server? | The server card includes the transport type and endpoint URL. The Actor captures this so you can configure your MCP client correctly. |

### Related actors

Browse the full [ParseForge collection](https://apify.com/parseforge?fpr=vmoqkp) for more scrapers.

🆘 **Need help?** Email parseforge@protonmail.com with your run ID, your input, and what you expected.

⚠️ **Disclaimer.** This Actor is unofficial and is not affiliated with, endorsed by, or sponsored by Apify Technologies s.r.o. It collects only publicly available data. You are responsible for using the collected data in compliance with the source's terms of service and applicable data-protection laws, including GDPR, CCPA, and PIPL. Do not use it to collect personal data unlawfully.

# Actor input Schema

## `maxItems` (type: `integer`):

Free users: Limited to 10 items (preview). Paid users: Optional, max 1,000,000

## Actor input object example

```json
{
  "maxItems": 10
}
```

# Actor output Schema

## `results` (type: `string`):

Complete dataset of all scraped records.

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "maxItems": 10
};

// Run the Actor and wait for it to finish
const run = await client.actor("parseforge/apify-mcp-server-scraper").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = { "maxItems": 10 }

# Run the Actor and wait for it to finish
run = client.actor("parseforge/apify-mcp-server-scraper").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "maxItems": 10
}' |
apify call parseforge/apify-mcp-server-scraper --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,parseforge/apify-mcp-server-scraper"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/QdFULwjRkj92LN7UI/builds/9UvfAj6qMrLM0nJM0/openapi.json
