matthewbusel-basis

Hand this document to Claude Code or Codex and let it walk you through building a working unified MCP gateway in roughly a day. The output is a git repo, one provider mounted end-to-end, a usage skill paired with that provider, and a provider-addition skill so the next provider lands in an hour. The shape mirrors what we run at Basis as Satellite, with most of the names changed and the heavyweight pieces simplified.
What you're about to build
A single endpoint that fronts many provider integrations, authenticates the caller, holds the right credential per user, exposes provider tools through one MCP surface, and ships with the procedural-knowledge layer that makes those tools actually useful inside an agent. The post that links this recipe argues that the under-appreciated cost of running your own gateway is skills, not security or maintenance. The recipe takes that seriously: it pairs every provider with a usage skill, treats the skill as part of the provider contract, and refuses to call the build done unti