Add permissions section to MCP Server setup

[joepeeples]

What does this PR do? What is the motivation?

Important

Please expedite editorial review as much as possible. This content is needed for a high-priority website update.

Contributes to DOCS-13657 by adding a full "Required permissions" section to the MCP Server setup docs. This will help customers avoid having access problems when they start using the MCP Server.

• Add new section to setup page
• Remove small redundant section from index page
• Reformat JetBrains instructions with numbered steps
• Add step to each setup tab for visibility, and link to new section for more details

Note

As with other content in the setup tabs, the added step is intentionally duplicated on each tab to make the instructions self-contained per client.

Merge instructions

Merge readiness:

• Ready for merge

For Datadog employees:

Your branch name MUST follow the <name>/<description> convention and include the forward slash (/). Without this format, your pull request will not pass CI, the GitLab pipeline will not run, and you won't get a branch preview. Getting a branch preview makes it easier for us to check any issues with your PR, such as broken links.

If your branch doesn't follow this format, rename it or create a new branch and PR.

[6/5/2025] Merge queue has been disabled on the documentation repo. If you have write access to the repo, the PR has been reviewed by a Documentation team member, and all of the required checks have passed, you can use the Squash and Merge button to merge the PR. If you don't have write access, or you need help, reach out in the #documentation channel in Slack.

AI assistance

Additional notes

[github-actions]

Preview links (active after the build_preview check completes)

Modified Files

• https://docs-staging.datadoghq.com/joepeeples/13657-mcp-permissions/bits_ai/mcp_server/
• https://docs-staging.datadoghq.com/joepeeples/13657-mcp-permissions/bits_ai/mcp_server/setup

[rtrieu]

minor feedback but otherwise looks good