Skip to content
OwnVersion

AI workflows

When the apps are yours,
your AI can use them.

Your analytics, your newsletter and your app all run on your own server, so nothing stands between them and your AI. Connect Claude to OwnVersion once and it can read every one of them, put them together and act.

One connection

Everything you run, through one MCP.

OwnVersion’s MCP gives your AI your servers and apps: health, usage, updates, backups and installs. Apps that come with their own MCP show up inside it, so the same connection reaches their data too.

No code on your side. When you install an app with an MCP, OwnVersion gives it a key and connects it for you.

Workflows

Things your AI can do once your apps are yours

Copy a prompt into Claude, or put it on a schedule. Anything that changes or sends something waits for your OK.

A personal first email for every sign-up

Every hour Analytics Newsletter Your app

Instead of a drip template that sends everyone the same thing three days later, your AI writes each new user a real note about what they came for.

  1. 1 Finds people who signed up since the last run.
  2. 2 Looks up where each one came from and the pages they read in your analytics.
  3. 3 Checks your app for what they set up and where they stopped.
  4. 4 Drafts a one-to-one email with their first step already done, for you to approve or send.

Prompt

Using the ownversion MCP: call get_account, then list_app_tools for my analytics and newsletter apps. For everyone who signed up in the last hour, look up how they found us and what they viewed, check where they got stuck in my app, and draft a short personal email that helps with their next step. Show me the drafts before anything is sent.

Uses the MCP tools of the apps it names.

Learn which emails actually make money

Every Monday Newsletter Analytics

Clicks from your newsletter land in your analytics next to your sales, so your AI can see which sends paid off and write the next one like them.

  1. 1 Pulls last week’s sends and their clicks from your newsletter.
  2. 2 Matches the clicks to sign-ups and revenue in your analytics.
  3. 3 Ranks the emails by what they earned, not just by opens.
  4. 4 Drafts next week’s email in the style of the winners.

Prompt

Using the ownversion MCP, compare last week's newsletter sends with sign-ups and revenue in my analytics app. Tell me which emails earned the most and why you think so, then draft next week's email using what worked. Don't send it.

Uses the MCP tools of the apps it names.

Post about what people are already reading

Every Friday Analytics Social scheduler

Your AI checks which pages are pulling visitors this week and turns them into posts for your own social scheduler.

  1. 1 Finds your top pages and where their visitors came from.
  2. 2 Writes a post for each channel that’s sending traffic.
  3. 3 Puts them in your social app as drafts for you to schedule.

Prompt

Using the ownversion MCP, find my five most-visited pages this week in my analytics app and which sites sent the visitors. Write a post for each, suited to the channel that sent the most traffic, and save them as drafts in my social scheduler app.

Uses the MCP tools of the apps it names.

Bring back people who drifted off

Every week Your app Analytics Newsletter

People who stopped coming back get a note that mentions what they actually used, not a coupon blast.

  1. 1 Finds users who were active and then went quiet.
  2. 2 Looks at what they used most before they left.
  3. 3 Drafts a short, specific note for each, with anything new since they left.

Prompt

Using the ownversion MCP, find users who were active last month but haven't been back in two weeks. For each, look at what they used most and draft a short personal note mentioning it and anything we've shipped since (check list_releases). Show me the list before sending anything.

Uses the MCP tools of the apps it names.

A morning check on everything you run

Every morning OwnVersion

One message each morning: what’s down, what’s filling up, which updates are out and whether last night’s backups worked.

  1. 1 Reads every server’s CPU, memory and disk, and every app’s uptime.
  2. 2 Lists apps with an update waiting and backups that failed.
  3. 3 Flags anything that needs you, with a link to fix it.

Prompt

Using the ownversion MCP, call get_account and get_server for each server. Give me a short morning report: anything down or failing, disks over 80%, apps with updates waiting and any failed backups. Keep it to what needs my attention.

Works with OwnVersion’s own tools.

Update day, done carefully

When you ask OwnVersion

Your AI reads what changed, backs each app up first, updates it and checks it came back healthy.

  1. 1 Reads the release notes for each app with an update.
  2. 2 Backs up the app’s database.
  3. 3 Updates it once you approve, then confirms it’s live and healthy.

Prompt

Using the ownversion MCP, find my apps with update_available. For each, summarise the release notes from list_releases, run back_up_app, then preview update_app and wait for my approval. After it deploys, check get_app and tell me it's healthy.

Works with OwnVersion’s own tools.

Ready for a traffic spike

Every 15 minutes OwnVersion Analytics

When a launch or a viral post sends a wave of visitors, your AI sees the server working hard and lines up a bigger size, with the price, for you to approve.

  1. 1 Watches visitors in your analytics and CPU on the server.
  2. 2 If both climb, finds the next size up and its monthly price.
  3. 3 Asks you before resizing, and tells you when it’s back.

Prompt

Using the ownversion MCP, check current visitors in my analytics app and CPU and memory in get_server. If the server is above 85% while traffic is rising, use list_server_options for that server and preview resize_server to the next size up. Ask me before applying it.

Uses the MCP tools of the apps it names.

Ask for the feature you keep wishing for

When you ask OwnVersion

When you tell your AI something an app should do, it writes the request in your words and sends it to us once you OK it. We reply in your dashboard.

  1. 1 Turns what you said into a clear request.
  2. 2 Shows it to you first.
  3. 3 Sends it, and the reply shows up in your dashboard.

Prompt

Using the ownversion MCP, write up this change I want in one of my apps as a request_change, in my words: [what you want]. Show me the preview before sending it.

Works with OwnVersion’s own tools.

Set it up

Three steps, about two minutes

  1. 01

    Make a token

    In your dashboard, open Settings, then AI connection, and create a token.

  2. 02

    Add OwnVersion to your AI

    Paste one command into Claude Code, or add the server URL to any MCP client that can send a header.

  3. 03

    Run a workflow

    Paste a prompt below, or put it on a schedule so it runs every hour, day or week.

Claude Code

claude mcp add --transport http ownversion https://ownversion.com/mcp --header "Authorization: Bearer YOUR_TOKEN"

Questions

Can my AI change things without asking?

Installs, updates, restarts, new servers, resizes and change requests all come back as a preview first, and only go ahead after you approve that exact preview. Your AI is told to ask before calling any app tool that changes or sends something. Every call shows up in your app’s activity.

Which AI can I use?

Claude Code and any MCP client that can send a header, such as Claude Desktop, Cursor or VS Code. Sign-in for Claude.ai and ChatGPT connectors is coming next.

Where does my data go?

Your apps and their data stay on your own server. When your AI calls an app’s tool, OwnVersion passes the call to that server and hands back the answer, and only the AI you connected sees it.

How do apps get their own MCP?

An app’s maker builds the MCP into the app. When you install one that has it, OwnVersion gives it a key on your server and lists it in your connection, with nothing for you to set up.

Can I turn it off?

Yes. Revoke the token under Settings, then AI connection, and the AI loses access right away.