Skip to content

paperclipai/paperclip / packages/skills-catalog/catalog/optional/software-development/prepare-mcp-integration

prepare-mcp-integration

Verified

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.

FileKindSize
SKILL.mdskill md12.1 KB
examples/notion-mcp-research-gate.mdmarkdown1.9 KB

examples/notion-mcp-research-gate.md

View on GitHub
# Example: Research and Gate a Notion MCP Connection

## Input

> Research Notion's hosted MCP server and prepare it for Paperclip. Start from
> the vendor documentation URL. Do not build the connector until I approve the
> research.

## Application

1. Read the current `paperclip-content/integrations/README.md` and integration
   harness from the content target commit.
2. Research the official Notion MCP, OAuth, scopes, tools, limits, and admin
   setup. Record URLs and access dates, and mark unknowns rather than guessing.
3. Reconcile existing Notion integration artifacts and open PRs before adding
   or changing catalog content.
4. Open a research-only `paperclip-content` PR containing the planning package
   required by the integrations playbook.
5. Record the research PR head SHA and proposed connection set in an issue
   document, then request confirmation against that exact revision.
6. Stop with the issue in review. No Paperclip App branch exists yet.

## Gate Output

```text
Research PR: https://github.com/paperclipai/paperclip-content/pull/123
Research head: 0123456789abcdef0123456789abcdef01234567
Content source: 89abcdef0123456789abcdef0123456789abcdef
App source: fedcba9876543210fedcba9876543210fedcba98
Proposed connection set:
- notion-mcp: one OAuth credential owner, hosted MCP endpoint, and independently
  reviewable Notion action catalog
Known limitations:
- Production OAuth consent still requires credentialed QA after approval.
Next action:
- Human confirms or rejects this exact research revision.
```

After acceptance, create one isolated Paperclip App worktree and PR for
`notion-mcp`, reread the current Connector Playbook, and follow its current
implementation and validation requirements. If research reveals a reusable
OAuth or documentation rule, update the owning upstream playbook in the
appropriate PR before declaring the connector merge-ready.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 323kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 323kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 323kUpdated Claude CodeCodexVerifiedInstall