prepare-mcp-integration

Prepares MCP vendor integrations through gated research PRs and per-connection connector PRs.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Adding a new MCP or vendor integration to Todero normally mixes research, planning, and connector code into one risky change. This Skill enforces a two-phase workflow: a reviewable research PR in todero-content, an exact-revision human approval gate, and then one governed connector PR per approved connection in the Todero App. ## Core Features & Use Cases - Cited research phase: Intakes a vendor link or brief through the integration harness, records every factual claim with URL and access date, and opens a research-only PR with the full planning package. - Exact-revision approval gate: Binds human acceptance to one research PR head SHA and an explicit connection set via a request_confirmation interaction, blocking all implementation until accepted. - Governed connector delivery: Implements one Todero App PR per approved connection following the Connector Playbook, covering OAuth discovery, credential handling, action catalogs, tests, and documentation. - Use Case: Given Notion's hosted MCP documentation URL, produce a research PR with evidence and a proposed connection set, wait for human approval of that exact revision, then ship a merge-ready notion-mcp connector PR with tests and admin setup docs. ## Quick Start Research the vendor MCP documentation at this URL and prepare the integration for Todero, but do not build the connector until I approve the research.

Frequently Asked Questions about prepare-mcp-integration

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

FAQPage Schema
How do I add a new MCP integration to Todero?

Run this Skill with the vendor documentation URL or brief. It produces a research-only PR in todero-content, requests human confirmation of the exact research revision, then creates one Todero App connector PR per approved connection following the Connector Playbook.

How does the research approval gate work before connector implementation?

The gate binds acceptance to one research PR head SHA and an explicit connection set via a request_confirmation interaction on an issue document. No App branch or code is created while the interaction is pending, and any change to the research head or connection set requires a fresh confirmation.

Can one PR contain multiple MCP connector connections?

No. Each approved connection gets its own isolated worktree, branch, and PR so it can be reviewed and merged independently. Only shared prerequisite infrastructure or broad playbook corrections may use separate prerequisite PRs.

Does the Skill handle OAuth discovery and dynamic client registration for MCP vendors?

Yes. Phase B derives OAuth behavior from evidence, probes DCR and redirect constraints safely, and avoids shipping a complete authorization/token endpoint pair for discovery-capable vendors unless intentionally authoritative, since broker precedence can bypass stored endpoints and RFC discovery.

When should I not use this Skill for connector work?

Do not use it for ad hoc connector coding that bypasses the research and approval playbooks. It is designed for new integration research and delivery where a human gate and per-connection PRs are required, not quick unreviewed changes.