Flstudio

Created By
veenastudioa year ago
Overview

what is Flstudio?

Flstudio is an MCP server that connects Claude to FL Studio, enabling users to create music using AI-generated MIDI messages.

how to use Flstudio?

To use Flstudio, download the necessary files, set up the MCP server, configure your MIDI ports, and start making music by sending MIDI messages to FL Studio.

key features of Flstudio?

  • Integration with Claude for AI-assisted music creation
  • Virtual MIDI controller setup
  • Easy configuration for both Windows and Mac users

use cases of Flstudio?

  1. Composing music with AI-generated melodies and chords.
  2. Recording live performances directly into FL Studio.
  3. Collaborating with others in the music community via Discord.

FAQ from Flstudio?

  • Can I use Flstudio on both Windows and Mac?

Yes! Flstudio is compatible with both operating systems.

  • Is there a community for support?

Yes! You can join our Discord for help and feature requests.

  • What do I need to get started?

You need to download the files, set up the MCP server, and configure your MIDI settings.

Server Config

{
  "mcpServers": {
    "flstudio": {
      "command": "PATH\\TO\\uv.exe",
      "args": [
        "--directory",
        "PATH\\TO\\FOLDER\\WITH\\SERVER",
        "run",
        "trigger.py"
      ]
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
veenastudio
Star
-
Language
-
License
-

Recommend Servers

View All
Voyei

3 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

14 hours ago