Pictures, 3D models, a vision model and workflows as tools at /mcp
An agent driving Blender made its concepts, meshes and render reviews through a tool server of the game's own, which called this gateway; the gateway's MCP server offered only the memory notes. It now offers generate_image, generate_mesh, review_images, run_workflow, job_status and gateway_status beside them, each only where a model for it is here. Each tool makes its request of the client API as the caller, through the handler Handler built, key check and all: allowlists, limits, licences left out, budgets and accounting apply as to any request, and a job is the caller's. What a tool makes is kept as the caller's file and answered by id and download URL, since a server over HTTP cannot write to the caller's disk; a picture comes with a 512 px preview, and whole where no file can be kept. A picture to work from is a file id, a data URL or base64; one sent to the vision model is shrunk to 1280 px. A mesh takes minutes. A client that takes a stream is answered as server-sent events, with notifications/progress for its token while the job is queued, waiting for the GPU and running, and waits up to ten minutes; one that does not waits 50 seconds and gets the job id, which job_status asks after. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
1 parent
7c53380e68
commit
55d5e13534
9 files changed
+1314
-10
No files matched your search
@@ -82,7 +82,7 @@
|
||||
"/mcp": {
|
||||
"post": {
|
||||
"operationId": "postMcp",
|
||||
"summary": "The gateway's MCP server: the memory notes as tools",
|
||||
"summary": "The gateway's MCP server: the memory notes, and pictures, 3D models, vision and workflows, as tools",
|
||||
"tags": [
|
||||
"mcp"
|
||||
],
|
||||
|
||||
Reference in new issue
Block a user