Select two. The whole team should get the productivity agent's connection to your internal issue-tracker MCP server, which authenticates with each developer's personal API token. Separately, one engineer wants to try an experimental MCP server for a new code-search tool without affecting teammates. Which two configuration choices are correct?

Answer: A and D — Define the issue-tracker server in the project-scoped .mcp.json committed to the repository, referencing the credential as ${TRACKER_TOKEN} through environment variable expansion. / Configure the experimental server in the engineer's user-scoped ~/.claude.json, so it is available only in that engineer's sessions and stays out of version control.

Shared team tooling belongs in the project-scoped .mcp.json, and environment variable expansion keeps secrets out of the repository (a). Personal or experimental servers belong in the user-scoped ~/.claude.json (d). (b) commits a secret to version control. (c) gives every teammate the experimental tools at connection time, since all configured servers' tools are discovered and available together, and telling people in a README to ignore them is not isolation.