# Use Prompt Verse with your AI

> Connect Claude, ChatGPT or any MCP assistant to Prompt Verse: through Geenius OS or with the app's own MCP address.

Source: https://prompt-verse.geenius-os.tech/docs/use-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.

> [!HONEST]
> The pre-beta is invite-only. You need a Prompt Verse account, or a Geenius OS workspace that has Prompt Verse installed. The in-app run actions are switched off, so everything on this page is about your AI doing the running.

## Way 1: through Geenius OS

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

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

```json title="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

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

### ChatGPT

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

### Other MCP clients and scripts

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

::mcp-config

> [!WARNING]
> Never paste a key into a chat. Use a key only in the configuration of a client that cannot sign in, name each key after what uses it, and revoke it in the app when you stop using that client.

## Your first ask

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

```text title="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`.

::mcp-tools

## 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.