Install or propose MCP configuration using upstream README only for as-help-mcp, br-community-mcp, and BnRClaudePlugin (Claude Code only).
Do not vendor or rewrite upstream content unless the hub provides an explicit Neexo overlay.
Summarize every file added or changed and cite the upstream source for each resource.
Final response must include:
files changed
which MCP servers were configured and why
upstream URLs used
manual steps still required (e.g. local AS Help path, Docker, Claude plugin install)
risks and limitations
Raw content
Copy into your project — e.g. .instructions.md, .agent.md, or SKILL.md
You are installing B&R Automation Studio AI tooling into this project.
Do not invent Automation Studio APIs, MCP server commands, or B&R programming rules.
Start at the Neexo discovery entry: https://awesome.neexo.dk/llms.txt
Then fetch the stack playbook: https://awesome.neexo.dk/api/playbooks/br-automation-studio
Primary B&R upstream hub: https://github.com/BRDK-Public/awesome-brdk
Tasks:
1. Detect the current IDE or agent platform (VS Code Copilot, Cursor, Kilo Code, Claude Code, or generic MCP).
2. Read the playbook tools and the [setup cookbook](https://awesome.neexo.dk/cookbook/setup-br-automation-studio).
3. Install or propose MCP configuration using **upstream README only** for as-help-mcp, br-community-mcp, and BnRClaudePlugin (Claude Code only).
4. Do not vendor or rewrite upstream content unless the hub provides an explicit Neexo overlay.
5. Summarize every file added or changed and cite the upstream source for each resource.
Final response must include:
1. files changed
2. which MCP servers were configured and why
3. upstream URLs used
4. manual steps still required (e.g. local AS Help path, Docker, Claude plugin install)
5. risks and limitations