Blog
Read the product from your editor
MCP lets Cursor, Claude, ChatGPT, and other clients read your products, performance, AI visibility, and drafts. The connection cannot post or edit them.
The useful question during a release is rarely “write me a post.” It is “which query showed up this month,” “what did the brief say to fix,” or “what does the Dev.to draft already say.” Those answers live in ProductPost 360. MCP lets the editor you are already in read them, on the account you approve.
The connection is read-only. It can look at the product. It cannot create a draft, rewrite one, post it, or delete it. You still copy, and you still paste from your own account. Setup for each client is on the public MCP page.
What the client can see
After you sign in with the same Google or GitHub account you use for the product, and you allow read access, the client can see:
- Product names, and the channels turned on for each one.
- Search performance, including the stored summary, the recommendations, and the opportunities.
- AI visibility: the prompts, the mention picture, the cited domains.
- Campaigns, and the draft written for each channel you have already generated.
A release afternoon is the case these reads are for. You are in the diff, the changelog entry is already written, and you want the stored brief or the existing draft in the same window. Ask for the product by name. The client answers from the account you connected, which matters when the workspace holds more than one product.
That is enough to work without a second tab. It is the same data as the pages in the app, scoped to the account you approved, and it needs an active plan or trial on that account.
Three questions worth asking beside the diff
The point of the connection is the question you would otherwise context-switch to answer.
- You are about to ship a release. Ask which sources are already in the queue, and which channels are on for this product. If the release is a one-host bugfix, the draft you want is the room that host already uses. The channel list will tell you whether that room is even turned on.
- You changed a title because the brief recommended it. Ask what the recommendation said, and which query it named, before you rewrite a second page. The brief is stored. The client can read the stored note. It should not invent a new one.
- You want the Dev.to version of a post you published this morning. Ask for that campaign’s draft. Read it in the editor if that helps you edit. Copy from the app when you are ready to paste. Regenerating, remixing, and marking it posted stay in the product.
A fourth habit is worth naming so it does not creep in. Do not ask the client to post the draft “since it can see it.” It cannot post. If a client offers to, it is improvising with your accounts, which is the outcome the read-only line is there to prevent.
How you connect it
Each client takes the same server URL, https://productpost360.com/mcp. Leave client id, client secret, and extra headers empty. The client registers itself, then opens a browser. You confirm the account and allow read access.
Cursor, Claude, Windsurf, Codex, and ChatGPT each have a slightly different settings screen, and the public page has the exact config for each. Add it for every project, or for one repo, the same way you would add any other remote MCP server. A teammate connects their own account. They see the products that account can open.
Use it on the days you are already in the editor and the question is about a number or a draft you stored. Use the app on the days you are choosing rooms, connecting Search Console, or pasting. The two stay in that order on purpose: the client can remind you what the product knows, and the product is where anything gets published, by you.