docs(TSP-1439): document custom MCP servers on Connectors page

[claude]

Summary

• Added a new Managing custom MCP servers from the Connectors page section to mcp-client.mdx explaining that custom MCP servers appear in a "Custom" category on the Connectors page, how to edit them by clicking their card, and how to add new ones via the "Add custom MCP" action card.
• Updated the intro paragraph of mcp-client.mdx to mention the Connectors page as a management surface.
• Updated the Warning in mcp-server.mdx to cross-reference the Connectors page for custom MCP connection management.
• Included a rollout note since the feature is behind the connectors-custom-category flag.

Linear: https://linear.app/relevance/issue/TSP-1439/

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
relevanceai	🟢 Ready	View Preview	Sep 9, 2026, 7:04 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

[linear]

TSP-1439

[github-actions]

🎯 Vibe check

Reviewed: 2 files (2 with issues, 0 clean)

Scores

	Dimension	Score	What's holding it back
🟡	Consistency	7/10	Six product-term capitalization misses in mcp-server.mdx — "agents", "tools", and "knowledge" used lowercase when referring to Relevance AI product features.
🟢	Technical clarity	9/10	Instructions are specific and UI element names are exact. Minor: the <Tip> on line 15 of mcp-server.mdx says the plugin makes the experience "significantly better" without stating what specifically is better.
🟢	Non-technical clarity	9/10	The Warning boxes at the top of each page are excellent orientation for readers who landed on the wrong one. Access control section is dense but the role matrix table rescues it.
🟡	Structure	7/10	Troubleshooting accordions in both files use unordered bullet lists. CLAUDE.md requires accordion content to use flowing sentences.

Score key: 🟢 9–10, 🟡 6–8, 🔴 1–5. Scores are a single overall judgment about the whole PR — not per file. The dropdowns below contain the line-by-line specifics.

✨ Overall vibe: Solid, well-scoped pair of pages that orient readers clearly and cover the right ground — the scope-clarifying Warning boxes and the access control role matrix are particularly good. The main drag is inconsistent capitalization of Relevance AI product terms in mcp-server.mdx and a pattern of bullet lists inside troubleshooting accordions across both files, both of which are quick fixes.

🔧 Issues (6)

• integrations/mcp/mcp-server.mdx:8 — "your agents, tools, and knowledge" → "your Agents, Tools, and Knowledge" (all three are Relevance AI product features)
• integrations/mcp/mcp-server.mdx:50 — "the Relevance AI tools will be available" → "the Relevance AI Tools will be available"
• integrations/mcp/mcp-server.mdx:228 — "access tools and agents across all your projects" → "access Tools and Agents across all your projects"
• integrations/mcp/mcp-server.mdx:268 — "call Relevance AI tools" → "call Relevance AI Tools"
• integrations/mcp/mcp-server.mdx:358 — accordion title "Can I restrict which tools are available via MCP?" → "Can I restrict which Tools are available via MCP?" (product term in an accordion title)
• integrations/mcp/mcp-server.mdx:359 — "exposing only a specific subset of agents" → "a specific subset of Agents"

🧩 Component suggestions (2)

• integrations/mcp/mcp-client.mdx:74–92 — the three troubleshooting accordions ("Tools not loading from external MCP server", "Agent cannot run external Tools", "Connection timeout or errors") all use unordered bullet lists. CLAUDE.md requires accordion content to use flowing sentences. Convert each list to a short prose paragraph, e.g. "Verify the server URL is correct and the server is online. If credentials are required, confirm they're entered correctly. The external server must support the Streamable HTTP transport."
• integrations/mcp/mcp-server.mdx:313–329 — same issue: the three troubleshooting accordions ("Authentication issues", "Tools not appearing", "Connection errors") each use unordered bullet lists. Convert to flowing sentences. The "Agent execution timeouts" accordion (line 332) already does this correctly — use that as the model.

🏗️ Page structure (1)

• integrations/mcp/mcp-server.mdx:26–169 — the "Supported clients" accordions use numbered step lists inside each accordion. This is borderline against the "flowing sentences" rule, but procedural setup instructions are a pragmatic exception. Lower priority than the troubleshooting lists. If Mintlify supports nested <Steps> inside <Accordion>, those would add the visual progress indicators that numbered lists lack — worth testing. Otherwise, leave as-is.

✅ Clean files (0)

Both files have at least one issue.

🔋 Credit usage

Item	Count
Files reviewed	2
Context pages read	3
Total lines processed	~928

Files read: integrations/mcp/mcp-client.mdx (111 lines), integrations/mcp/mcp-server.mdx (362 lines), integrations/mcp/agent-skills.mdx (111 lines), integrations/mcp/claude-code.mdx (127 lines), get-started/core-concepts/mcp-plugins.mdx (217 lines)