GIOS Studioalpha · read-only
MCP Explorer
Given an approved dispatch plan, how is work represented as MCP server/tool interactions? Protocol model only — the runtime invokes nothing. Approval-gated. Read-only.
3
Sessions
5
Servers
11
Calls
4
Approval barriers
MCP research representationready
2 server · 1 tool · 2 resource · 5 call
knowledgefilesystemserver_pingresource_readtool_callprompt_get
MCP integration write representationwaiting_approval
2 server · 2 tool · 1 resource · 3 call
communicationdataserver_pingtool_call2 approval
MCP creative pipeline representationwaiting_approval
1 server · 2 tool · 1 resource · 3 call
creative_mediaresource_readtool_call2 approval
The MCP Runtime owns only the tool-protocol surface (servers, tools, resources, prompts, transports, calls). It represents HOW work maps onto MCP; it never invokes — real invocation is owned solely by the future Broker, gated on a binding Policy allow, with secrets resolved by the future Vault (names only) and human approvals by the future Approval runtime.