Repository navigation
faba mcp on legume-mcp 0.3.1: producers in the background; README for any client (0.18.1) - #36
Merged
Merged
Conversation
…or any MCP client The user asked that long runs go to the background and that every tool's MCP server move to legume-mcp 0.3. count, depth, atoi, dartseq, apa, snp, run, qc and cluster take `background`: the call returns a job id at once, followed with job_status / job_wait / job_cancel, and the step is recorded when it succeeds. The README's agent section now covers any MCP client (generic mcpServers, Claude Code, VS Code, Codex; LEGUME_MCP_PROJECT), the server's own instructions for clients that do not pass them on (kept in step by a test), background runs, records and watching. Version 0.19.0.
YPARK
changed the title
YPARK
added a commit
that referenced
this pull request
Oct 20, 2026
Untrack local files swept into #36
YPARK
added a commit
that referenced
this pull request
Oct 20, 2026
faba mcp on legume-mcp 0.3.1: producers in the background; README for any client (0.18.1)
YPARK
added a commit
that referenced
this pull request
Oct 20, 2026
Untrack local files swept into #36
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
You asked that long runs go to the background and that every tool's MCP server move to legume-mcp 0.3.
RUST_BACKTRACEset, which turned main's CI red. The agent now also gets the built-injob_status,job_waitandjob_cancel.backgroundon the producers:count,depth,atoi,dartseq,apa,snp,run,qcandclustertakebackground: true. The call then returns{job, written, note}at once, and the agent follows the job. It is recorded (runall.sh,INDEX.tsv) when it succeeds, and a person following the server sees it as its own call and can stop it. faba's instructions mention it in one line.mcpServers(Claude Desktop, Cursor, Gemini CLI), Claude Code, VS Code and Codex CLI, and why to setLEGUME_MCP_PROJECT;backgroundis a tool argument only an agent uses; no library API, CLI flag or subcommand changed.Tests
tests/mcp_server.rschecks:background, and thejob_*tools are listed;countwithbackground: truereturns a job at once, andjob_waitreports it failed, naming the missing BAM;