Update README and GETTINGSTARTED documentation to include Opencode an…

[uuc110]

Adds getting started documentation for Opencode and Kilocode — two AI coding agents not previously covered in the docs. This addresses the request raised in issue #863 where a user asked how to set up the Azure DevOps MCP Server with Opencode, and the maintainer invited a PR once figured out.

Changes:

• docs/GETTINGSTARTED.md — added two new sections:
  • Opencode: config snippet for ~/.config/opencode/opencode.json, PAT creation steps (dev.azure.com → profile icon → Personal access tokens → New Token → Full access), domain filtering tip using -d flag, browser-auth fallback note, link to official Opencode MCP docs
  • Kilocode: global config via mcp_settings.json (Option A) and project-level .kilocode/mcp.json (Option B, committable to version control), Windows cmd wrapper note, link to official Kilocode MCP docs
• README.md — updated the Installation & Getting Started callout to mention Opencode and Kilocode alongside the existing tools

GitHub issue number

Closes #863

Associated Risks

None — documentation-only change. No logic, APIs, or tool definitions modified.

✅ PR Checklist

• I have read the contribution guidelines
• I have read the code of conduct guidelines
• Title of the pull request is clear and informative.
• 👌 Code hygiene — N/A (docs only)
• 🔭 Telemetry added, updated, or N/A — N/A
• 📄 Documentation added, updated, or N/A — Added
• 🛡️ Automated tests added, or N/A — N/A

🧪 How did you test it?

• Verified the Opencode config snippet against a live local setup (~/.config/opencode/opencode.json) with @azure-devops/mcp running against a real Azure DevOps organization using AZURE_DEVOPS_EXT_PAT
• Verified the Kilocode config snippet against the local mcp_settings.json (kilocode.kilo-code/settings/mcp_settings.json) with the same MCP server running successfully
• Confirmed domain filtering (-d core work work-items repositories) works as expected in both agents
• Reviewed Markdown rendering locally — all code blocks, blockquotes, and section anchors are valid

[uuc110]

@uuc110 please read the following Contributor License Agreement(CLA). If you agree with the CLA, please reply with the following information.

@microsoft-github-policy-service agree [company="{your company}"]

Options:

• (default - no company specified) I have sole ownership of intellectual property rights to my Submissions and I am not making Submissions in the course of work for my employer.

@microsoft-github-policy-service agree

• (when company given) I am making Submissions in the course of work for my employer (or my employer has intellectual property rights in my Submissions by contract or applicable law). I have permission from my employer to make Submissions and enter into this Agreement on behalf of my employer. By signing below, the defined term “You” includes me and my employer.

@microsoft-github-policy-service agree company="Microsoft"

Contributor License Agreement

@microsoft-github-policy-service agree

[danhellem]

We are not advocating for PATs in the docs as PATs are slowing being removed from the service.

Have you tried using other ways for auth?

[uuc110]

I believe and have seen that Pat is Totally optional. Most of the time once the MCP is detected auto login window open in set default browser and authentication is done through that.

[danhellem]

that is fine, but we can't add using PAT into the docs. If you want to test a different auth method and update the doc, happy to merge this

[uuc110]

Sure, I will test non PAT Auth method, will double confirm on my end and will change the docs.

[uuc110]

@danhellem I have reviewed the Auth method auto logic trigged from the MCP. As you can see kilo code worked without my PAT configs. which was optional tho, still as per your mention I have removed it from the doc.