Max Igoshev.

Plugins

I build plugins for ChatGPT and Claude

Your service, working inside the assistant your customer already has open. I design it, build it, submit it to the directories and keep it running after launch.

A plugin puts your service inside the assistant. The customer does not open your site, log in or learn your interface. They ask in the chat they already had open, and the assistant calls your service and answers with your data.

For a business that changes where the work starts. People who would never have found your product meet it at the moment they need it, inside a tool they already trust.

The build itself is one server that both assistants talk to. What differs is the packaging: how it is submitted, how it is described, and what a reviewer needs to see.

What I do

Four things, and you can start at any of them.

  • A plugin from scratch

    You describe what the plugin should do for your customer. I design the set of actions, build it and take it to a working state.

  • Your service as a plugin

    If you already have a product with an API, it becomes a plugin without a rewrite. The service stays where it is, the assistant calls it.

  • Publication in the directories

    Submission, review metadata, descriptions and screenshots, country settings, answers to the reviewers until it is listed.

  • Promotion after launch

    A listing is a start, not a result. I work on the description, the examples people see first, and the wording that gets the plugin picked.

Two platforms, one build

Both run on the Model Context Protocol, so a single server serves them both. That is the part most people pay for twice.

  • ChatGPT

    Plugins are built with the Apps SDK and listed in the Plugin Directory, shared by ChatGPT and Codex. Submission goes through the OpenAI developer platform with review.

  • Claude

    The same server connects to Claude as a connector. Anthropic created the Model Context Protocol, and Claude speaks it natively.

Built and running

The first one is my own platform. Its agents now answer inside both assistants.

How the work goes

Four steps. You see the plugin working before it goes to review.

  1. Task review

    We work out what your service does and which of it belongs inside a chat.

  2. Actions and data

    I design the set of actions the assistant can call, and how it reaches your data.

  3. Build and test

    I build the server and test it in both assistants on real requests with you.

  4. Submission and support

    I prepare the listing, answer the review, and stay on the plugin after it goes live.

Tell me about your service

Write what it does and who uses it. I will tell you what it looks like as a plugin.

Request a plugin

← Home