Problem
SoleilCode currently ships a fixed set of project tools. Contributors cannot add a trusted external tool without changing the core package, while the ecosystem increasingly expects an interoperable server protocol.
Proposed experience
Design and implement a minimal MCP-compatible extension layer after agreeing on the threat model in this issue.
Acceptance criteria:
- Add explicit configuration for enabled servers; never auto-discover or auto-run third-party tools.
- Show the server and tool name in approval prompts.
- Preserve workspace boundaries, secret-file blocking, command approval, and private-mode expectations.
- Apply timeouts, output limits, clear errors, and cancellation.
- Include one local fixture server and integration tests with no network dependency.
- Document the trust model, configuration format, and a small example.
A short design proposal should be reviewed before implementation begins.
Free-first policy
Problem
SoleilCode currently ships a fixed set of project tools. Contributors cannot add a trusted external tool without changing the core package, while the ecosystem increasingly expects an interoperable server protocol.
Proposed experience
Design and implement a minimal MCP-compatible extension layer after agreeing on the threat model in this issue.
Acceptance criteria:
A short design proposal should be reviewed before implementation begins.
Free-first policy