# MCP Tool Manifest Generator (`junipr/mcp-tool-manifest-generator`) Actor

Generate structured MCP-style tool manifests from supplied tool definitions, OpenAPI-like docs, JSON schemas, Markdown docs, or existing function definitions.

- **URL**: https://apify.com/junipr/mcp-tool-manifest-generator.md
- **Developed by:** [junipr](https://apify.com/junipr) (community)
- **Categories:** SEO tools, Developer tools
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $6.50 / 1,000 schema validateds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

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 Tool Manifest Generator

### Store Positioning

**Store title:** MCP Tool Manifest Generator

**Short description:** Generate structured MCP-style tool manifests from supplied tool definitions, OpenAPI-like docs, JSON schemas, Markdown docs, or existing function definitions.

**SEO title:** MCP Tool Manifest Generator — API, schema, and developer QA

**SEO description:** Generate structured MCP-style tool manifests from supplied tool definitions, OpenAPI-like docs, JSON schemas, Markdown docs, or existing function definitions. Use it to catch contract drift, schema mistakes, unsafe endpoint assumptions, and developer-tool quality issues before release.

**Categories:** SEO\_TOOLS, DEVELOPER\_TOOLS

**Keywords:** mcp, tool, manifest, generator, structured data, schema, openapi, api testing, api/developer qa

### Pay-Per-Event Pricing

This actor uses pay-per-event pricing. Event prices include Apify platform usage; users are not expected to pay a separate platform-usage pass-through charge for the configured pricing model.

- Tier: A1 — API/developer QA
- Primary event: `schema-validated` at $0.00650 base
- Default max charge: $10.00
- Store discounts: FREE/BRONZE base, SILVER discounted, GOLD deepest approved discount

Event set:

- `actor-start`: base $0.00500, GOLD $0.00400. MCP Tool Manifest Generator: charged when actor start is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `schema-validated`: base $0.00650, GOLD $0.00520. MCP Tool Manifest Generator: charged when schema validated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `contract-rule-checked`: base $0.00390, GOLD $0.00312. MCP Tool Manifest Generator: charged when contract rule checked is completed. The price includes Apify platform usage; no separate usage pass-through is intended.
- `report-generated`: base $0.05000, GOLD $0.04000. MCP Tool Manifest Generator: charged when report generated is completed. The price includes Apify platform usage; no separate usage pass-through is intended.

### Public Task Concepts

- Audit MCP Tool Manifest controls on a capped public sample
- Find high-priority MCP Tool Manifest issues before release
- Validate MCP Tool Manifest evidence from supplied pages
- Prioritize MCP Tool Manifest fixes with severity and proof
- Export MCP Tool Manifest QA rows for client review

Generate structured MCP-style tool manifests from supplied tool definitions, OpenAPI-like docs, JSON schemas, Markdown docs, or existing function definitions. The actor emits bounded structured rows and buyer-ready reports from supplied or fetched public documentation.

### Inputs

- `toolDefinitions`
- `jsonSchemas`
- `openApiFragments`
- `markdownDocs`
- `readmeTexts`
- `existingFunctionSpecs`
- `manifestFormat`
- `namingConvention`
- `includeExamples`
- `includeSafetyNotes`
- `includeAuthMetadata`
- `strictValidation`
- `timeoutMs`

### Public source provenance

Tool names and capabilities are derived from the public GitHub MCP server at https://github.com/github/github-mcp-server. Inputs are supplied definitions, not claims that a remote MCP server was invoked.

### Billing safety

The actor charges `actor-start` before analysis, charges the primary PPE event before each dataset row, and charges the report event before writing report artifacts. `maxChargeUsd` stops work or output gracefully before the configured cap is exceeded.

# Actor input Schema

## `toolDefinitions` (type: `array`):

Tool Definitions controls MCP Tool Manifest Generator processing for the supplied inputs; keep values conservative for first runs.

## `jsonSchemas` (type: `array`):

Schemas used by MCP Tool Manifest Generator to validate supplied records or responses.

## `openApiFragments` (type: `array`):

Open API Fragments controls MCP Tool Manifest Generator processing for the supplied inputs; keep values conservative for first runs.

## `markdownDocs` (type: `array`):

Optional supplied Markdown documentation pages to convert or inspect.

## `readmeTexts` (type: `array`):

Supplied readme texts to analyze directly.

## `existingFunctionSpecs` (type: `array`):

Existing Function Specs controls MCP Tool Manifest Generator processing for the supplied inputs; keep values conservative for first runs.

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

Manifest Format controls MCP Tool Manifest Generator processing for the supplied inputs; keep values conservative for first runs.

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

Naming Convention controls MCP Tool Manifest Generator processing for the supplied inputs; keep values conservative for first runs.

## `includeExamples` (type: `boolean`):

Include examples in output rows or reports when available.

## `includeSafetyNotes` (type: `boolean`):

Include safety notes in output rows or reports when available.

## `includeAuthMetadata` (type: `boolean`):

Include auth metadata in output rows or reports when available.

## `strictValidation` (type: `boolean`):

Enable stricter validation for MCP Tool Manifest Generator and flag more edge cases as findings.

## `timeoutMs` (type: `number`):

Maximum time in milliseconds allowed for the MCP Tool Manifest Generator operation before it is treated as timed out.

## `maxChargeUsd` (type: `number`):

Maximum estimated PPE charge allowed for the run before the actor stops gracefully.

## Actor input object example

```json
{
  "toolDefinitions": [
    {
      "sourceUrl": "https://github.com/github/github-mcp-server",
      "serverName": "github-mcp-server",
      "name": "get_file_contents",
      "inputSchema": {
        "type": "object",
        "properties": {
          "owner": {
            "type": "string",
            "title": "Owner",
            "description": "Owner input value."
          },
          "repo": {
            "type": "string",
            "title": "Repo",
            "description": "Repo input value."
          },
          "path": {
            "type": "string",
            "title": "Path",
            "description": "Path input value."
          },
          "ref": {
            "type": "string",
            "title": "Ref",
            "description": "Ref input value."
          }
        },
        "required": [
          "owner",
          "repo",
          "path"
        ]
      },
      "outputSchema": {
        "type": "object"
      },
      "auth": {
        "type": "github-token"
      },
      "examples": [
        {
          "owner": "modelcontextprotocol",
          "repo": "servers",
          "path": "README.md"
        }
      ]
    }
  ],
  "jsonSchemas": [],
  "openApiFragments": [],
  "markdownDocs": [],
  "readmeTexts": [],
  "existingFunctionSpecs": [],
  "manifestFormat": "mcp-json",
  "namingConvention": "snake_case",
  "includeExamples": true,
  "includeSafetyNotes": true,
  "includeAuthMetadata": true,
  "strictValidation": true,
  "timeoutMs": 5000,
  "maxChargeUsd": 1
}
```

# 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 = {};

// Run the Actor and wait for it to finish
const run = await client.actor("junipr/mcp-tool-manifest-generator").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 = {}

# Run the Actor and wait for it to finish
run = client.actor("junipr/mcp-tool-manifest-generator").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 '{}' |
apify call junipr/mcp-tool-manifest-generator --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,junipr/mcp-tool-manifest-generator"
        }
    }
}

```

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/eGlThVqPHRfGzsbxO/builds/z2R7NPNAPha5qmVMj/openapi.json