Blog post and documentation changes for Remote MCP

[arturl]

Changs for remote MCP

[pulumi-bot]

Your site preview for commit b2acc2f is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-16168-b2acc2f6.s3-website.us-west-2.amazonaws.com.

[pulumi-bot]

Your site preview for commit 471bf06 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-16168-471bf06b.s3-website.us-west-2.amazonaws.com.

[pulumi-bot]

Your site preview for commit 8714e49 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-16168-8714e497.s3-website.us-west-2.amazonaws.com.

[arturl]

@claude review this PR for technical accuracy and content.

[claude]

Claude finished @arturl's task —— View job

---

Technical Review Complete

I've completed a comprehensive review of this PR for technical accuracy and content. Here are my findings:

---

✅ Overall Assessment

The PR successfully introduces Remote MCP Server documentation and updates existing content. The technical accuracy is solid, and the content is well-structured and informative.

---

🔴 Critical Issues

1. Missing alias for moved documentation file

Location: content/docs/iac/using-pulumi/mcp-server/index.md

The documentation file was moved from content/docs/iac/using-pulumi/mcp-server.md to content/docs/iac/using-pulumi/mcp-server/index.md, but no aliases field was added to the frontmatter.

Required fix: Add this to the frontmatter:

aliases:
- /docs/iac/using-pulumi/mcp-server/

Why this matters: Without the alias, any existing links to the old URL will break. This is explicitly required by AGENTS.md.

2. Broken link in new blog post

Location: content/blog/remote-mcp-server/index.md:41

For instructions on how to configure different AI assistants, see [Pulumi MCP Server](docs/iac/using-pulumi/mcp-server).

Issue: Missing leading / in the link path.

Should be:

For instructions on how to configure different AI assistants, see [Pulumi MCP Server](/docs/iac/using-pulumi/mcp-server).

---

🟡 Style Guide Issues

3. Inconsistent heading capitalization in new blog post

Location: content/blog/remote-mcp-server/index.md

Several H3 headings use Title Case instead of Sentence case:

• Line 33: ### Zero Local Setup, Universal Access → should be ### Zero local setup, universal access
• Line 43: ### Centralized Authentication & Secrets → should be ### Centralized authentication & secrets
• Line 58: ### Discover and Query Infrastructure → should be ### Discover and query infrastructure
• Line 80: ### Generate Infrastructure Code → should be ### Generate infrastructure code
• Line 100: ### Autonomous Infrastructure with Pulumi Neo → should be ### Autonomous infrastructure with Pulumi Neo

Per STYLE-GUIDE.md: "H2 and deeper: Sentence case"

---

🟢 Positive Observations

1. Good content structure - Both blog posts are well-organized with clear sections
2. Technical accuracy - The descriptions of MCP functionality, Neo integration, and tools are accurate
3. Proper ordered lists - All ordered lists correctly use 1. for each item
4. Good use of code formatting - Inline code, URLs, and tool names are properly formatted
5. Appropriate callouts - The "Note" callout in the remote-mcp-server blog uses the correct format
6. Clear migration messaging - Good explanation of why Remote MCP exists alongside the local version
7. Helpful examples - The documentation includes practical examples and use cases

---

📝 Minor Suggestions (Optional)

Documentation file (mcp-server/index.md)

1. Line 6: The meta_image uses the generic docs image. Consider using a custom image like the blog posts do.

2. Line 168: The prompt "convert-terraform-to-typescript" is mentioned but might be worth expanding on how users can access prompts vs tools in their AI assistants.

New blog post (remote-mcp-server/index.md)

1. Line 10: Consider changing tag MCP to lowercase mcp to match the ai tag format (though this depends on your tagging conventions).

2. Line 156: The workflow example is excellent and very helpful for understanding the user experience.

---

📊 Content Accuracy Review

Remote MCP Server capabilities: ✅ Accurate

• Correctly describes OAuth authentication flow
• Tool descriptions match implementation
• Neo integration details are accurate

Migration from local to remote: ✅ Clear

• Explains rationale well
• Notes that local version remains supported
• Benefits are well-articulated

Setup instructions: ✅ Comprehensive

• Covers multiple AI assistants
• Configuration examples are correct
• Authentication flow is accurate

---

Summary

Must fix before merge:

1. Add aliases field to moved documentation file
2. Fix broken link in blog post (missing leading /)
3. Change H3 headings to sentence case in new blog post

Style improvements recommended:

• Maintain consistent heading capitalization throughout

The content is technically accurate and well-written. Once the critical issues are addressed, this will be a solid addition to the documentation.

---

Job: https://github.com/pulumi/docs/actions/runs/
Branch: arturl/remote-mcp

[pulumi-bot]

Your site preview for commit 94aa0e2 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-16168-94aa0e2e.s3-website.us-west-2.amazonaws.com.

[pulumi-bot]

Your site preview for commit d133bf4 is ready! 🎉

http://www-testing-pulumi-docs-origin-pr-16168-d133bf4d.s3-website.us-west-2.amazonaws.com.