Metadata-Version: 2.5
Name: fl-studio-agent
Version: 0.1.0
Summary: MCP server for controlling FL Studio's piano roll
Project-URL: Homepage, https://github.com/origami-research/fl-studio-agent
Project-URL: Repository, https://github.com/origami-research/fl-studio-agent
Project-URL: Documentation, https://github.com/origami-research/fl-studio-agent/tree/main/docs
Author: Origami Research
Maintainer: Origami Research
License-Expression: MIT
License-File: LICENSE
Keywords: fl-studio,mcp,music-production,piano-roll
Classifier: Development Status :: 3 - Alpha
Classifier: Intended Audience :: Developers
Classifier: License :: OSI Approved :: MIT License
Classifier: Operating System :: OS Independent
Classifier: Programming Language :: Python :: 3
Classifier: Programming Language :: Python :: 3.11
Classifier: Programming Language :: Python :: 3.12
Classifier: Programming Language :: Python :: 3.13
Classifier: Topic :: Artistic Software
Requires-Python: >=3.11
Requires-Dist: flpkit==0.8.1
Requires-Dist: mcp>=2.0.0
Requires-Dist: numpy>=2.0.0
Requires-Dist: pip>=24.0
Requires-Dist: python-rtmidi>=1.5.0
Requires-Dist: watchdog>=6.0.0
Description-Content-Type: text/markdown

# FL Studio MCP server

This package is the MCP front end for deterministic FL Studio work. It routes
project data through `flpkit`, live host operations through the native Bridge,
and live controller operations through the MIDI wire/control broker.

## Setup

From the repository root, follow [../SETUP.md](../SETUP.md). For direct package
development:

```bash
cd mcp-server
uv sync --extra private
```

The `private` extra pins the unreleased `flpkit` source for internal work. A
public installation requires the released `flpkit` package described in the
OSS launch checklist.

Install the FL-side components with `uv run fl-mcp-install`. The native Bridge
is optional for file-lane work and required for live host operations.

Register the server with an MCP client using this environment's Python:

```bash
claude mcp add fl-studio -- /absolute/path/to/mcp-server/.venv/bin/python -m fl_mcp
```

## Tools and SDK

The server exposes `run`, `get_scene`, `check`, `render`, and `analyze`; the
operator's setup report is the `fl-mcp-doctor` command. The `run` tool docstring is the SDK cheatsheet: it documents
`fl`, `theory`, `Note`, and each supported operation. `run` executes cells in a
persistent kernel process with full Python, confined by the OS to its workspace
on Windows; see [../docs/38-python-kernel.md](../docs/38-python-kernel.md).

Use `uv run fl-mcp-dev-session --no-repl` for a disposable live smoke session.
Run `../scripts/gate.sh` for the repository gate; [../docs/gate.md](../docs/gate.md)
defines its current checks and test count.
