CCAR-F practice › Tool Design & MCP Integration · Question 39 of 105
Tool Design & MCP Integration
A team's .mcp.json, committed to the repository, configures a GitHub MCP server with an engineer's personal access token written directly in the file. What is the best fix?
Show answer and explanation
Answer: C — Replace the literal token with ${GITHUB_TOKEN} and have each engineer set that variable
Environment variable expansion in .mcp.json keeps the shared configuration in the repository while each environment supplies its own secret (c). Gitignoring the file (a) or moving the server to user scope (b) keeps the token out of git but gives up the shared team configuration. A token as a tool parameter (d) puts the credential in model-visible calls.
Keep going
More Tool Design & MCP Integration questions
- A team is standardizing Claude Code MCP setup. They need Jira for everyone, and one…
- An agent is connected to an internal MCP server whose search_code tool indexes all 40…
- A support agent connected to an internal knowledge-base MCP server spends many tool…
- Asked to explain how a checkout request is processed in an unfamiliar 600-file service…
- An agent needs to change one timeout value in a YAML file that has three identical…