Skip to content

Conversation

arturl
Copy link
Member

@arturl arturl commented Oct 4, 2025

Blog post announcing Remote MCP server and changes in the docs.

@arturl arturl changed the title Remote MCP - doc initial change Blog post and documentation changes for Remote MCP Oct 4, 2025
@pulumi-bot
Copy link
Collaborator

@pulumi-bot
Copy link
Collaborator

@pulumi-bot
Copy link
Collaborator

@pulumi pulumi deleted a comment from claude bot Oct 4, 2025
@arturl
Copy link
Member Author

arturl commented Oct 4, 2025

@claude review this PR for technical accuracy and content.

@pulumi-bot
Copy link
Collaborator

@pulumi-bot
Copy link
Collaborator

@pulumi pulumi deleted a comment from claude bot Oct 6, 2025
@arturl arturl marked this pull request as ready for review October 6, 2025 14:20
@arturl
Copy link
Member Author

arturl commented Oct 6, 2025

@claude review this PR for technical accuracy and content.

Copy link
Contributor

claude bot commented Oct 6, 2025

Claude finished @arturl's task —— View job


PR Review: Remote MCP Changes

Reviewing this PR for technical accuracy and content quality.

Tasks

  • Read all changed files
  • Review new blog post for technical accuracy
  • Review documentation changes for technical accuracy
  • Check content quality and clarity
  • Verify style guide compliance
  • Post comprehensive review feedback

Technical accuracy

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

Strengths:

  • Clear explanation of the evolution from local to remote MCP server
  • Good technical details about OAuth authentication flow
  • Excellent real-world Neo examples with concrete use cases
  • Well-structured progression from discovery → code generation → autonomous automation

Issues:

  1. Line 27 - Inconsistent note formatting. The style guide doesn't mention using > blockquotes for notes. According to STYLE-GUIDE.md, notes should use the {{% notes type="..." %}} shortcode. Current text:

    > **Note:** The local MCP server continues to be available...

    Should be:

    {{% notes type="info" %}}
    The local MCP server continues to be available and fully supported for developers who prefer local tooling or need offline capabilities.
    {{% /notes %}}
  2. Lines 117-118 - Formatting inconsistency. The bold text example should not be bolded as it's meant to be a user prompt, not emphasis. Consider using regular text or code formatting instead.

  3. Line 102 - The description says Neo is "an AI that ships infrastructure changes autonomously" but this might be misleading since Neo still requires human approval for PRs (as mentioned in line 113 "Human-in-the-loop"). Consider clarifying that Neo prepares and proposes changes autonomously.

  4. Technical accuracy check needed: Can you confirm that the Remote MCP Server at https://mcp.ai.pulumi.com/mcp is actually live and accessible? This is crucial for the blog post announcement.

Documentation (content/docs/iac/using-pulumi/mcp-server/index.md)

Strengths:

  • Comprehensive coverage of all supported AI assistants
  • Detailed tool documentation with clear descriptions
  • Good troubleshooting section
  • Proper alias configured for the URL migration (/docs/iac/using-pulumi/mcp-server/)

Issues:

  1. Line 14 - The alias list is actually correct (it preserves the old URL path). Good job on this.

  2. Line 17 - Good update to mention Neo integration upfront.

  3. Line 110 - Windsurf configuration format looks different from other assistants. Can you verify this is the correct format? Other assistants use transport and url fields, but Windsurf uses serverUrl. Is this confirmed correct for Windsurf?

  4. Line 163 - The deploy-to-aws tool is listed, but there's no explanation of what "automatically analyzes your application files" means. Does it scan the directory? Does it require specific file types? This needs clarification.

Modified blog post (content/blog/mcp-server-ai-assistants/index.md)

Changes:

  • Updated Cursor installation from local npm package to remote server URL ✅
  • Updated link text from "visiting the following link" to "clicking the following button" (more accurate) ✅
  • Removed screenshot of Cursor MCP settings validation (presumably outdated with remote setup) ✅
  • Updated link to MCP docs from absolute to relative URL ✅

These changes look good and align with the remote MCP migration.


Content quality and clarity

Blog post strengths:

  • Excellent narrative structure with clear value propositions
  • Strong opening that contextualizes the evolution
  • Real-world examples are specific and compelling
  • "Real-World Workflow" section provides concrete understanding

Documentation strengths:

  • Comprehensive AI assistant coverage
  • Clear step-by-step instructions
  • Excellent examples section with realistic use cases
  • Good balance between reference and tutorial content

Suggestions:

  1. Blog post line 49 - "Enter your Pulumi Access Token (which is validated server-side)" - Consider adding a security note about token handling/storage. Users might be concerned about entering tokens in a browser popup.

  2. Documentation line 229 - "Delegate to Neo for tasks that require:" - This list is good, but consider adding an example of what NOT to delegate to Neo (e.g., simple queries, one-off resource lookups).

  3. Both files - The OAuth flow description is mentioned but could benefit from a note about token expiration/refresh. Do users need to re-authenticate periodically?


Style guide compliance

Headings: ✅ All correct

  • Blog H1: "Announcing Pulumi Remote MCP Server" (Title Case) ✅
  • Blog H2s: "The Evolution of Pulumi MCP", "Why Remote MCP?" etc. (Title Case - appropriate for blog post) ✅
  • Docs H1: "Pulumi Model Context Protocol server" (in frontmatter) ✅
  • Docs H2+: Sentence case ✅

Lists: ✅ The ordered lists don't all use 1. format, but most lists in this content are unordered, which is appropriate.

Capitalization: ✅ Generally good. Proper nouns capitalized correctly (Pulumi, Neo, Claude, Cursor, etc.). Common nouns like "stack" are lowercased. ✅

Links: ✅ Descriptive link text throughout, no "click here" or vague references.

Tone: ✅ Professional and clear, avoids "easy" or "simple".

Line breaks: ⚠️ Some paragraphs could be shortened for better readability (see blog lines 104-113, which is a long 6-bullet list that could be broken up), but overall acceptable.


Migration checklist

  • Old single-file docs replaced with page bundle (to support images)
  • Alias configured correctly in new location
  • Old file deleted
  • Images added to bundle directory
  • Blog post updated with new remote MCP link
  • New blog post created announcing remote MCP
  • Meta image added for new blog post

Summary

This PR successfully migrates the MCP documentation to support the Remote MCP Server launch. The technical content is accurate and comprehensive, with excellent real-world examples. The main issues are:

  1. Critical: Verify the remote MCP server URL is live before merging
  2. Style: Convert blockquote note to proper notes shortcode (line 27 of blog post)
  3. Clarification needed: Windsurf config format, deploy-to-aws tool behavior
  4. Minor: Consider security note about token handling in OAuth flow

The content is well-written, properly structured, and follows the style guide. Great job on the comprehensive documentation and compelling blog post! 🎉


Job Run | Branch: arturl/remote-mcp

Copy link
Contributor

claude bot commented Oct 6, 2025

Pull Request Review

Thank you for this comprehensive update on the Remote MCP Server! Overall, this is strong content with good structure and clear explanations. I've identified several issues that need attention before merging.


Critical Issues

1. Typo in PR description

Issue: "Changs for remote MCP" should be "Changes for remote MCP"

2. Missing newline at end of file

File: content/blog/remote-mcp-server/index.md (line 194)
Issue: File must end with a newline per repository standards.

3. Incomplete file in documentation

File: content/docs/iac/using-pulumi/mcp-server/index.md (line 85)
Issue: The Claude Desktop configuration section appears truncated in the diff. Please verify the full file was committed correctly.


Style and Content Issues

4. Vague language

File: content/blog/remote-mcp-server/index.md (lines 21, 25)
Issue: Phrases like "The adoption and feedback...has been positive" are vague. Be specific about metrics or concrete benefits if possible.

5. Avoid "simply"

File: content/blog/remote-mcp-server/index.md (line 35)
Issue: "you simply configure" — Avoid words like "simply" per STYLE-GUIDE.md as they judge difficulty.
Suggestion: "you configure your AI assistant"

6. Passive voice

File: content/blog/remote-mcp-server/index.md (line 49)
Issue: "which is validated server-side" — Use active voice.
Suggestion: "which the server validates"

7. Run-on sentence

File: content/blog/remote-mcp-server/index.md (line 154)
Issue: Long sentence could be split for clarity.

8. Inconsistent code formatting

File: content/blog/remote-mcp-server/index.md (lines 65-67, 71-72)
Issue: Tool names formatted as code inconsistently throughout document.

9. Repetitive structure

File: content/blog/remote-mcp-server/index.md (lines 120-147)
Issue: Three consecutive examples use the same "Neo will:" list structure. Vary formatting for readability.

10. Unclear instructions

File: content/docs/iac/using-pulumi/mcp-server/index.md (lines 67-71)
Issue: Numbered list describes "After adding configuration" but some steps may happen during setup. Clarify sequence.


Recommendations

11. Verify links

Please confirm these internal links work:

  • /docs/pulumi-cloud/neo/
  • /docs/iac/using-pulumi/mcp-server/
  • /docs/pulumi-cloud/cloud-rest-api/

12. Verify image

File: content/docs/iac/using-pulumi/mcp-server/index.md (line 88)
Issue: Verify claude-desktop-setup.png exists and displays correctly.

13. Alias correctly added

Good work: The alias for the moved file is correctly added (line 13-14).


Summary

Must Fix:

Strongly Recommended:

Overall, this is excellent content that will be helpful for users. Once the critical issues are addressed, this will be ready to merge!

@kramhuber kramhuber requested a review from CamSoper October 7, 2025 00:54
Copy link
Contributor

@kramhuber kramhuber left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I only reviewed the blog post. I'll defer the docs to @CamSoper

@pulumi-bot
Copy link
Collaborator

Copy link
Contributor

@CamSoper CamSoper left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No notes, LGTM!

@arturl arturl merged commit c985856 into master Oct 7, 2025
15 checks passed
@arturl arturl deleted the arturl/remote-mcp branch October 7, 2025 16:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants