Scope Claude Code's .mcp.json to the project instead of trusting global defaults

Produce a project-scoped .mcp.json for D:\CLAUDE\tools.scult.in, plus the accompanying guidance a teammate opening this repo for the first time would need before approving it — a new MCP server is new code with tool-calling access running inside every session in this repo, not a passive config value.

MCP SERVERS THIS PROJECT ACTUALLY NEEDS
A Postgres MCP server for querying the staging database read-only during debugging, and a Figma MCP server for pulling design-token values referenced in the component library.

HOW SECRETS FOR THESE SERVERS ARE HANDLED TODAY
The Postgres connection string lives in a local .env file, never committed; each developer has their own read-only staging credential.

WHETHER EACH SERVER BELONGS AT PROJECT SCOPE OR USER SCOPE
Postgres and Figma both belong at project scope — everyone on this repo debugs against the same staging database and the same design file.

WHAT ALREADY EXISTS
No .mcp.json exists yet in this repository.

PRODUCE
1. The .mcp.json file itself, listing only the servers named above, each with its command, args, and any required env vars referenced by name using the dollar-brace environment-variable substitution syntax MCP configs expect — never a literal token, key, or connection string written directly into the file, since .mcp.json is typically committed to version control and a literal secret in it is a secret leaked to everyone with repository read access, including in the git history after the line is later removed.
2. A short note per server on what tools it exposes and why this specific repository needs it — a server justified by 'might be useful' rather than a concrete task this repo actually does is a larger trust surface than the project needs and should be left out.
3. A .env.example entry for every referenced variable, so a new contributor knows exactly what to set locally without guessing, and confirmation that the real .env is already gitignored.
4. For each server, one line on The Postgres server is a widely used, actively maintained community server; the Figma server is newer and worth a closer look at what it can write, not just read. — is this a first-party or well-known server, or something newer and less audited — since Claude Code will prompt for approval the first time a project's MCP servers are loaded, and that prompt is only useful if a teammate reading it actually knows what they are approving rather than clicking through out of habit.

CONSTRAINTS
- If No .mcp.json exists yet in this repository. already lists a server not named in the current needs list, flag it explicitly rather than silently dropping or silently keeping it — an unused server still listed is either dead configuration or a sign the needs list above is incomplete.
- Do not add a server at project scope if Postgres and Figma both belong at project scope — everyone on this repo debugs against the same staging database and the same design file. indicates it is really a personal preference, such as a developer's own note-taking tool, rather than something this specific codebase depends on — project scope means every teammate and every session in this repo inherits it, whether they want it or not.
- State plainly which servers grant filesystem or network access beyond this repository, since that is the specific category of MCP tool access most worth a second look before approval.

OUTPUT
The .mcp.json file, the .env.example additions, and the per-server trust notes, in that order.