Upgrade offers

I do find it a bit irritating that not long after you purchase an add on, such as Cms pro it is shortly afterwards discounted by 50%. I get the marketing bit and “this is the way” (Mandalorian style!) but hey ho…

Is this a one-off purchase?

I don’t follow? I just got an email offering me 50% off CMS Pro when I purchased it recently at full price. But I don’t want to make an issue out of it, just a bit irritating!

But I think they will meet you.

But I read somewhere that you only pay for it once and then it is mine. No subscription, etc.

Sorry you miss understand! I bought CMS Pro recently at full price, today I received an email offering me 50% off a CMS Pro licence. I know it a one off purchase that I have already made.

Anyhow, it was just an irritant, not a problem, just thought I would share my thought.

I know it’s annoying, this kind of thing can and does happen with any product. However, we always try to do the right thing for out customers…

If you purchased CMS Pro in the past couple of weeks, drop an email to support and we’ll see what we can do. Please link to this thread in the email so we know what it’s about :smiling_face:

Hi @dan no issue it’s fine but a little irritant. Maybe you could exclude previous purchasers from promos? :flushed_face: don’t fret about it (I’m sure you aren’t) just a thought…

I will buy it now. Before too expensive for me. Keep those offers coming … :clinking_glasses:

I am very tempted to add on…

But already have functioning sites with CMS

Onesoneveryday.com (not being updated - project finished)

WindyTown.com 70 ish plus songs (CMS - finished)

Technitrox.com manual CMS

TrumpetStudio.com full Pro CMS license used a lot… ongoing

Really thinking Tech blog would benefit…

I’m getting a lot of use with TrumpetStudio.com

But don’t want to do:

  • Edit in Typora.
  • Load to Elements.
  • Copy frontmatter.
  • Update metadata.
  • Find or create artwork.
  • Publish.

So have articles sitting there for the tech blog unpublished…

Just don’t know if a tech blog is getting any traction…

Your Thoughts?

Never mind - it’s worth it… - for me-

Bought :slight_smile:

Thank You @ben @dan

Play and install tomorrow….

What’s the difference between Solo and Pro? I am tempted to buy the Pro version even I am still learning CMS and just building my first Blog. I have no outside contributors, plan is to maintain family entries with pictures from my HD, so maybe it’s just a bit too much for now.

Is there a video about the Pro features and what it can do?

Personally I would buy the pro on sale now - it’s a great deal.

Claude is now editing all the articles frontmatter: tags, categories, and seo descriptions.

It really is amazing technology…

Claude is busy or I’d ask for a comparison between the two products you asked about…

Ai help ai help ai help

Just looked it up…

The automation features I just mentioned are NOT available on solo…

I’ll write and article drop it in Claude say “publish this August 6th and update and create all the appropriate frontmatter”

It does all the work…

That’s why you want pro

We’re currently only offering the Pro plan as that was by far the most popular and we wanted to be able to offer the full feature set to all users going forward.

The CMS 2.0 announcement video covers over most of the Pro features. We also have a dedicated video on how to connect Claude (or ChatGPT) to your CMS (this is using the MCP server feature included in Pro).

There’s also a full list of features included in Pro on the CMS website.

If you have any other questions, or are unsure about anything, just let us know :slight_smile:

Thank you for the “push” I needed. I think I’m going to make the purchase because, in the near future, I’ll likely be working on a blog where content needs to be published not only to the website, but also to Substack, Medium, and other social platforms. Maybe, together with Claude, CMS Pro will be must so I can take care easily of the entire publishing workflow.

You’ll be very happy and surprised at the ease of workflow… Very very happy…

@ben I just subscribed to perplexity max and would like to connect it to elements. It already creates custom components for me, but before I buy the CMS Pro license I would need to be sure I can connect it with elements - even at a later stage.

you can connect the CMS directly to any app that supports connections to an MCP server :slight_smile:

@ben for your info, update:

Great news — I was working from stale info. Perplexity already supports custom MCP connectors, and you’re on Max, so you already have access. Let me confirm and walk you through it.
The answer: it’s already live
Perplexity launched Bring Your Own Connector on March 13, 2026 for Pro, Max, and Enterprise subscribers. Since you pay for Max, you can add the Elements CMS MCP server directly to Perplexity right now.[perplexity]
How to add Elements CMS to your Perplexity account
Based on Perplexity’s official help center:[perplexity]

  1. Get the Elements credentials first. In the Elements CMS Online Editor as owner: AI → Connections. Copy the endpoint URL (looks like https:///editor/mcp.php ) and click Create token — give it a name like “Perplexity”, pick the user the assistant should act as, and copy the mcp_… token immediately (it’s shown only once).
  2. Open Perplexity settings. Go to perplexity.ai/account/connectors or click your profile avatar → Connectors.
  3. Add a custom connector. Click + Custom connector in the top-right, then select Remote.
  4. Fill in the form:
    • Name: Elements CMS (or your site name)
    • MCP Server URL: https:///editor/mcp.php
    • Authentication: Choose API Key, then paste your mcp_… token
    • Transport: Streamable HTTP (usually auto-detected; try SSE as fallback if it fails)
    • Optional: description, icon
  5. Check the risk acknowledgement and click Add.
  6. Click the connector card to complete authentication.
  7. Enable it in a thread under Sources, then ask “What tools do you have access to?” — you should see content_list_items , content_read_item , resources_upload_request , etc.
    Two things to watch for
    • Auth method mismatch: Elements’ docs show the preferred auth as Authorization: Bearer mcp_… . Perplexity’s “API Key” option should send exactly that header. If it doesn’t work, try the fallback: use the URL form https:///editor/mcp.php?token=mcp_… with Authentication: None (Realmac docs).
    • Comet browser caveat: Custom connectors work on Perplexity web and Mac/Windows desktop apps, but some current Comet builds may not surface them — set it up from the web/desktop and your account settings will carry over.[tempreon]

@ben Anything I need to be aware of regarding the news above, please?

Thank you very much.