docs(claygent): document custom MCP server configuration in Claygent builder#250
Merged
Merged
Conversation
Collaborator
Author
| Intercom conversation 215474454637579 was escalated to a human because Fin couldn't answer when customer Esteban asked: "can you point me to where I can find to add custom MCP on my claygents created outside a table" — they were trying to connect a self-hosted n8n instance behind a VPN to a standalone Claygent via MCP. I diagnosed that `docs/claygent-builder.md` had zero coverage of the custom MCP server capability: the doc documented web search and find contacts/jobs as Claygent tools but said nothing about the "Add custom MCP server" button in the Configuration → Tools panel. Verified against code via the verifier sub-agent (BETA: button at `apps/frontend/src/components/AgentPlayground/Sections/AgentPlaygroundToolsSection.tsx:360` in standalone Claygent, no flag gate; Eppo-gated in table-embedded context) and Slack (Sep 2025 #all-product-progress: "Custom MCP is now live for Enterprise"; Apr 2026 #team-rep-tools: "Self-serve users can access it by joining the beta"). Verifier also corrected my initial claim — the API key is optional (typed `api_key?` in `libs/shared/src/actions/use-ai/mcp-servers.ts:96-100`), not required. Opened PR #250 adding a "Custom MCP server" subsection to the "Configuring your agent" section with setup steps, plan availability note (Enterprise live, self-serve beta opt-in), optional API key guidance, and usage tips (specific prompting, 2–3 server limit, chaining, no OAuth); also added a FAQ entry specifically answering the customer's question about standalone Claygents outside tables. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Added a "Custom MCP server" subsection to the "Configuring your agent" section in
docs/claygent-builder.md, and a matching FAQ entry: "Can I connect a custom MCP server to a standalone Claygent (created outside a table)?" The new section covers what custom MCP servers are, how to add one from the Claygent builder Configuration → Tools panel, how to add one workspace-wide via Settings → Connections, which fields are required vs. optional (name + URL required; API key optional), and tips for effective use (specific prompting, 2–3 server limit, chaining, OAuth not supported).Why
Intercom conversation 215474454637579 was escalated to a human because Fin couldn't answer: customer Esteban (Veryon client use case) asked "can you point me to where I can find to add custom MCP on my claygents created outside a table" — they wanted to connect a self-hosted n8n instance (behind VPN) via MCP to a standalone Claygent. Support agent Quentin Renaud answered by sending screenshots showing the Configuration panel → Tools → "Add custom MCP server" button. The docs had zero coverage of this capability:
claygent-builder.mdmentioned web search and find contacts/jobs as configurable tools but said nothing about custom MCP server connectivity, leaving Fin unable to answer.Considered existing closest docs before adding to
claygent-builder.md:mcp-settings.md: covers the outward MCP direction — Clay as a tool usable from ChatGPT/Claude/Glean. Adding inward custom MCP content there would confuse the two distinct features (the existing FAQ in that doc even explicitly says "There is no generic Clay MCP server URL to enter manually," which would contradict a custom MCP server section). Not the right home.ai-in-clay.md: has a single bullet "MCP (Model Context Protocol) server support when using your own keys" with no guidance — this is a general overview doc, not the right place for step-by-step Claygent configuration; adding a full section here would bury it away from where users actually configure their agents.access-settings-for-connections.md: covers admin permission controls for workspace connections — wrong audience (admins managing access, not users building agents) and wrong context.claygent-builder.mdis the canonical Claygent configuration reference and already contains the sibling sections (web search, find contacts/jobs, model selection) this new section joins naturally.Source link(s)
apps/frontend/src/components/AgentPlayground/Sections/AgentPlaygroundToolsSection.tsx:360(standalone, no flag gate) andapps/frontend/src/components/AISettingsEditor/Sections/MCPSettingsSection.tsx:184(table-embedded, Eppo-gated). Enterprise live; self-serve beta opt-in (confirmed Apr 7, 2026 #team-rep-tools Slack thread).api_key?atlibs/shared/src/actions/use-ai/mcp-servers.ts:96-100; corrected in doc to "optionally add an API key."Uncertainties
None. Feature existence, availability (Enterprise live / self-serve beta), and configuration fields all verified against code (verifier sub-agent) and Slack.
Related observations
ai-in-clay.md:79has a bare bullet "MCP (Model Context Protocol) server support when using your own keys" — adding a cross-link to the newclaygent-builder.mdsection would improve discoverability, but that's a low-priority follow-up outside this PR's scope.