# Apify Actor to ChatGPT App Packager (`wintry_nutmeg/apify-chatgpt-app-packager`) Actor

Generate a deployable MCP bridge and validated ChatGPT/Codex plugin package from any public Apify Actor, including tests and submission assets.

- **URL**: https://apify.com/wintry\_nutmeg/apify-chatgpt-app-packager.md
- **Developed by:** [Dries Vd](https://apify.com/wintry_nutmeg) (community)
- **Categories:** Developer tools, AI, MCP servers
- **Stats:** 1 total users, 0 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$250.00 / 1,000 generated chatgpt app packages

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/actors/running/actors-in-store.md#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

## Apify Actor to ChatGPT App Packager

Turn a public Apify Actor into a deployable remote MCP bridge and a ChatGPT/Codex plugin package. The Actor reads public Store metadata and the latest public input schema, converts the input contract into Zod, and creates a ZIP containing:

- a Node.js Streamable HTTP MCP server;
- a focused MCP tool with accurate safety annotations;
- `.codex-plugin/plugin.json`, `.app.json`, and `.mcp.json`;
- a companion skill and starter prompts;
- Docker deployment files;
- positive and negative test cases;
- an OpenAI submission checklist.

### Important boundary

This Actor creates the code and review package; it does not impersonate the publisher, verify a domain, or bypass OpenAI review. A public submission still needs a live HTTPS `/mcp` endpoint, a verified publisher identity, correct legal/support URLs, a registered connection ID, retained test evidence, and approval through the OpenAI Platform.

The generated MCP tool starts an external Actor run, so it is marked `readOnlyHint: false`, `openWorldHint: true`, and `destructiveHint: false`. The deployer must store `APIFY_TOKEN` as a server-side secret and should use the narrowest practical token scope.

When the Store listing uses pay-per-event pricing, one successful complete ZIP emits exactly one `generated-package` event. Failed packages do not emit that event.

# Actor input Schema

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

Actor in username/name format. Its public schemas and Store metadata are used to generate the package.

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

Optional kebab-case name. Defaults to the Actor name.

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

Optional user-facing plugin name. Defaults to the Actor title.

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

Must match the verified identity used for a public OpenAI submission.

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

HTTPS origin where the generated MCP bridge will be deployed. A placeholder is allowed while packaging.

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

Public HTTPS product or company website for listing metadata.

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

Public HTTPS support page required before submission.

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

Public HTTPS privacy policy required before submission.

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

Public HTTPS terms page required before submission.

## `timeoutSeconds` (type: `integer`):

Timeout compiled into the MCP bridge for target Actor calls.

## Actor input object example

```json
{
  "actorId": "wintry_nutmeg/agent-revenue-auditor",
  "developerName": "Agent Commerce Labs",
  "publicBaseUrl": "https://your-domain.example",
  "websiteUrl": "https://your-domain.example",
  "supportUrl": "https://your-domain.example/support",
  "privacyPolicyUrl": "https://your-domain.example/privacy",
  "termsUrl": "https://your-domain.example/terms",
  "timeoutSeconds": 180
}
```

# Actor output Schema

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

Generated names, metadata, deployment steps, tests, and submission gaps.

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

Deployable MCP bridge and plugin bundle.

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

Machine-readable path/content collection.

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

One record per automated validation or remaining manual requirement.

# 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("wintry_nutmeg/apify-chatgpt-app-packager").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("wintry_nutmeg/apify-chatgpt-app-packager").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 wintry_nutmeg/apify-chatgpt-app-packager --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,wintry_nutmeg/apify-chatgpt-app-packager"
        }
    }
}

```

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/9ywLeMq4KbRBundDK/builds/8C84arfO7EH1kgwcg/openapi.json