mcp-server

Solid

Before adding a remote MCP server or tool to a web product, adding OAuth to it, or listing it in a directory: ship it right the first time, tests included.

AI & Automation 633 stars 85 forks Updated today MIT

Install

View on GitHub

Quality Score: 91/100

Stars 20%
93
Recency 20%
100
Frontmatter 20%
70
Documentation 15%
100
Issue Health 10%
80
License 10%
100
Description 5%
100

Skill Content

# MCP server **Build the remote MCP server and prove it before listing it.** This skill covers serving outside agents and getting listed without relearning the same lessons. Its examples use Next.js, Supabase, Clerk and Netlify. **Keep product-specific facts in that product's own records.** This skill names those records by what they hold: - The API contract: every REST route and MCP tool, what it accepts, returns and refuses; - The distribution record: one row per listing (directory, registry, package), with its state, its date and how it is updated, and each client verified, with the date and what was called; - The decision log: dated decisions that had real options, each with its reopen trigger; - The backlog: deferred work, each item with the trigger that reopens it. **Read `clerk-production` § MCP OAuth before writing the route.** Clerk's settings are there, not here; this skill does not repeat them. Allow for four behaviours: discovery lists differ from token shape, verifier outages return `503`, unknown `kid` values are refused before Clerk, and revocation remains unseen until expiry. ## What binds, in order 1. **Apply `saas-authorization` first because a tool is a route.** Its caller is resolved by the three functions, deterministic code decides what it may do, and everything it returns that a person wrote is untrusted text. 2. **Apply and reread every Clerk OAuth setting per instance.** Apply `clerk-production` § MCP OAuth. 3. **Apply this skill to the server a...

Details

Author
phuryn
Repository
phuryn/product-engineering
Created
2 weeks ago
Last Updated
today
Language
Python
License
MIT

Integrates with

Similar Skills

Semantically similar based on skill content — not just same category

AI & Automation Listed

mcp-authorization

This skill should be used when the user mentions "MCP auth", "MCP OAuth", "MCP authorization", "OAuth 2.1", "OIDC", "access token validation", "audience", "resource server", "protected resource metadata", "token passthrough", "confused deputy", "Entra", "Okta", or securing a remote MCP server's identity and access. It provides the 2026-07-28 OAuth 2.1 / OIDC model for MCP servers as OAuth resource servers.

3 Updated 4 days ago
ClaudeRegistry
AI & Automation Listed

mcp-builder

Build production MCP servers with dual transport (stdio + HTTP) and OAuth 2.1 for Claude Co-Work. Covers server design, tool definitions, Vercel deployment, and the full OAuth ceremony. Use when building a new MCP server, adding HTTP transport, adding OAuth, or deploying to Vercel. Triggers on "MCP server", "build MCP", "create MCP", "Co-Work", "mcp-builder", "remote MCP".

0 Updated 3 months ago
addiplus
API & Backend Listed

building-mcp-servers

Use this skill whenever the user wants to design, build, harden, review, or debug an MCP (Model Context Protocol) server — including "build me an MCP server for X", connecting an AI agent/Claude to a database or API, adding tools/resources to an existing MCP server, reviewing a contributor PR against an MCP server, or fixing security issues (SQL injection, unpinned install scripts, error leakage) in one. Especially strong for database MCP servers (Postgres, MySQL, SQLite) — schema introspection, connection pooling, read-only guardrails, and query safety. Trigger this even if the user just says "MCP server" without saying "skill," and even for smaller tasks like adding a single tool or fixing a transport bug.

1 Updated 3 months ago
cyberreinxy