convez.ai
MCP ServerAutomaçãoIntermediário
ygetu22

Fruitful — Co-produtor de IA para FL Studio

ygetu22/fruitful

Co-pilot de IA que transforma ideias musicais em FL Studio via Claude

Ver no GitHub
InicialPluginScore · de 0 a 100

Servidor MCP que conecta Claude ao FL Studio nativo, permitindo controlar batidas, canais, mixer e plugins por comando de voz. Traduz descrições musicais em plain English para ações estruturadas no DAW, mantendo contexto do projeto em tempo real.

Instalação

$npx convez-ai ygetu22/fruitful

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
0
Forks
0
Acompanhando
0
Saúde
57%
Último commit
há 3 semanas
Versão
—
Issues abertas
0
Contribuidores
1

Casos de uso

  • Programar batidas e padrões no step-sequencer descrevendo ritmo em palavras
  • Ajustar parâmetros de VSTs e plugins nomeados sem navegar menus
  • Fazer gain staging e routing no mixer via comando estruturado
  • Explorar ideias musicais rapidamente sem interromper o fluxo criativo

Veredito

Projeto promissor em desenvolvimento ativo que resolve um problema real: desacoplar intenção criativa de conhecimento técnico de DAW. Implementação via SysEx nativo é sólida, mas ainda em v1 com cobertura limitada — ideal para quem quer experimentar a interface IA+música agora, entendendo que o escopo vai expandir.

README

A tradução para o português deste README ainda está na fila.

🍊 Fruitful

Your AI co-producer for FL Studio.

Most people who want to make music never get the sound out of their head — not because they're short on ideas, but because the theory and a DAW full of menus get in the way first. Fruitful is about tearing that wall down: say what you're hearing in plain words, and it helps you build it in FL Studio.

Fruitful is an open-source Model Context Protocol (MCP) server that connects the Claude desktop app to FL Studio. It's meant to be a real co-pilot — approachable enough for someone opening a DAW for the first time, and quick enough to stay useful once you already know your way around.

Design philosophy

Fruitful is built around FL Studio's native MIDI Controller Scripting API, using only directly supported operations so that every action is deterministic and reliable. Rather than emulating note input, it issues structured commands and reads project state, giving Claude accurate context to work from.

This keeps the v1 surface focused on what the API supports well today:

CapabilityHow
🥁 Drum / beat programmingWrites step-sequencer patterns directly (channels.setGridBit)
🎚️ Channel controlVolume, pan, name, color, pitch, mute/solo, route to mixer track
🎛️ Plugin parameter controlTune any native or third-party VST knob by name (plugins.setParamValue)
🎚️ Mixer controlGain staging, routing, naming
▶️ TransportPlay / stop / record / loop / position
🧠 Project awarenessReads your actual rack, mixer, and plugins so Claude acts on context

Piano-roll note authoring is intentionally out of scope for v1: FL's API does not expose a native, persistent note-writing function. See SPEC.md for the rationale.

How it works

Claude Desktop ──MCP──▶ Fruitful server (FastMCP) ──SysEx──▶ FL Studio device script ──▶ FL Studio engine
                                          (virtual MIDI ports: Request / Response)

Commands travel as SysEx messages, whose payload is an arbitrary-length byte stream, so Fruitful sends structured commands and receives real return values. See SPEC.md for the full design.

Why a separate project?

A few open-source projects already connect AI to FL Studio, and they're worth a look — especially Flapi, which paved the way for talking to FL's scripting API remotely.

Fruitful exists because it takes a different path. Most existing tools record notes into FL through a virtual MIDI port; Fruitful instead drives FL's native scripting API directly with structured commands, focusing on reliability and on the parts of the API those tools don't cover. That's a different foundation rather than a tweak on top of an existing one, so it made more sense to build it cleanly than to bolt it onto a project designed around another approach.

Status

🚧 In active development (started 2026, ongoing). The architecture and the core MIDI/SysEx bridge are designed and implemented; command coverage is expanding milestone by milestone (see the roadmap in SPEC.md). The full source will be published here as the project matures.

License

Released under the MIT License — free to use, modify, and build on.

Ver o original no GitHub

Bom para

Relacionados