Build: add Tiger CLI/MCP task, safety, and cookbook pages - #407
Conversation
Carves the "build" section out of the CLI/MCP docs umbrella (#375), picking up after get-started, reference, and learn already merged. Adds a "Build with Tiger CLI and MCP" sidebar group with three new pages (common tasks, agent best practices, and a cookbook adapted from timescale/pg-ai-cookbook), a DoWithAi callout sprinkled across the SQL task pages it applies to, and backfills the deferred cross-links into the already-merged get-started/learn pages. Every CLI command, MCP tool call, and SQL statement was verified live against a real Tiger Cloud service, which surfaced and fixed a few real issues: a hypertable created via the recommended WITH syntax already carries a default columnstore policy, so the cookbook's optimization recipe now removes it before adding a custom one; the read-replica guidance was pointing at the wrong feature (read-scaling replica sets instead of HA replicas, which is what `tiger db connect` actually offers to connect to); and the "read and advice oriented" framing around Tiger MCP's design/analysis skills didn't hold for the fork-testing step, since forking is itself blocked in read-only mode.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
✅ Checklist CompleteThank you for taking the time to properly review your PR! All checklist items are complete. |
manage-storage.mdx: enabling tiered storage and changing IOPS are Console-only (confirmed against the full CLI/MCP tool surface, no equivalent exists), so the callout was pointing readers at an agent workflow that doesn't exist for that part of the page. migrate-to-new-form.mdx: this procedure only applies to TimescaleDB v2.24 and earlier (removed in v2.25); Tiger Cloud runs 2.28.3, so no Cloud service can ever be in the affected state.
Askir
left a comment
There was a problem hiding this comment.
The best practice page looks good, although i wonder if we have a bit too many pages now with info spread out thin across them.
There is the build pages:
- common tasks (giving some sample commands)
- Best practices (this one)
- Cookbook (which contains some sample prompts)
The learn page about CLI and MCP which explains how they work.
The getting started pages with:
- More sample commands on the first page
- More install instructions on the second page and also the read only instructions
- A REST API guide (but under the CLi/MCP topic?)
And then the reference pages of course for both the CLI and the MCP.
That's 9 separate pages spread out across the navigation and linking to each other, but imo it's hard to get an overview over "everything CLI/MCP". Took me 10 minutes to even compose this comment. Then again maybe the github repo is the more natural entry point and these are just additional details so its fine. Just some thoughts.
Signed-off-by: Anastasiia Tovpeko <114177030+atovpeko@users.noreply.github.com>
|
Overall looks good! I think the replica piece is the only thing we should address before deploying. I agree with Jascha -- maybe in Q3 we can partner to flesh these out a bit more and help users get set up end-to-end with the CLI and MCP. |
Describe your changes
Carves the "build" section out of the CLI/MCP docs umbrella (#375), picking up after get-started, reference, and learn already merged. Adds a "Build with Tiger CLI and MCP" sidebar group with three new pages:
timescale/pg-ai-cookbook, with links to the full recipes on GitHub.Affected pages
/build/columnar-storage/setup-hypercore
/build/continuous-aggregates/compression-on-continuous-aggregates
/build/continuous-aggregates/create-a-continuous-aggregate
/build/continuous-aggregates/create-index
/build/continuous-aggregates/drop-data
/build/continuous-aggregates/refresh-policies
/build/data-management/create-and-manage-jobs
/build/data-management/data-retention/create-a-retention-policy
/build/data-management/example-downsample-and-compress
/build/data-management/example-generic-retention
/build/data-management/query-data/advanced-analytic-queries
/build/data-management/query-data/select
/build/data-management/write-data/delete
/build/data-management/write-data/insert
/build/data-management/write-data/update
/build/data-management/write-data/upsert
/build/examples/hybrid-search
/build/how-to/basic-compression
/build/how-to/your-first-hypertable
/build/tiger-cli-mcp/agent-best-practices
/build/tiger-cli-mcp/common-tasks
/build/tiger-cli-mcp/cookbook
/get-started/quickstart/mcp-cli
/get-started/quickstart/tiger-cli
/learn/tiger-cli-mcp
🧪 Component kitchen sink — check for visual regressions if you changed components, styles, or dependencies.
Related Issues
Checklist before requesting a review