prepare-mcp-integration

Topics in the source

• Prepare MCP Integration
• Preserve These Boundaries
• Default Connection Experience
• Preflight
• Keep The Run Resumable
• Phase A: Research In paperclip-content
• Gate Research Before Building
• Phase B: Implement In Paperclip App

Take an input link or vendor brief through two separate phases: a reviewable research PR in paperclip-content, then connector implementation in Paperclip App only after a human accepts the exact research revision and connection set. Treat paperclip-content/integrations/README.md as the research contract and paperclip-content/integrations/skills/integration-harness/SKILL.md as its entrypoint. Reference and run them; do not copy their schemas, templates, state machines, reconciliation rules, or internal gates into this skill. Treat paperclip/doc/connections/CONNECTOR-PLAYBOOK.md on the implementation target branch as the connector contract. Follow it end to end; do not substitute remembered behavior or the examples in this skill. Finish Phase A with a research-only PR. Do not create an App implementation branch, task, or code change before the research gate is accepted. Bind acceptance to one research PR head SHA and an explicit connection set. Acceptance does not cover later commits or additional connections. Create one Paperclip App PR per approved connection. Shared prerequisite infrastructure or broad playbook corrections may use separate prerequisite PRs; never combine distinct

This is an excerpt. Refer to the complete source and its current requirements.