Skip to content

Develop

How neon-mcp is built, how to add a tool, how it is tested, and how to contribute.

  • Architecture - The module map of neon-mcp: registry and SDK adapter, the NEON client, cache and catalogs, projections, and the transports.
  • Adding a tool - A walkthrough of adding a neon-mcp tool: input and output models, registration, annotations, a fixture route, tests and docs regeneration.
  • Testing - The neon-mcp test layout: hermetic fixtures and the FixtureRouter, the conformance suite, live tests, coverage and the CI jobs.
  • Contributing - Branch and pull-request rules, lint and type checks, documentation regeneration, the two change logs, versioning and releases.