Deliver the plugin's skills through an MCP server any agent can connect #67

Component

Something else: an MCP server as a delivery channel

Experience

• Operator: in any agent, one install line connects an MCP server that delivers the plugin's parts MCP can carry. That includes agents with no plugin format.
• Owner: those parts are updated in one place for every agent.

Proposed behaviour

Design an MCP server that serves skill text, templates and possibly rules, and decide whether it runs locally or is hosted on AWS. AWS's agent-toolkit-for-aws already serves skills this way through a retrieve_skill tool. It must settle four questions first, by runs:

1. Do Codex, Cursor and Kiro add an MCP server's instructions to the session, as Claude Code does?
2. Do sub-agents see those instructions?
3. Which command-line tools show elicitation, MCP's way for a server to ask the user a question? This could fill the missing fixed-option question in Kiro and Codex.
4. Does the model pick skills as reliably through a fetch tool as through skill descriptions?

Motivating case

MCP is the one extension point all four tools accept. It cannot carry hooks, or agents with their own tool lists, so it adds to the plugin and does not replace it.

A hosted server needs authentication and uptime, and makes every session depend on the network, all run by one maintainer. Weigh a local server against it before building anything.

Done when

The four questions are answered by runs, and the hld for this stream chooses local or hosted, or decides not to build.

Depends on

#63, for the tool-neutral text it would serve. This is a stream in .freethinking/strategies/multi-tool-plugin.md. Design with /freethinking:hld .freethinking/strategies/multi-tool-plugin.md mcp-delivery.