> ## Documentation Index
> Fetch the complete documentation index at: https://docs.glissando.dev/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> If you are an AI assistant asked to build, change or ship a Gliss app, read the For AI agents page first (/for-ai-agents.md on this site) and follow its steps.
> Inside an app's folder, the app's own AGENTS.md is the authority; `gliss guide` prints it. Never ask the user for a secret's value.

# Supported AI tools

> Using Gliss from Claude Code, Claude Desktop, Cursor and Codex: the guidance in every app, and the Gliss tools over MCP.

> [!NOTE]
>
> **Coming in the first release.** This page describes behaviour being built for the first Gliss release. Details may change before it ships.

Gliss works with the AI tool you already use: **Claude Code, Claude Desktop, Cursor and Codex**, or any tool that reads `AGENTS.md` and speaks MCP.

## Start with one sentence

Tell your AI:

```text theme={null}
Read https://docs.glissando.dev/for-ai-agents.md, then build me a Gliss app that <your idea>.
```

[For AI agents](https://docs.glissando.dev/for-ai-agents.md) is written for your AI. It checks the `gliss` client, signs you in, creates the app and builds it, and asks you when it needs you. The whole site is also available to AI tools as Markdown: add `.md` to any page's address, or start from `llms.txt` at the root of this site.

## The guidance in every app

Every Gliss app carries instructions for your AI, so it writes `gliss.yaml` correctly, keeps secrets out of the code and uses mock mode:

| File | Read by |
| - | - |
| `AGENTS.md` | Codex, Cursor and most AI tools. The full guide; its text is on [AGENTS.md](https://docs.glissando.dev/reference/agents-md.md) |
| `CLAUDE.md` | Claude Code. A block Gliss manages imports `AGENTS.md`; the rest of the file is yours |
| `.cursor/rules/gliss.mdc` | Cursor |
| `.claude/skills/gliss-secrets/`, `.cursor/skills/gliss-secrets/` | Claude Code and Cursor: how to declare a secret without ever handling its value |
| `PROMPT.md` | You: a starter prompt with examples to paste into your AI |

`gliss init` writes them into a new app. In any app's folder:

| Command | What it does |
| - | - |
| `gliss guide` | Print `AGENTS.md` |
| `gliss guide --check` | Say whether the files are missing or out of date |
| `gliss guide --write` | Write or refresh them. It replaces only files Gliss wrote, and only its own block in `CLAUDE.md` |

Commit the files, so everyone working on the app gets the same guidance. Run `gliss guide --write` again after `gliss update`.

## Connect the Gliss tools

`gliss mcp` gives your AI the [Gliss tools](https://docs.glissando.dev/reference/mcp-tools.md): status, diagnosis and logs. It uses your `gliss login` session.

**Claude Code**

```sh theme={null}
claude mcp add gliss -- gliss mcp
```

**Cursor**

In `.cursor/mcp.json` in the app's folder, or `~/.cursor/mcp.json` for every project:

```json theme={null}
{"mcpServers": {"gliss": {"command": "gliss", "args": ["mcp"]}}}
```

**Codex**

In `~/.codex/config.toml`:

```toml theme={null}
[mcp_servers.gliss]
command = "gliss"
args = ["mcp"]
```

**Claude Desktop**

In Settings, Developer, Edit Config, add to `claude_desktop_config.json`:

```json theme={null}
{"mcpServers": {"gliss": {"command": "gliss", "args": ["mcp"]}}}
```

If Claude Desktop cannot find `gliss`, give its full path as `command`: `command -v gliss` prints it on macOS and Linux, `where.exe gliss` on Windows.

## Letting your AI release

By default your AI can read status, diagnoses and logs, but not change anything. To let it release from your machine too, start the server with `--allow-release` (Beta and your Preview) or `--allow-release=preview` (your Preview only), and `--dir` for the app's folder. It then asks you before every release. This builds with Docker on your machine, so it needs what [`gliss release`](https://docs.glissando.dev/reference/cli#gliss-release) needs. Soon most people won't need it: each push to your work branch will build your Preview.

> [!WARNING]
>
> Never allowlist or auto-approve `gliss_release`. Each call replaces what runs at a stage.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.