# Navigating Claude Code: MCP Servers Worth Adding > [!question] Lingering Questions > - The recommended server list reflects the author's own stack, not a universal baseline — worth checking which servers actually justify their cost for a WordPress/DevRel-heavy workflow specifically. > - Server trust and transport-security tooling change quickly; recheck any specific server recommendation before adopting it. > [!tip] Article Ideas > - "If I haven't used a server in a week" as a literal audit trigger — could become a periodic MCP-server-pruning habit, paired with the vault's existing per-turn-cost measurement (Haas's 600-vs-45,000-token finding). > [!link] Cross Reference > - Part 9 of Oleg Efimov's 10-article HackerNoon series; see [[3. Resources/Literature Notes/Navigating Claude Code - The Full Workflow]] for series context. > - [[3. Resources/Permanent Notes/A Declared Capability Costs You Every Turn Not Every Use]] — the article's context-cost framing for MCP servers is the same measured mechanism from a different practitioner (Jürgen Haas, ECA) > [!quote] Vocabulary > - **Scoping (MCP)** — enabling a server only for the project where its tools are actually needed, and exposing only the specific tools required rather than a server's full tool set ## Bibliographic capsule Article, HackerNoon, 2026-08-04. Ninth installment of Oleg Efimov's Claude Code series. ## Author's thesis (Adler Q1+Q2) **What is the article about?** When an MCP server's data and actions justify the security, configuration, and context costs it adds to every Claude Code session. **What is being argued?** MCP servers should be scoped by project, exposing only the tools a task actually needs; use read-only credentials and narrow filesystem roots by default; and audit server code, disabling integrations that go unused — because every enabled server's tool schemas cost context on every turn regardless of whether the task uses them. ## Key arguments (≤3) 1. **Scope servers by project, expose only needed tools** — a server enabled globally with its full tool set costs every session, whether or not that session needs it. 2. **Use read-only credentials and narrow filesystem roots by default** — least-privilege as the default posture, not an opt-in hardening step. 3. **Audit server code and prune unused integrations** — "if I haven't used a server in a week" is offered as a literal cutoff. ## Claim atoms ### MCP servers carry a security surface, not just a convenience surface > [!quote] ID:rw_01kz7stpvxerxvc9vj3zbz4vqk > MCP servers are more dangerous Where/why: reframes MCP adoption as a security decision first, convenience decision second. ### Default to minimum access — read-only, narrow roots > [!quote] ID:rw_01kz7stqk7nd6cm5p3ttxjb7nk > Give servers the minimum access Where/why: the article's concrete least-privilege default. ### Prune servers that go unused > [!quote] ID:rw_01kz7straj36p3je9z6fw3mnfm > if I haven't used a server in a week Where/why: gives a literal, actionable pruning trigger rather than a vague "review periodically." ## Permanent candidates - The article's cost/security framing for MCP servers substantially overlaps an existing Permanent note built from a different practitioner's measured token cost (600 vs. 45,000 tokens/turn) — connecting rather than creating a near-duplicate note. ## Processing checklist - [x] Checked existing Permanents for this article's MCP-scoping claim — found a closely matching, better-evidenced note (measured token cost), linked rather than duplicated - [x] Connect into the relevant MOC — [[3. Resources/MOCs/AI Agent Safety MOC]], [[3. Resources/MOCs/AI Cost & Tokenomics MOC]] ## Links - [[3. Resources/MOCs/AI Agent Safety MOC]] — MCP server scoping is a direct agent-access-control practice - [[3. Resources/MOCs/AI Cost & Tokenomics MOC]] — the per-turn context cost of enabled tool schemas - [[3. Resources/Permanent Notes/A Declared Capability Costs You Every Turn Not Every Use]] — because evidence-for; independently confirms the same "every enabled tool costs every turn" mechanism this article argues from principle rather than measurement - Metadata: [[3. Resources/Readwise/Articles/Navigating Claude Code MCP Servers Worth Adding|Navigating Claude Code - MCP Servers Worth Adding]]