Skip to content
FeedX
FeedX journal

How to Use ChatGPT with FeedX MCP: Create Images, Content & Schedules

Learn how to connect ChatGPT to FeedX MCP, create images and content from products or blog articles, research keywords, and schedule reviewed posts.

FeedX editorial
How to Use ChatGPT with FeedX MCP: Create Images, Content & Schedules

ChatGPT connected to FeedX via MCP turns a conversation into a controlled content workflow: retrieve current product information, develop ideas and images, save a draft for review, and only then schedule or publish. FeedX does not turn one prompt into a published post. You still choose the product, media, destination accounts, time, and final action.

This guide is for store owners and marketers who want to use ChatGPT and FeedX to create images from a description, turn a product or blog article into social content, research keywords for an article, and add approved work to a publishing schedule. ChatGPT labels and menus can change by plan and workspace policy, so keep the FeedX connection guide for ChatGPT open while you set up.

The right workflow: context, creative work, review, then delivery

ChatGPT is where you think and write; FeedX is the connection to your workspace, catalog, media, drafts, and publishing schedule. A reliable workflow has four parts:

  1. Set the context: choose the right workspace, brand, product, and social account.
  2. Create options: request distinct writing angles, visual directions, or new images with clear boundaries.
  3. Review the exact version: check claims, media, caption, CTA, destination accounts, and time.
  4. Deliver: save a draft, schedule it, or publish the unchanged reviewed version.

Choosing a concept, generating an image, or saving a draft is not publishing. If you change the caption, image, product, account, or time, treat it as a new version and review it again.

What to have ready

  • A FeedX account with access to the workspace you want to use.
  • A ChatGPT account that can add a custom connector. Your plan or workspace administrator may control this permission.
  • Social accounts connected in FeedX if you want to schedule or publish. You can still explore a workspace before connecting a social destination.
  • Product information, a brief, research materials, or media that you have the right to use.

Never paste a FeedX password, Shopify password, social token, Client ID, or Client Secret into chat. Sign in only on FeedX's OAuth page. When a Client ID or Client Secret field is optional, leave it empty; FeedX handles the connector's OAuth configuration.

How to connect FeedX to ChatGPT

Open ChatGPT on the web while signed in. From your account menu, go to Settings, then Security and login. Turn on Developer mode if your account or administrator allows it, and keep Enforce CSP in developer mode enabled. Next, open ChatGPT's Plugins page, select the plus button or Create app, and create a new connection.

Use these values in the form:

  • Name: FeedX
  • Description: Plan social content with FeedX.
  • Connection: Server URL
  • Server URL: https://mcp.feedx.app/mcp
  • Authentication: OAuth

Read the custom-connector notice, confirm it only if you trust FeedX, and select Create. A FeedX sign-in window opens; complete sign-in and approve access there. Return to a new ChatGPT conversation, open the plus menu beside the message box, and select FeedX from your installed plugins.

FeedX uses MCP, short for Model Context Protocol, so ChatGPT can call tools approved for your workspace. OpenAI notes that write or change actions can require confirmation and that full MCP capability depends on your ChatGPT plan and organization policy. Check OpenAI's current Developer mode and MCP apps guide for availability details.

Start a chat with the right context

Start with a read-only request. It confirms that you are in the right workspace before you create anything:

Use FeedX. Show my available workspaces, confirm the workspace we are using, and explain what I can do there. Do not create, schedule, or publish anything yet.

If you have several workspaces or brands, use their human-readable names. Do not ask ChatGPT to guess from a domain. When you are ready to work, name both the brand and the destination:

In [workspace name], use [brand name]. Show my connected social accounts by name and platform. Check which accounts can receive an image post. Do not create content yet.

FeedX checks compatibility by format. An account that can receive an image post does not automatically support a Reel, Story, or text post. Check before investing time in a format.

Use case 1: create a new image from a description in ChatGPT

When ChatGPT has image generation available and quota remaining, develop the image in chat first. You can review the actual result instead of approving a vague description. State the audience, framing, lighting, elements to preserve, and elements to avoid.

Create a vertical 4:5 image for an Instagram post about [brief]. Style: [style]. Subject: [subject]. Lighting: [lighting]. Palette: [colors]. Do not include text, logos, watermarks, discount claims, or brand details I have not provided. Show me the actual image first; do not import it into FeedX or create a post yet.

After you choose a result, use a separate follow-up so the exact approved file is retained:

I approve this exact image. Import that file into FeedX, create two caption options for [account name] from this brief: [brief], and save them for review. Do not schedule or publish.

Importing an approved image does not recreate it and does not publish anything. If ChatGPT cannot hand over the original file, ask FeedX for an upload link and upload that original file. Do not use a filename, screenshot, or viewer-page link in place of the source file.

FeedX can also be an image-generation fallback when native ChatGPT image generation is unavailable, quota-limited, or when you explicitly choose FeedX. Before it generates anything, ask for the exact number of images and the credit or cost impact, then approve that cost separately. Approving generation cost is not approval to publish a post.

Use case 2: create content and an image from a current product

This is especially useful for stores with a catalog. Start with an exact product link or name so FeedX can retrieve the current snapshot. It reduces the risk of writing from an old price, availability status, variant, or image.

Find the exact product at [product URL] in this FeedX workspace. Summarize its name, price, availability, variants, link, and supported claims. If there is no exact match, stop; do not substitute a similar product.

Once you have confirmed the facts, request genuinely distinct creative directions:

Use the exact product we just confirmed to propose three image-post concepts for [account name]: one practical-benefit angle, one everyday-use angle, and one question-led introduction. Use current facts only. Describe the visual for each option, identify unsupported claims that must not be used, and save the options for review.

Choose one concept before asking ChatGPT to create a visual. If the image needs to preserve the product packaging, label, or logo, say so explicitly. Do not ask AI to infer materials, certifications, promotions, performance, or customer feedback from a product image.

Before you save a draft, read the caption, CTA, and hashtags as one complete post. They share the destination's final text limit; each part can fit on its own while the combined post does not.

Use case 3: turn a blog article or URL into a visual and social posts

A blog article can be a useful source of ideas when you have the right to use it, but a URL alone does not prove every claim it contains. There are two safe paths:

  1. In ChatGPT: paste an approved excerpt or provide a public URL, and state which facts are allowed. Ask ChatGPT to summarize first, mark uncertainty, and only then write captions or a visual direction.
  2. In the FeedX web workspace: use Website page to paste a public product page, blog article, or landing page. FeedX can read page details and find reusable images; you still preview the page and select media before creating a campaign.

Use this prompt for a blog article that has been approved as a source:

Use this blog article as authorized source material: [URL or excerpt]. First, summarize no more than five supported facts, the audience, one core message, and any unverified details. After I confirm the summary, propose three visual concepts with no text in the image and two caption options for [account name]. Do not use long verbatim quotations or copy the article.

When the summary is correct, choose one visual direction and follow the image-generation and import workflow above. If you use existing page images, choose only images FeedX has verified as belonging to the page preview; do not pull in unrelated URLs or media that you are not entitled to use.

Use case 4: research keywords and create a blog article in FeedX

A useful SEO article starts with intent, not keyword stuffing. For this topic, the primary keyword is ChatGPT MCP FeedX. Supporting terms can include “connect ChatGPT to FeedX,” “create ChatGPT images for social media,” “schedule social media posts with AI,” “create content from Shopify products,” and “create Shopify blog articles with AI.” This is an intent-led keyword map; do not invent search volume or keyword difficulty without data from your keyword tool.

Split research into two steps. First, create a brief and evidence sheet:

Research a practical guide for the primary keyword [keyword]. Identify search intent, audience, related questions, a six-section H2 outline, natural supporting keywords, claims that need sources, and a list of primary-source URLs. Do not write the full article. Do not invent statistics, quotations, or case studies. Attach each fact to a source or mark it unverified.

Review the brief before writing: does the keyword match the reader's need; are the sources primary; which claims need to be removed; and what CTA fits the article? Then create the proposal:

For the [blog name] blog, write a practical English guide about [topic] for [audience]. Use the primary keyword [keyword] naturally in the title, introduction, and where relevant. Use supporting keywords without repetition. Create a title, excerpt, meta description, six-section outline, complete article, and FAQ. Use only facts in the approved brief, link to suitable primary sources, and save this as a FeedX proposal for review. Do not send it to Shopify yet.

A FeedX blog proposal is neither a Shopify draft nor a live article. For a featured image, create or choose one approved image, import it into FeedX, attach it to the proposal, and review the article again. Only then choose one clear delivery action:

Deliver this unchanged reviewed article to the [blog name] Shopify blog as a Shopify draft. Keep the approved title, excerpt, body, and featured image.

Publish this unchanged reviewed article live on the [blog name] Shopify blog, including its approved featured image.

Live publication requires the appropriate permission in the Shopify workspace. If you change the title, body, image, or destination after review, create the new version and review it again before delivery.

Use case 5: schedule one post or a week of content

First, save the chosen content as a FeedX draft. Then ask ChatGPT to read back the current version: caption, media, accounts, format, product facts, and delivery time. For one post, always use a precise date, time, and IANA timezone instead of “tomorrow morning.”

Schedule this unchanged reviewed draft to [exact account names] on 2026-10-12 at 09:00 in Asia/Ho_Chi_Minh. Use its reviewed copy and media and skip the optional preview. Before scheduling, summarize the current draft, accounts, date, time, and timezone so I can confirm them.

To prepare a content week, ask for a review-only calendar first:

Plan seven distinct product posts for seven days starting [date] in [timezone] for [account names]. Prepare and review every post, media item, format, destination, and publish time. Do not schedule anything. Then show the complete plan as a readable calendar summary.

When the content, media, accounts, dates, and times are all correct, confirm with a separate instruction:

I approve this unchanged publishing week with the posts, media, account names, dates, times, and timezone just shown. Schedule the full week.

FeedX validates each item in a publishing week independently, so some items can be accepted while another needs attention. An accepted schedule means FeedX has accepted the request; check status afterwards to distinguish pending, successful, failed, or uncertain delivery for every account.

More useful use cases to try

  • Product-free content: create two LinkedIn text posts from a brief without adding product claims.
  • Account-specific copy: keep one idea but use a warm Instagram caption and a more professional LinkedIn version.
  • Draft translation: retain names, prices, facts, and media, but treat the translation as a new revision.
  • Claim review: remove discounts, scarcity, guarantees, or results that are unsupported by the catalog or brief.
  • Existing media: search the FeedX Media Library for a real asset before creating another image.
  • Schedule and delivery review: read campaigns, scheduled posts, and the calendar for a date range; never retry an uncertain result before checking its current status.

FeedX's AI use-case library includes copy-ready prompts for these workflows, including product discovery, media, review, blog writing, and weekly scheduling.

Checklist before you confirm a schedule or publication

  • Is this the correct workspace and brand?
  • Are the product, facts, price, and availability current?
  • Is this the exact approved image or video, in the correct format and with the right to use it?
  • Have you read the caption, CTA, hashtags, and supported fields as one complete post?
  • Are the destination social accounts named correctly, with no unplanned accounts included?
  • Are the date, time, timezone, action, and blog destination explicit?
  • Has anything changed since the final review?

If any answer is unclear, stop at the draft and resolve it first. The effective use of ChatGPT and FeedX is not about automating every decision. It shortens the creative and organizational work while you keep control of consequential public actions.

Frequently asked questions

Does connecting FeedX publish a post automatically?

No. Connecting gives the workflow access to FeedX. A concept, image generation, media import, or draft is not a publication result. You need to request and confirm a specific schedule or publish action.

Can I use an image created by ChatGPT?

Yes, when ChatGPT has image generation available and you approve the exact result. Import that exact file into FeedX before attaching it to a draft. If the original file cannot be handed over, use a FeedX upload link with the original media.

Can FeedX infer product facts from an image?

Do not rely on that. Let FeedX retrieve current product facts from the catalog and use only supported claims. A product image is supporting visual evidence, not a source for specifications, certifications, or promises.

Can I publish a blog article from ChatGPT?

With an eligible Shopify workspace and the right permission, you can save a proposal, deliver a Shopify draft, or request live publication. Keep those steps separate, use a reviewed featured image, and only publish the unchanged version after final review.

What if I cannot see FeedX in ChatGPT?

Open a new conversation, enable FeedX in the tools or plugins menu, check that OAuth has not expired, and make sure the URL includes /mcp. If you still cannot add a custom connector, check your ChatGPT plan or ask your workspace administrator.

Next step: open a new ChatGPT conversation with FeedX enabled, send the read-only workspace prompt, and try one image-post concept for a specific product. A small, carefully reviewed workflow is the best foundation for a larger content calendar.