guides: add AI Integration section with MCP-for-agents page - #1
Open
deliciousmonster wants to merge 1 commit into
Open
guides: add AI Integration section with MCP-for-agents page#1deliciousmonster wants to merge 1 commit into
deliciousmonster wants to merge 1 commit into
Conversation
Customer-facing how-to for the MCP surface that every @export-ed table exposes for free. Covers the auto-generated tools/resources/ prompts, @export(mcp: false) opt-out, @access(public: [read]) for read-only agents, client-side wiring for Claude Desktop / Cursor / Claude Code, and a curl smoke-test. Wire-level JSON-RPC details stay in reference/api/operations.md. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
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.
Summary
guides/SUMMARY.mdwith a single starter page,guides/ai/mcp.md.reference/api/operations.md(which is the wire-spec reference): what every `@export`-ed table exposes for free, how to opt out with `@export(mcp: false)`, how to combine with `@access(public: [read])` for read-only agents, and how to wire Claude Desktop / Cursor / Claude Code.Why
docs/guides/in the platform repo had four guides not mirrored in yeti-documentation:building.md,development.md,testing.md, andmcp.md. The first three are contributor-facing (build-from-source, workspace layout, platform test harness) and correctly excluded.mcp.mdis customer-facing — an app developer needs to know their tables already speak MCP and how to connect a client — so it belongs here. This PR closes that gap with a guide-shaped doc (~200 lines, code-forward) rather than reproducing the 660-line in-repo file verbatim.Test plan
🤖 Generated with Claude Code