docs: MCP guide updates for current tool surface [sc-17040]

[emmavdh]

What and why?

Updates the ValidMind MCP documentation to match the shipped backend/mcp tool surface (17 tools on origin/main), and reconciles supported-client wording across related pages.

Before

• Capabilities covered only list/get + custom-field updates + templates
• Filters incorrectly mentioned risk level and deployment region
• Integrations overview / FAQ listed Claude Desktop instead of Claude Code
• No limitations, multi-environment URL note, or create/summarize/schema coverage

After

• Capabilities cover record/artifact read+write (including create and summarize), schemas/lookups, custom field schema + value read/write, and templates
• Filters match the MCP record/artifact filter surface (tiering, ownership roles, status, use case, business unit, etc.)
• Supported clients aligned to Cursor IDE + Claude Code
• Limitations callout for inventory/templates scope, findings-only artifacts, and rate limiting
• Production MCP URL called out explicitly, with a note for other environments

Shortcut: https://app.shortcut.com/validmind/story/17040

Implementation evidence (authoritative tool surface):

• validmind/backend mcp/mcp_service/tool_ids.py and mcp/mcp_service/tooling.py on origin/main
• Notable related backend work includes multi-record-type MCP support (SC-16816 / backend #3281) and earlier MCP inventory write/read expansions

How to test

skills/validmind-docs-coverage/scripts/render-pages.sh \
  guide/mcp/connect-ai-assistants-via-mcp.qmd \
  guide/integrations/managing-integrations.qmd \
  faq/faq-integrations.qmd \
  guide/chatbot-capabilities.qmd \
  about/glossary/glossary.qmd

Hosted preview in docs-staging - will be available once the validate check completes:

• Connect AI assistants via MCP
• Managing integrations
• Integrations and support FAQ
• ValidMind in-app assistant
• Glossary

What needs special review?

• Auth: Customer docs continue to document API key + secret as the supported production setup path. OAuth / PAT bearer modes exist in the MCP service and eng README, but are not published here as a customer setup path.
• Clients: Claude Desktop was removed from integrations/FAQ so those pages match the setup guide (Cursor + Claude Code). Codex appears in the eng README only and is intentionally omitted from customer docs.
• Artifacts: Documented as findings-only, matching the current artifact_type enum.

Dependencies, breaking changes, and deployment notes

• No product/code dependencies
• Docs-only change; follows normal main → staging → prod documentation delivery

Release notes

Expanded the ValidMind MCP setup guide so AI assistants can create and update inventory records and findings, discover schemas and lookups, and use accurate filters — plus clarified supported clients and current limitations. Learn more ...

Checklist

• What and why
• Screenshots or videos (Frontend)
• How to test
• What needs special review
• Dependencies, breaking changes, and deployment notes
• Labels applied
• PR linked to Shortcut
• Unit tests added (Backend)
• Tested locally
• Documentation updated (if required)
• Environment variable additions/changes documented (if required)

[github-actions]

Validate docs site

✓ INFO: A live preview of the docs site is available — Open the preview

[cachafla]

Great