[Access] Add Terraform configuration guide for MCP server portals#31004
Open
kennyj42 wants to merge 1 commit into
Open
[Access] Add Terraform configuration guide for MCP server portals#31004kennyj42 wants to merge 1 commit into
kennyj42 wants to merge 1 commit into
Conversation
Collaborator
Author
|
@GreenStage anything else you think we should add for this? Do we document doing the OAuth for servers anywhere? |
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
3 participants
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 this PR does
Adds a new 'Configure via Terraform' section to the MCP server portals page covering:
cloudflare_zero_trust_access_mcp_server_portalresourcecloudflare_dns_recordCNAME togateway.agents.cloudflare.comWhy
There is currently zero Terraform coverage for MCP portals. A customer (usespeak.dev) hit 522 errors because the Terraform provider silently skips CNAME creation. This was filed as MCP-108. Internal engineers have also been confused by this gap.
The CNAME must point to
gateway.agents.cloudflare.comand be proxied through Cloudflare.