docs: surface MCP and agent skills for coding agents#3093
Conversation
Add a "Using coding agents with Estuary" hub plus an "Agent skills" page in Advanced Features, and cross-link them with the existing MCP page. flowctl setup now points users to both. Skills content is drawn from the public estuary/agent-skills repo. Stage 1 (least disruption): cluster the three pages at the top of Advanced Features; no existing URLs change. Stage 2 (pending team consensus) would promote these into a dedicated top-level Coding Agents section.
|
🚀 Preview deployed to https://docs.estuary.dev/pr-preview/pr-3093/ 📄 Changed pages: |
|
Hey @aeluce we've had some positive feedback on the MCP and skills, this is making it a bit more connected/prominent. In a subsequent PR I'd like to have a top level 'Coding Agents' page that points to flowctl, MCP, and skills (especially the setup skill), so people can go down that route without having to dive too far into our documentation if that's their desired approach. What do you think? |
| sidebar_position: 3 | ||
| --- | ||
|
|
||
| # Agent Skills |
There was a problem hiding this comment.
There is already an Agent Skills page here: https://docs.estuary.dev/guides/agent-skills/
It's what the dashboard "Agent Skills" button links to.
See also conversation from #2961 for additional notes. Re: yes, we could bundle the MCP integration and agent skills pages under one subsection to make the related pages easier to find. Maybe we could keep it under /features for now. /guides is getting a little unwieldy and I'm not convinced we'd have enough content for a top-level section.
| sidebar_position: 1 | ||
| --- | ||
|
|
||
| # Using Coding Agents with Estuary |
There was a problem hiding this comment.
Is this page useful as-is? It mostly seems to reiterate information from other places in docs.
|
|
||
| The token will expire after a predetermined duration. Repeat this process to re-authenticate. | ||
|
|
||
| ## Drive flowctl from an AI coding agent |
There was a problem hiding this comment.
This section sounds a little "marketing"-y. My suggestion would be to tone down the hype and simply present it as an alternate option. Something like:
You can also run flowctl commands via AI coding assistants to build and maintain pipelines.
- **Agent skills** provide steps to run common workflows, like creating connectors or
troubleshooting pipelines.
- An **MCP integration** provides your assistant additional context on using flowctl by
connecting to Estuary's documentation.
2 participants
What
Surface Estuary's MCP integration and agent skills more prominently for users who currently only hear about flowctl.
features/agent-skills.md) — catalog, install methods, usage. Content drawn from the public estuary/agent-skills repo.features/using-coding-agents.md) — end-to-end setup walkthrough for flowctl + MCP + skills.Approach: stage 1 (least disruption)
These three pages are clustered at the top of Advanced Features (positions 1–3). The existing MCP page stays at
/features/mcp-integration/, so no URLs change and nothing external breaks (the public agent-skills README links to that page). The only other edits bump three existing pages'sidebar_position(time-travel, task-shards, logs-stats) to make room.Proposed stage 2 (needs consensus — @Emily)
Promote these into a dedicated top-level Coding Agents section in the left nav, consolidating the hub + MCP + skills there. That moves the MCP page's URL, so it needs a redirect and sign-off. Holding until we're aligned on IA.
Notes
estuary-flowctl-setup) only covers flowctl, so the hub/skills content came from the public agent-skills repo instead./getting-started/installation/, which is actually the cloud-storage page. The real flowctl setup is/guides/get-started-with-flowctl/. Worth fixing in that repo.