# MCP Server Data Extractor — Extract Tool Schemas & Resources (`yourwingman/mcp-server-data-extractor`) Actor

Connect to any MCP server and extract tool schemas, resource definitions, and prompt templates. Essential for AI agent development, function calling setup, and LLM tool integration.

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

## Pricing

Pay per event + usage

This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage.

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

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
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.
Actors are written with capital "A".

## 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.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## MCP Server Data Extractor

Connect to any MCP (Model Context Protocol) server and extract tool schemas, resource definitions, and prompt templates.

### Why This Actor?

MCP (Model Context Protocol) is an open protocol that enables AI models to interact with external tools and data sources securely. This actor helps you discover and inspect MCP server capabilities:

- **AI Agent Developers**: Quickly see what tools an MCP server offers
- **LLM Integrators**: Get the JSON schemas you need for function calling
- **Tool Builders**: Verify your MCP server's tool definitions
- **System Administrators**: Audit MCP server endpoints

### Input

| Field | Type | Default | Description |
|-------|------|---------|-------------|
| `mcpServerUrl` | string | — | URL of the MCP server endpoint |
| `requestTimeout` | integer | 30 | Timeout per request (seconds) |
| `includeResources` | boolean | true | List available resources |
| `includePrompts` | boolean | true | List available prompts |
| `serverHeaders` | object | {} | Custom HTTP headers (auth tokens, etc.) |

### Output

Each dataset entry represents a tool, resource, or prompt definition:

| Field | Type | Description |
|-------|------|-------------|
| `type` | string | Entry type: `tool`, `resource`, or `prompt` |
| `name` | string | Name of the tool/resource/prompt |
| `description` | string | Human-readable description |
| `inputSchema` | string | JSON schema for input parameters |
| `serverName` | string | Name of the MCP server |
| `serverVersion` | string | Server version |
| `uri` | string | Resource URI (resources only) |
| `mimeType` | string | Resource MIME type (resources only) |

### Example

```json
{
  "mcpServerUrl": "https://mcp.example.com/api"
}
```

### Protocol Support

- JSON-RPC 2.0 over HTTP POST
- MCP protocol version 2024-11-05
- Supports `tools/list`, `resources/list`, `prompts/list`

# Actor input Schema

## `mcpServerUrl` (type: `string`):

URL of the MCP server endpoint (e.g., https://mcp.example.com/mcp).

## `requestTimeout` (type: `integer`):

Timeout for each JSON-RPC request to the MCP server.

## `includeResources` (type: `boolean`):

Whether to list available resources from the server.

## `includePrompts` (type: `boolean`):

Whether to list available prompts from the server.

## `serverHeaders` (type: `object`):

Additional HTTP headers to send with requests (e.g., API keys, auth tokens).

## Actor input object example

```json
{
  "mcpServerUrl": "https://mcp.example.com/mcp",
  "requestTimeout": 30,
  "includeResources": true,
  "includePrompts": true,
  "serverHeaders": {}
}
```

# Actor output Schema

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

Whether this is a tool, resource, or prompt definition

## `name` (type: `string`):

Name of the tool, resource, or prompt

## `description` (type: `string`):

Description of what this entry does

## `inputSchema` (type: `string`):

JSON Schema for the tool/prompt input parameters

## `serverName` (type: `string`):

Name of the MCP server

## `serverVersion` (type: `string`):

Version of the MCP server

## `uri` (type: `string`):

URI template for resources (for resource entries only)

## `mimeType` (type: `string`):

MIME type of the resource content

# 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 = {
    "mcpServerUrl": "https://mcp.example.com/mcp"
};

// Run the Actor and wait for it to finish
const run = await client.actor("yourwingman/mcp-server-data-extractor").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 = { "mcpServerUrl": "https://mcp.example.com/mcp" }

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

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

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

```

## CLI example

```bash
echo '{
  "mcpServerUrl": "https://mcp.example.com/mcp"
}' |
apify call yourwingman/mcp-server-data-extractor --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=yourwingman/mcp-server-data-extractor",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/8MUeECXx2HqhhjNfA/builds/2F5HSrKTC0VZr1ViV/openapi.json