Use Prompt Verse with your AI

Prompt Verse runs no model. Your own AI, Claude, ChatGPT, Grok or any assistant that supports MCP, connects to your library, finds a prompt, asks for it rendered with its variables filled, and runs it on its own subscription. This page shows the two ways to connect and what your AI can do once it is connected.

Way 1: through Geenius OS#

If you use Geenius OS, one connection gives your AI all your apps.

Install Prompt Verse in your Geenius OS workspace.
Add the Geenius OS connector to your AI, using the address that Geenius OS shows you, and approve it once.
Your AI now has a tool called geenius_promptverse. It takes a tool (the area, such as prompts), an action (the verb) and args.

A call through Geenius OS

{ "tool": "prompts", "action": "search", "args": { "q": "support reply" } }

Every call acts in the Prompt Verse workspace of your Geenius OS workspace, after a plan check. If the workspace has no Prompt Verse plan, the call answers with PLAN_REQUIRED.

Way 2: Prompt Verse’s own address#

On its own, Prompt Verse has an MCP address that ends in /mcp. You find yours in the app under Connect, with a button to copy it.

Claude#

In Claude, open Settings, then Connectors, then Add custom connector.
Paste your Prompt Verse address and save.
Sign in with your Prompt Verse account when Claude asks.

ChatGPT#

In ChatGPT, open Settings, then Connectors, and add a remote MCP server.
Paste your Prompt Verse address.
Sign in with your Prompt Verse account when it asks.

Other MCP clients and scripts#

In the app, open Connect and make a key under Keys. It is shown once, so copy it then.
Point your client at your Prompt Verse address.
Send the key as a bearer token.

MCP client configuration

{
  "mcpServers": {
    "prompt-verse": {
      "url": "https://<your Prompt Verse address>/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Your first ask#

Paste this to your AI, with your own topic and input:

A first ask

Use Prompt Verse. Find my prompts about <topic> (prompts, action search), open the best one (prompts, action get), answer it for <my input>, and suggest one improvement I can save (prompts, action update).

For a prompt with variables, ask for the rendered text: prompts with action render, the prompt’s id, a format such as messages, and a variables object. The answer lists any variable you left out.

The tools#

Your AI sees a short list: one entry per area, with the detail on request. Ask for the actions of an area with action: "help", and for the exact arguments of one action with action: "help" and of.

Tool	What it is for	Actions
`prompts`	Prompts, responses and contexts of the workspace.	`create` `get` `list` `render` `run` `search` `share` `update`
`versions`	Git-shaped versioning of a prompt, workflow or agent.	`commit` `commits` `branch` `branches` `checkout` `current` `merge` `tag` `tags`
`evals`	Cases plus a scoring method, checked against a prompt.	`create` `get` `list` `run` `runs`
`agents`	Agents you own.	`create` `get` `list` `run`
`workflows`	Workflows you own.	`create` `get` `list` `update` `run`
`collections`	Named shelves of assets.	`create` `list` `get` `add` `remove` `update` `delete`
`library`	Pieces, skills, MCP tools and models.	`pieces` `piece` `skills` `skill` `create_skill` `tools` `create_tool` `call_tool` `models`
`runs`	Run history.	`list` `workflow`
`market`	The marketplace.	`browse` `read` `install` `buy` `publish` `withdraw` `try`

What your AI cannot do yet#

The run actions of prompts, agents and workflows, evals run and market try are listed but refuse with AI_DISABLED in the pre-beta. The error tells your AI to call prompts render and to answer the text itself, which is the intended way. To test a prompt, your AI can read the saved cases with evals get, run the prompt and score the answers in the conversation.