How to Configure Plugin Categories in OpenAI Plugins

OpenAI plugin categories are configured by setting the interface.category property in each plugin's plugin.json manifest file located at plugins/<plugin-name>/.codex-plugin/plugin.json.

The openai/plugins repository defines how plugins appear in the OpenAI Plugin Marketplace through structured manifest files. Properly configuring the category ensures your plugin surfaces in the correct browse sections and reaches users searching for specific functionality.

Where Plugin Categories Are Defined

In the openai/plugins repository, category metadata resides in the plugin manifest. The marketplace infrastructure reads this file during the build and indexing process to determine where the plugin appears in the marketplace UI and filtering systems.

The interface.category Property

The category value is stored in the interface.category field of the JSON manifest. This string property sits inside the top-level interface object and accepts values that the marketplace uses for organization and discoverability.

Standard Category Taxonomy

While the category field accepts free-form strings, the repository follows a shared taxonomy to maintain marketplace organization. Standard values include:

• Developer Tools
• Communication
• Finance
• Productivity
• Data & Analytics
• Creativity
• Education & Research
• Business & Operations
• Travel

Using these established values ensures your plugin appears alongside related tools rather than isolated in uncategorized sections.

Step-by-Step Configuration

Follow these steps to set or update a plugin's category in the openai/plugins repository:

1. Open the plugin's manifest file at plugins/<plugin-name>/.codex-plugin/plugin.json.
2. Locate the interface object, which contains UI metadata such as displayName and shortDescription.
3. Add or modify the "category" property with your desired value, such as "Developer Tools".
4. Commit the changes to the repository. The marketplace will reflect the new category during the next indexing cycle.

Example Configuration

The MagicPath plugin demonstrates proper category configuration in its manifest file at plugins/magicpath/.codex-plugin/plugin.json:

{
  "name": "magicpath",
  "version": "0.1.1",
  "description": "Use MagicPath to find, inspect, install, create, and edit UI components from Codex.",
  "interface": {
    "displayName": "MagicPath",
    "shortDescription": "Find, install, and author MagicPath UI components from Codex",
    "category": "Developer Tools",
    "capabilities": ["Interactive", "Read", "Write"],
    "websiteURL": "https://www.magicpath.ai/",
    "privacyPolicyURL": "https://www.magicpath.ai/privacy",
    "termsOfServiceURL": "https://www.magicpath.ai/terms"
  }
}

The category field sits alongside other interface metadata, defining where users will find this tool when browsing the Developer Tools section.

Best Practices for Category Selection

• Match primary functionality: Choose the category that describes your plugin's main use case rather than secondary features.
• Use standard taxonomy: Stick to the established category strings to ensure proper grouping with similar plugins.
• Avoid vague terms: Specific categories like "Developer Tools" improve discoverability more than generic alternatives like "Utilities".

Summary

• Plugin categories are defined in the interface.category field of plugins/<plugin-name>/.codex-plugin/plugin.json.
• The openai/plugins repository uses standard taxonomy strings like "Developer Tools", "Finance", and "Productivity" to organize the marketplace.
• Changes to the category field are picked up during the next indexing cycle after commit.
• Consistent categorization is critical for plugin discoverability in the OpenAI Plugin Marketplace.

Frequently Asked Questions

What file contains the plugin category?

The category is defined in the plugin.json manifest file located at plugins/<plugin-name>/.codex-plugin/plugin.json within the openai/plugins repository. Specifically, it is the interface.category property inside this JSON file.

Can I use custom categories?

While the interface.category field accepts any string value, the marketplace infrastructure expects standard taxonomy values such as "Developer Tools" or "Communication". Using custom categories may result in your plugin appearing in an uncategorized section or being filtered out of standard browsing views.

How long until category changes appear in the marketplace?

Category updates are reflected during the next indexing cycle after you commit changes to the repository. This process is handled automatically by the OpenAI Plugin infrastructure when it reads the updated manifest files.

What happens if I don't specify a category?

Omitting the category property may result in your plugin being excluded from category-based filtering in the marketplace UI, significantly reducing discoverability. The field is optional in the schema but highly recommended for proper marketplace placement.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}