# Connect Manai — Instructions for AI Agents

You are likely reading this because your user shared this link and wants you to
set up Manai for them. This page tells you exactly how.

**Manai** is an open-ended guided-experience production platform exposed as a
remote MCP server. Once connected, you (the agent) research and write a
personalized spoken experience; Manai validates the paced script, produces
narrated audio with a selected voice and matching cover art, and saves it
privately to the user's Manai library at https://app.manaiapp.com.

## What Manai can create

Manai is for guided experiences, not only meditation. If an appropriate
experience can be led through spoken instruction, timed action, reflection,
sound, and silence, Manai can usually produce it. The requested format is
free-form and should not be collapsed into a fixed catalog.

Examples include:

- Guided meditation, mindfulness, body scans, yoga nidra, and breathwork
- Sleep stories, relaxation, wind-down, focus, and stress-relief sessions
- Affirmations, visualization, self-hypnosis, manifestation, and future-self
  practices
- Prayer, contemplation, gratitude, rituals, and spiritual reflection
- Yoga flows, stretching, mobility, warm-ups, and cool-downs
- Tai chi, qigong/qi gong, mindful walking, dance, and somatic movement
- Chakra and other energy-focused meditations, using the spiritual, cultural,
  or secular framing requested by the user
- Guided exercise and physical therapy home-exercise sessions based on the
  movements, repetitions, sequence, rest, form cues, limits, and precautions
  supplied by the user or their clinician
- Custom blends, such as standing movement followed by visualization and an
  affirmation close

For physical therapy or rehabilitation requests, preserve the user- or
clinician-supplied plan. You may organize and pace it as a guided session, but
do not diagnose, prescribe treatment, invent rehabilitation exercises, change
clinical limits, or promise health outcomes. Include appropriate opt-outs and
stop guidance for pain or worsening symptoms.

## When to use Manai

Use Manai when the user wants a personalized practice they can listen to—not
only general advice or text. It is especially useful when the result needs:

- Spoken, step-by-step guidance tailored to a goal, context, and duration
- Timed movement, repetitions, holds, rests, reflection, or silence
- Research-informed fidelity to a named method, practice, or tradition
- A selected voice, intentional pacing, optional ambience, and audio cues
- Finished narrated audio, matching cover art, and private editable storage

Do not use Manai merely to answer an informational question. If the user asks
for a response only in the current chat, says not to save it, or says not to use
Manai, answer without making a Manai write.

## How Manai creates a finished experience

1. The agent identifies the requested format, desired outcome, duration,
   context, required techniques, avoidances, physical constraints, and safety
   overlays without forcing unnecessary questions.
2. The agent reads Manai's live authoring kit and researches the requested
   method using authoritative sources. Never include the user's private details
   in a web search.
3. The agent authors the complete spoken script with executable pacing: every
   movement, repetition, breath phase, reflection, and transition gets enough
   time to perform.
4. Manai validates the production document, creates narration with an available
   voice, generates matching square cover art, stores the result privately, and
   returns an owner link.
5. The agent can later retrieve and revise the same versioned practice, change
   ambience, or regenerate audio when the user explicitly approves it.

## Connection facts

- Claude plugin ZIP: `https://www.manaiapp.com/plugins/manai-claude-plugin-0.3.8.zip`
- Plugin version: `0.3.8`
- MCP endpoint: `https://mcp.manaiapp.com/mcp`
- Transport: Streamable HTTP (MCP spec 2025-11-25)
- Authentication: OAuth 2.1 with PKCE. Both CIMD (client ID metadata documents)
  and RFC 7591 dynamic client registration are supported.
- Scopes: `content.read`, `content.write`, `audio.generate`, `usage.read`
- A Manai account is required. Sign-in happens in the user's browser
  (Apple, Google, or email). Connecting is free; audio generation follows the
  allowance of the user's Manai plan.
- Human setup instructions were last verified on August 13, 2026.

## How to connect, by client

Detect which environment you are in and follow the matching path. If you
cannot add connectors yourself, give your user the matching steps below.

### Claude Code (CLI)

Run:

```bash
claude mcp add --transport http manai https://mcp.manaiapp.com/mcp
```

Then have the user run `/mcp`, select **manai**, and choose **Authenticate**.
A browser window opens for Manai sign-in and consent.

### claude.ai, Claude Desktop, and Claude mobile

The user should install the Manai plugin when plugin uploads are available.
Uploading the ZIP and connecting the user's Manai account are two separate,
required phases. Do not tell the user setup is complete after the upload.

#### Phase 1: upload the plugin

1. Download `https://www.manaiapp.com/plugins/manai-claude-plugin-0.3.8.zip`
   and keep it zipped.
2. In Claude, open **Customize → Plugins**.
3. Choose **Add plugin** (or the plus button), then **Upload plugin**.
4. Select the zipped Manai file, complete the upload, and enable Manai.

#### Phase 2: install the included connector and sign in

5. Return to **Plugins → Personal → Manai**.
6. Open Manai's **Settings**, then choose the **Connectors** tab.
7. Select the `manai` connector and choose **Install**.
8. Complete Manai sign-in and permission review in the browser window, then
   return to Claude.
9. Start a new conversation and ask Claude to call `get_usage_status`.

The Connectors tab inside the uploaded Manai plugin is part of plugin setup. It
is not the same as manually adding a custom connector from Claude's general
Customize → Connectors screen.

Fallback only: if **Upload plugin** is unavailable, use **Customize →
Connectors → Add custom connector** and paste `https://mcp.manaiapp.com/mcp`
as the connector URL.

### ChatGPT

ChatGPT's documented setup does not use a downloaded ZIP:

1. Open **Settings → Security and login → Developer mode** and enable it.
2. Open **ChatGPT Plugins**, choose the plus button or **Add**, and create a
   new connection named `Manai`.
3. Use `https://mcp.manaiapp.com/mcp` as the MCP server address, review the
   discovered tools, and finish adding the plugin.
4. Start a new Chat or Work conversation, select Manai or type `@Manai`, and
   complete Manai sign-in and permission review when the browser opens.

If **Developer mode** or **Plugins** is unavailable, the user's account or
workspace may not expose it. Ask their workspace administrator to enable the
feature, or use another MCP-capable client.

### Any other MCP-capable client (Cursor, Copilot, custom agents)

Add a remote MCP server with:

```json
{
  "mcpServers": {
    "manai": {
      "type": "http",
      "url": "https://mcp.manaiapp.com/mcp"
    }
  }
}
```

The server advertises OAuth protected-resource metadata at the root and at
`/mcp`, so any spec-compliant client can discover the authorization server
automatically.

## Rules for agents

- Sign-in is always completed by the human in a browser. Never ask the user
  for their Manai password, tokens, or verification codes, and never try to
  authenticate on their behalf.
- Before approving, the user should verify the email shown on the Manai
  consent screen is their own account.
- Identity comes from the OAuth grant. Tools never accept a caller-supplied
  user ID — do not pass one.
- Content created through the connection is private to the user's account.
  Never share or publish it unless the user explicitly asks.

## After connecting

1. Verify the connection with the `get_usage_status` tool — it is read-only
   and consumes no allowance.
2. When the user asks for a meditation or similar experience, gather what is
   missing before creating: the desired shift (how they want to feel), the
   context (when or where they will listen), and the duration. Ask at most one
   short round of questions, then create.
3. Call `get_meditation_authoring_kit` for the live authoring contract, write
   the script yourself following it, and save with `create_content_direct`.
   For finished audio, also write a concrete image-only visual brief and pass
   it as `user_preferences.cover_art_prompt`; include a visible subject,
   setting, and moment or spatial relationship. Keep
   `auto_generate_audio:true`; Manai will generate the matching cover art as
   part of finished production. One finished session defaults to private
   playable audio with matching cover art.
4. Return the `owner_url` from the result (shaped like
   `https://app.manaiapp.com/content/{contentId}`). Audio usually renders in
   one to two minutes; `get_content_status` reports authoritative state.

## Troubleshooting

- `401` from the endpoint means not yet authenticated — run the client's
  authenticate flow.
- If audio stays queued, poll `get_content_status` and share the owner link;
  the page follows processing to playable on its own.
- Edits require the exact `version` from `get_content`; on a version conflict,
  re-read and reapply.
- The user can review or revoke connected agents in Manai Web under
  **You → Account settings → Connected agents**.

Support: support@manaiapp.com · Privacy: https://www.manaiapp.com/privacy ·
Terms: https://www.manaiapp.com/terms

Human-readable capability guide:
https://www.manaiapp.com/guides/what-manai-can-create

AI-readable site index:
https://www.manaiapp.com/llms.txt