docs(mcp): add GitHub Agent configuration

[Barbapapazes]

🔗 Linked issue

❓ Type of change

• 📖 Documentation (updates to the documentation or readme)
• 🐞 Bug fix (a non-breaking change that fixes an issue)
• 👌 Enhancement (improving an existing functionality)
• ✨ New feature (a non-breaking change that adds functionality)
• 🧹 Chore (updates to the build process or auxiliary tools and libraries)
• ⚠️ Breaking change (fix or feature that would cause existing functionality to change)

📚 Description

Hey,

I've added instructions to add MCP to GitHub Copilot.

It works well: https://github.com/Barbapapazes/infra.soubiran.dev/actions/runs/19268871494/job/55091539782#step:6:108

📝 Checklist

• I have linked an issue or discussion.
• I have updated the documentation accordingly.

[pkg-pr-new]

npm i https://pkg.pr.new/@nuxt/ui@5440

commit: 88a77f7

[HugoRCD]

@Barbapapazes I wrote this doc for the Nuxt MCP on Copilot Agent, do you think it's necessary to specify that you need admin rights on the repo and the validation process ?

### GitHub Copilot Agent

::note{icon="i-lucide-info"}
**Repository administrator access required** to configure MCP servers for GitHub Copilot coding agent.
::

If you have already configured MCP servers in VS Code, you can leverage a similar configuration for GitHub Copilot coding agent. You will need to add a `tools` key specifying which tools are available to Copilot.

#### Setup Instructions:

1. Navigate to your GitHub repository
2. Go to **Settings** > **Code & automation** > **Copilot** > **Coding agent**
3. In the **MCP configuration** section, add the following configuration:

```json
{
  "mcpServers": {
    "nuxt": {
      "type": "http",
      "url": "https://nuxt.com/mcp",
      "tools": ["*"]
    }
  }
}

4. Click Save

Validating the Configuration

To verify the MCP server is configured correctly:

1. Create an issue in your repository and assign it to Copilot
2. Wait for Copilot to create a pull request
3. In the pull request, click View session in the "Copilot started work" timeline event
4. Click the ellipsis button (...) at the top right, then click Copilot in the sidebar
5. Expand the Start MCP Servers step to see the configured Nuxt tools

For more information on using MCP with GitHub Copilot coding agent, see Extend coding agent with MCP.

[Barbapapazes]

In VS Code, the key is servers whereas in GitHub it is mcpServers so

If you have already configured MCP servers in VS Code, you can leverage a similar configuration...

isn't correct.

[Barbapapazes]

Otherwise, looks good!

[HugoRCD]

In VS Code, the key is servers whereas in GitHub it is mcpServers so

If you have already configured MCP servers in VS Code, you can leverage a similar configuration...

isn't correct.

It would be clearer if I added this clarification, don't you think?

If you have already configured MCP servers in VS Code (replace the `servers` key with `mcpServers` for GitHub Copilot Agent), you can leverage a similar configuration for GitHub Copilot coding agent. You will need to add a `tools` key specifying which tools are available to Copilot.

[Barbapapazes]

yes, looks perfect.