Repository navigation
MCP: let external clients list what the composer offers (skills, commands, files) #33128
Replies: 2 comments
|
One more gap from the same client, in case it fits here. A Would you accept the before and after token counts on that item? It's a small read-only addition. I can include it with the composer lists or send it as its own PR, whichever you prefer. |
|
One more read-only gap from the same client. Would you accept returning the resolved scripts from those tools, including for linked environments? It's a small change, and I can send it with the composer lists or as its own PR, whichever you prefer. |
Uh oh!
There was an error while loading. Please reload this page.
Problem or use case
MCP clients that message T3 threads can't offer the composer's
/,$and@pickers. Skills and slash commands are in the provider snapshot, butorchestrator_capabilitiesdoesn't return them. File search isprojects.searchEntrieson the WebSocket RPC, which rejects MCP tokens.Requested behavior
One read-only MCP tool, for example
t3_composer_search, takingenvironmentId,providerInstanceId, optionalprojectId,kind(skill,commandorpath),queryandlimit. It returns the names and short descriptions the composer would show, including on linked environments. A separate tool keeps these lists out oforchestrator_capabilitiesoutput, which agents read.Scope question
Is this direction acceptable, and would you want skills/commands and path search as one PR or two? I'm happy to implement whichever you approve.
Related: #15137 (similar read-only exposure) and #27123 (
skills_review, without commands or files).All reactions