franckdjiongo

convex-remote-mcp

franckdjiongo/claude-skills/convex-remote-mcp/SKILL.md

Build a production-ready REMOTE MCP server (Streamable HTTP) hosted INSIDE an EXISTING Convex backend — exposing your Convex functions as authenticated tools to claude.ai / Claude Desktop / Claude Code, secured by OAuth (WorkOS AuthKit), with a mandatory anti-leak projection layer, a gated test/verification discipline, and a production rollout. Use this skill whenever the user wants to create/build/set up an MCP server or custom connector on or for a Convex project, expose Convex functions/tools to claude.ai or Claude, add a remote/distant MCP connector backed by Convex, wire the `convex-mcp-gateway` component, add WorkOS AuthKit OAuth to a Convex MCP, safely project a Convex document for an LLM tool, harden a Convex MCP tool that reads the wall clock (e.g. a getCurrentDate / overdue / isOverdue tool returning a stale date over midnight or off by a timezone offset), or roll a Convex MCP server out to production — even if they only say "un MCP pour ce projet Convex", "expose mes fonctions Convex à Claude", "connecteur MCP distant Convex", "MCP gateway Convex", or mention `convex-mcp-gateway`. Project-agnostic and parameterized. NOT for: a generic non-Convex MCP server (use mcp-builder); a local stdio MCP; ordinary Convex app development or an in-app @convex-dev/agent assistant; or app/user sign-in auth (e.g. WorkOS/AuthKit login for a web app) that does not stand up an MCP server.

• Commits and pushes