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. For direct package development:
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:
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.
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
defines its current checks and test count.
Metadata
Release files for fl-studio-agent 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| fl_studio_agent-0.1.0.tar.gz | 453.1 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| fl_studio_agent-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 690.0 kB
Release files / fl_studio_agent-0.1.0.tar.gz
| Download URL | fl_studio_agent-0.1.0.tar.gz |
|---|---|
| Size | 453.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
759a96d8e694bb960eafbe54560e3eb5ecf81c235d6b301de4698b45fe461b78
|
|
BLAKE2b-256 checksum How to use checksums |
3ece66274eb75484593b18e30412432000e3fa5db47a1d29dea8be257825f54e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.11 {"installer":{"name":"uv","version":"0.10.11","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Release files / fl_studio_agent-0.1.0-py3-none-any.whl
| Download URL | fl_studio_agent-0.1.0-py3-none-any.whl |
|---|---|
| Size | 236.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4821900098ceb2276f26919e4770d0b70f83981f3e3ec515c2428a7c3911834d
|
|
BLAKE2b-256 checksum How to use checksums |
bffe968e3e3ae21931e6e2885acdcdc2cdd3e65a9485db3facfa65b35a21ff5b
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
uv/0.10.11 {"installer":{"name":"uv","version":"0.10.11","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
|
Security for fl-studio-agent 0.1.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.