Skip to content

docs(setup): add per-role MCP access how-to recipe#854

Merged
potiuk merged 1 commit into
apache:mainfrom
justinmclean:howto-per-role-mcp
Jul 13, 2026
Merged

docs(setup): add per-role MCP access how-to recipe#854
potiuk merged 1 commit into
apache:mainfrom
justinmclean:howto-per-role-mcp

Conversation

@justinmclean

Copy link
Copy Markdown
Member

Summary

Add docs/setup/per-role-mcp-access.md: a step-by-step recipe showing a team member how to enable an MCP server for their personal use only — registering it in user-scope Claude settings and writing a .apache-magpie-local/.md override — without touching shared project config. Includes three concrete examples (release manager / Policy MCP, security triage / private CVE database, infrastructure / deployment MCP) and guidance on when to graduate to shared project config.

Update docs/setup/README.md to list the new page in Deep documentation.

Generated-by: Claude (claude-sonnet-4-6)

Type of change

  • Skill change (.claude/skills/<name>/) — eval fixtures updated below
  • Tool / bridge contract (tools/<system>/*.md)
  • Python package (tools/*/ with pyproject.toml)
  • Groovy reference impl
  • Cross-cutting (RFC, AGENTS.md, sandbox, privacy-LLM)
  • Documentation (docs/, README.md, CONTRIBUTING.md)
  • Project template (projects/_template/)
  • CI / dev loop (prek, workflows, validators)
  • Other:

Test plan

  • prek run --all-files passes
  • For Python packages touched: uv run pytest / ruff check / mypy passes
  • For Groovy bridges touched: command-line invocation tested end-to-end
  • For skill changes: eval suite passes for the affected skill
    (PYTHONPATH=tools/skill-evals/src python3 -m skill_evals.runner tools/skill-evals/evals/<skill>/)
  • For skill behaviour changes: a new or updated eval fixture is included in this PR
    (a regression test for the bug fixed / the behaviour added — see CONTRIBUTING.md)
  • Other:

@justinmclean justinmclean self-assigned this Jul 13, 2026

@potiuk potiuk left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I like all the new personalisation features and having policy -based actions.

Add docs/setup/per-role-mcp-access.md: a step-by-step recipe showing a
team member how to enable an MCP server for their personal use only —
registering it in user-scope Claude settings and writing a
.apache-magpie-local/<skill>.md override — without touching shared
project config. Includes three concrete examples (release manager /
Policy MCP, security triage / private CVE database, infrastructure /
deployment MCP) and guidance on when to graduate to shared project config.

Update docs/setup/README.md to list the new page in Deep documentation.

Generated-by: Claude (claude-sonnet-4-6)
@potiuk potiuk force-pushed the howto-per-role-mcp branch from 56bcb55 to 75b3250 Compare July 13, 2026 08:56
@potiuk potiuk merged commit c7c6179 into apache:main Jul 13, 2026
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants