Add Workers development and debugging tool discovery - #185
Draft
irvinebroque wants to merge 3 commits into
Draft
irvinebroque wants to merge 3 commits into
irvinebroque wants to merge 3 commits into
Conversation
irvinebroque
marked this pull request as draft
September 8, 2026 04:42
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.


Agents need to know which Cloudflare development and debugging tools are available and how to discover their operations. Add
workers-development, a concise capability map covering Wrangler and Cloudflare Vite development, Local Explorer data and telemetry APIs, production observability, and preview deployment discovery. Register it in the README and Cloudflare troubleshooting route.Local guidance starts with the dev server's route hints and examples, extracting relevant OpenAPI operations when needed. It includes discovery when a hint is absent and a version/docs fallback when capabilities are missing. Production guidance routes through the bundled Cloudflare MCP server's
searchandexecutetools to telemetry keys, values, and queries, including trace summaries. The optional Workers Observability MCP server andwrangler tailare alternative tools. Trace details and sampling remain discoverable through current schemas and docs.Add a short preview section to Wrangler covering command and account eligibility, the project build workflow, version uploads, and resource sharing. A locally executing Worker can use remote bindings, and a preview URL does not establish storage isolation.
Validation:
ok, so filtering only by an error column would have missed it.view: tracesfor distributed trace summaries. No production account data was queried.wrangler preview --helpconfirmed the command, naming options, and private-beta designation. No preview was deployed or account eligibility tested.quick_validate.pypassed for both changed skills;git diff --checkpassed. Temporary dev servers were stopped.These are direct capability smoke tests and a documentation/schema review, not an independent agent benchmark. They establish that the documented discovery paths work in the tested versions; they do not establish production permissions, coverage of every binding type, or preview deployment success.
Documentation gap: cloudflare/cloudflare-docs#31775 remains open, while the published Preview URLs page describes version uploads. Preview guidance checks current docs, installed support, and beta eligibility instead of copying the proposed configuration and isolation matrix. Sources include the linked Local Explorer, Observability, Workers Traces, real-time logs, and version URL documentation, the MCP README/tool implementation, and the live MCP OpenAPI schema.