docs(connectors): write setup guides for remaining catalog entries

[itomek]

The connector framework (#926) shipped with two real setup guides — Google and GitHub — and the index page lists everything else under "Coming soon."

Each remaining catalog entry needs its own docs/connectors/<id>.mdx page covering:

1. What the connector is, in one paragraph
2. Where to get the required credential(s) (with screenshots of the upstream provider's UI where helpful)
3. Pasting credentials into the GAIA Agent UI
4. Per-agent grant examples
5. Common errors / troubleshooting
6. Revoking access

Once a page lands, set docs_url in the matching catalog spec to https://amd-gaia.ai/connectors/<id> so the AgentUI's "Learn more" link points at it. Update docs/connectors/index.mdx — move the connector from "Coming soon" into "Documented connectors."

Catalog entries to cover

• Microsoft 365 — mcp-outlook
• Calendars — mcp-google-calendar
• Email — mcp-gmail
• Email — mcp-sendgrid
• Productivity — mcp-notion
• Productivity — mcp-linear
• Productivity — mcp-jira
• Productivity — mcp-slack
• Developer — mcp-git
• Developer — mcp-postgres
• Developer — mcp-desktop-commander
• Web — mcp-fetch
• Web — mcp-brave-search
• Web — mcp-context7
• Web — mcp-playwright
• Web — mcp-microsoft-learn
• Other — mcp-spotify
• Other — mcp-stripe
• Other — mcp-memory
• Other — mcp-filesystem
• Other — mcp-windows-automation

Use docs/connectors/google.mdx and docs/connectors/github.mdx as templates. They establish the structure and tone.

Pick whichever connector you'd actually use yourself — those are usually the ones where the docs catch real friction.

[github-actions]

Thanks for filing this — it's a good follow-on to #926/#927 and gives anyone picking up a connector a clear, scoped chunk of work.

A few notes that might help whoever (or whichever agent) grabs this:

Templates land first. The issue references docs/connectors/google.mdx, docs/connectors/github.mdx, and docs/connectors/index.mdx, but docs/connectors/ doesn't exist on main yet — it's still in PR #926 (claude/gallant-wescoff-2e6e97, currently open). Anyone starting on this should wait for #926 to merge (or rebase onto that branch) so the templates are actually present to copy.

Suggested PR shape per connector to keep reviews tight:

• One PR per connector (or 2-3 closely related ones — e.g. all Microsoft 365 surfaces) rather than a single 22-page mega-PR.
• Each PR: new docs/connectors/<id>.mdx + docs_url set on the matching catalog spec + index.mdx moved out of "Coming soon" + entry in docs/docs.json navigation.
• Verify the doc renders by checking the existing connectors render correctly first — the Mintlify build is the source of truth.

Pick by friction, not alphabet. The issue's last line is the key one: pick connectors you'd actually use, because those are where the upstream provider's UI has real gotchas worth screenshotting (e.g. Slack's app manifest vs. classic-app distinction; Notion's internal-vs-public integration toggle; SendGrid's API-key scope picker). Boilerplate-only docs for connectors nobody on the team uses tend to age into wrong-but-confident.

Track progress on the issue. The 22 checkboxes in the body are great — keep them as the source of truth and tick them as PRs land, rather than spawning 22 sub-issues.

Happy to help reviewing individual connector pages — ping me on the PR.

🟢 Minor note: a couple of these (e.g. mcp-jira) overlap with first-class GAIA agents (src/gaia/agents/jira/). Worth a one-line cross-reference in those connector docs pointing at the corresponding agent guide so users don't get confused about which path to take.