[FEATURE] MCP install target for Claude Code (project + user scope)

[dmartinol]

Is your feature request related to a problem? Please describe.

apm install already configures MCP for several clients, but not Claude Code. Projects that use Claude (.claude/) or global installs (apm install -g) still had to maintain .mcp.json / user MCP config by hand, separate from apm.yml and the lockfile.

Describe the solution you'd like

Treat Claude Code as a first-class MCP target: when appropriate, merge declared MCP dependencies into Claude's config (project-level shared config and user-level config for global installs), consistent with how other supported clients are handled. Users should be able to steer behavior with the same kinds of runtime flags as today where it makes sense.

Describe alternatives you've considered

• Documentation-only workflows (manual copy/paste from the registry) — easy to drift from the manifest and lockfile.
• Supporting only project scope and ignoring global install — weaker fit for people who use apm install -g like other targets.

Additional context

Claude Code documents project vs user MCP scopes; the implementation should follow current upstream docs for paths and JSON shape. Details belong in the PR.