# Sound, inside your project.

Connect Satie to your coding agent, describe the world you already have, and bring its sound into your engine.



[Documentation](https://www.satie.world/docs)

## From your world to its sound



1. Connect your coding agent using the commands below. Sign in when the browser opens, then ask the agent to call satie_status. Signing in on this website alone does not authorize the agent.
2. Open your project in the agent. Describe the place, what happens there, and where the listener should be. The agent reads the actual objects, scale, events and controls before composing.
3. Review the sound plan and agree on a generation budget. The agent writes the sound scene, finds or makes its recordings, and installs the integration for your platform.
4. Run the project. Walk toward and away from sources, trigger its interactions, and adjust the mix. Keep the scene and recordings with the project so playback does not depend on a live generation call.

## A first request



Ask your coding agent

```
Add sound to this project with Satie. Inspect the existing scene and use its actual object names, scale and gameplay events. Start with a restrained, believable soundscape. Show me the plan and cost before generating audio, then install the integration for this engine and help me test it.
```

## Make it fit the place

Start with a few sounds that belong together. Continuous ambience can form a quiet bed; doors, footsteps and calls should happen when their causes do, with room for silence between them.

Check the nearest reachable source as well as the starting position. An already reverberant recording may not need another room around it. A successful runtime check confirms that the integration works; listening tells you whether the scene works.

[Full MCP reference](/developers/mcp.md) · [Try the soundscape editor](/sketch)

## Connect your coding agent

### Claude Code

```
claude mcp add --transport http --scope user satie https://www.satie.world/mcp
claude mcp login satie
claude mcp get satie
```

Run these in your own terminal, not through the agent: the login opens your browser and needs an interactive shell (inside Claude Code, /mcp then Satie does the same). Afterwards start a new session (or run /mcp) so the Satie tools load, then ask Claude Code to call satie_status.

[Claude Code MCP docs](https://code.claude.com/docs/en/mcp)

### Codex

```
codex mcp add satie --url https://www.satie.world/mcp
codex mcp login satie
codex mcp list
```

Run these in your own terminal, not through the agent: the login opens your browser. Then ask Codex to call satie_status; "Needs authentication" in the list means the login is still owed.

[Codex MCP docs](https://learn.chatgpt.com/docs/extend/mcp?surface=cli)

### Cursor

```
{
  "mcpServers": {
    "satie": {
      "url": "https://www.satie.world/mcp"
    }
  }
}
```

Cursor asks you to sign in the first time the server connects. Then ask the agent to call satie_status.

[Cursor MCP docs](https://docs.cursor.com/context/mcp)

### Gemini CLI

```
gemini mcp add --transport http --scope user satie https://www.satie.world/mcp
gemini
```

Run these in your terminal. Inside Gemini CLI, run /mcp auth satie and sign in through the browser, then /mcp list to check the connection. Ask Gemini to call satie_status.

[Gemini CLI MCP docs](https://geminicli.com/docs/tools/mcp-server/)

### Any MCP client

```
{
  "mcpServers": {
    "satie": {
      "url": "https://www.satie.world/mcp"
    }
  }
}
```

Any client that speaks remote HTTP MCP with OAuth works: add the endpoint, sign in when it opens the browser, then call satie_status. No local server, API key or bearer header.

[The agent guide](/developers/mcp.md)
