nv-onboard-dcr-mcp

Onboards DCR OAuth MCP catalog entries with provider documentation vetting and curl probes.

39.7k|4.4k|Updated Aug 26, 2021
One-click install
npx skills add https://github.com/novuhq/novu --skill nv-onboard-dcr-mcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: nv-onboard-dcr-mcp
Source: https://github.com/novuhq/novu/tree/main/.cursor/skills/nv-onboard-dcr-mcp
Command: npx skills add https://github.com/novuhq/novu --skill nv-onboard-dcr-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Adding a new dynamic client registration (DCR) OAuth entry to Novu's MCP server catalog requires verifying that each provider actually supports RFC 7591 self-serve registration, which involves tedious manual documentation review and live endpoint probing.

Core Features & Use Cases

  • Candidate Selection: Classifies catalog entries in mcp-servers.ts by oauth.mode and blocker status so only eligible provider-managed entries are onboarded, never re-auditing existing dcr entries.
  • Provider Docs Gate: Aborts onboarding when a provider requires redirect URI whitelists, manual approval, fixed pre-registered OAuth apps, or partner approval, and records the blocker in blocked-mcp-servers.md.
  • Curl Probe Checklist: Verifies RFC 9728 protected resource metadata, RFC 8414 authorization server metadata, and RFC 7591 dynamic client registration with ready-to-run curl commands and a PR body evidence template.
  • Use Case: When adding a new code-category MCP provider to the Novu catalog, run this checklist to confirm DCR support, probe the endpoints, and produce a catalog entry plus documented evidence.

Quick Start

Ask the agent to onboard a new provider-managed MCP entry to DCR mode using the nv-onboard-dcr-mcp checklist and paste the probe outputs into the PR body.

Frequently Asked Questions about nv-onboard-dcr-mcp

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

FAQPage Schema
How do I add a new DCR OAuth MCP server to the Novu catalog?

Read mcp-servers.ts and blocked-mcp-servers.md to confirm the entry is provider-managed and not blocked, then pass the provider docs gate, run the PRM, AS metadata, and DCR curl probes, and add the catalog entry with probe evidence in the PR body.

What OAuth standards does MCP dynamic client registration require?

The checklist verifies RFC 9728 protected resource metadata, RFC 8414 authorization server metadata with S256 PKCE support, and RFC 7591 dynamic client registration returning a client_id. All three must behave per spec for a catalog dcr entry.

When should MCP onboarding be aborted for a provider?

Abort when the provider requires redirect URI whitelist pre-approval, manual review of DCR registrations, a fixed pre-registered OAuth app instead of RFC 7591, or partner approval. Append the provider to blocked-mcp-servers.md with the blocker category and doc link.

Can I re-probe an MCP provider already set to dcr mode?

Only when the user explicitly requests verification or there is a production incident for that id. Run the probes and produce a short report without changing the catalog mode unless probes fail, in which case downgrade to provider-managed and add a blocker row.

When does MCP onboarding require code changes beyond the catalog entry?

Only for issuer or PRM mismatches, which extend mcp-oauth-issuer-match.ts, or non-standard token endpoint responses, which extend token-exchange-outcome.ts. The default rule is to never touch the OAuth URL generation or callback usecases for a new provider.