# Prepare MCP Integration

Researches and delivers vendor MCP integrations through approved, governed review steps.

- Repository: https://github.com/paperclipai/paperclip (109885 stars)
- Category: AI and agents
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add paperclipai/paperclip --skill prepare-mcp-integration -g -a claude-code -y`
Codex: `npx skills add paperclipai/paperclip --skill prepare-mcp-integration -g -a codex -y`
Cursor: `npx skills add paperclipai/paperclip --skill prepare-mcp-integration -g -a cursor -y`
Gemini CLI: `npx skills add paperclipai/paperclip --skill prepare-mcp-integration -g -a gemini-cli -y`

## Description

Prepare MCP/vendor integrations through cited research, a content PR, exact-revision human approval, and one governed Paperclip connector PR per approved connection. Use for new integration research and delivery; not for ad hoc connector coding that bypasses the playbooks.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Prepare MCP Integration

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.

## Preserve These Boundaries

- 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 connections into one connector PR.
- Keep vendor credentials in approved secret storage. Never put secrets in
  briefs, catalog files, issue text, plans, fixtures, screenshots, logs, branch
  names, commits, or PRs.

## Default Connection Experience

The rest: https://github.com/paperclipai/paperclip/blob/HEAD/packages/skills-catalog/catalog/optional/software-development/prepare-mcp-integration/SKILL.md