The developer productivity scenario is about connecting Claude to the systems a development team already uses — repositories, issue trackers, documentation, databases — so engineers can explore and operate them faster. It sits at the meeting point of tool design and MCP integration with Claude Code configuration.
The setup you should picture
A team works in Claude Code. Some capabilities run locally next to each developer, such as access to local files or a local build. Others are shared services, such as company documentation or an analytics database, served by central MCP servers. Project configuration makes the same servers available to everyone working in the repository.
Decisions the exam probes
Transport choice. A local server that a client launches as a subprocess uses stdio and exposes nothing on the network. A shared remote server uses the HTTP-based transport and needs authentication and per-user authorization.
Tool shape. Dozens of narrow tools that mirror database tables waste context and confuse selection. Fewer task-oriented tools with clear names, descriptions, parameter formats and enums work better. Overlapping tools should be merged with an explicit mode parameter.
Output size. A tool that returns thousands of rows floods the context window. Filters, pagination, limits and counts keep results useful.
Least privilege. If Claude should only read analytics data, the server connects with a read-only credential. Tool descriptions that say "read-only" do not make anything read-only.
Sharing configuration. Servers the whole project needs go in the project-scoped MCP configuration committed to the repository, with credentials supplied through environment variables or each user's own sign-in rather than written into the file.
Common traps
- Exposing a local-only server on the network.
- Sharing one admin credential with every user of a central server.
- Trying to fix wrong tool selection by shortening descriptions.
- Committing an API token inside the shared configuration.
- Relying on keyword filters to block write queries.
How to practise
Build a tiny MCP server with two overlapping tools and watch Claude choose between them. Rewrite the descriptions until the choice is reliable, then merge the tools and compare. Add a list tool that returns a large result set and introduce pagination. Finally, register the server in a project configuration file and confirm a teammate's setup would pick it up without any secret in the file.
The six scenarios are listed in Anthropic's official exam guide (version 1.1), with four drawn per sitting. The emphasis described here is our own study guidance, not official exam content.