prepare-mcp-integration

Orchestrate vendor integration research and connector implementation through governed PR workflows and human-approved gates.

79.8k|14.6k|Updated Mar 2, 2026
One-click install
npx skills add https://github.com/paperclipai/paperclip --skill prepare-mcp-integration
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: prepare-mcp-integration
Source: https://github.com/paperclipai/paperclip/tree/main/packages/skills-catalog/catalog/optional/software-development/prepare-mcp-integration
Command: npx skills add https://github.com/paperclipai/paperclip --skill prepare-mcp-integration

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires git, gh, curl, and includes references (resource) components.

What problem does it solve?

This Skill solves the challenge of fragmented, uncoordinated integration development by enforcing a strict, two-phase governance process that ensures research is validated before any implementation code is written.

Core Features & Use Cases

  • Research-First Governance: Mandates a reviewable research PR in paperclip-content before any App-level code is created.
  • Structured Implementation: Provides a clear, playbook-driven path for connector development, ensuring consistency in auth, discovery, and governance.
  • Use Case: When adding a new MCP-compliant vendor, use this Skill to research the API and auth requirements, get human approval on the research gate, and then execute the connector implementation in the Paperclip App.

Quick Start

Use the prepare-mcp-integration skill to research and implement the Notion MCP connector based on the provided vendor documentation URL.

Frequently Asked Questions about prepare-mcp-integration

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I start a new MCP integration?

Begin by running the prepare-mcp-integration skill with your vendor brief or documentation URL. The skill will guide you through the research phase in the content repository before any implementation begins.

Why is a research PR required before coding?

A research PR ensures that the integration strategy, auth modes, and resource boundaries are reviewed and approved by a human, preventing costly rework and ensuring alignment with Paperclip governance.

Can I combine multiple connections into one PR?

No, the playbook requires one Paperclip App PR per approved connection to ensure clear review, auditability, and independent deployment of each integration.

What should I do if the vendor requires advanced auth?

Document the exception in the research phase and explain it in plain language. The skill requires that advanced controls remain hidden behind a disclosure unless absolutely necessary for the connection.

How do I handle vendor credentials safely?

Never include credentials in briefs, PRs, or logs. The skill mandates using approved secret storage and prohibits placing sensitive data in any part of the development workflow.