feat(mcp-cloudflare): enhance Remote/stdio setup guides (#536)

- Add constraints and scopes guidance for stdio
- Deprecate SSE usage behind accordion with limitations
- UI tweaks: headings, margins, accordion components

chore(claude): enable co-authored-by and tighten tool allowlist

Author: dcramer

.claude/settings.json

@@ -17,8 +17,7 @@
       "Bash(gh pr checks:*)",
       "Bash(gh pr view:*)",
       "Bash(gh run view:*)",
-      "Bash(git status:*)",
-      "mcp__sentry__*"
+      "Bash(git status:*)"
     ],
     "deny": []
   },
@@ -36,6 +35,6 @@
     ]
   },
   "enableAllProjectMcpServers": true,
-  "includeCoAuthoredBy": false,
+  "includeCoAuthoredBy": true,
   "enabledMcpjsonServers": ["sentry"]
 }

packages/mcp-cloudflare/src/client/components/fragments/remote-setup.tsx

@@ -1,9 +1,15 @@
-import { Accordion } from "../ui/accordion";
+import {
+  Accordion,
+  AccordionContent,
+  AccordionItem,
+  AccordionTrigger,
+} from "../ui/accordion";
 import CodeSnippet from "../ui/code-snippet";
 import SetupGuide from "./setup-guide";
 import { Prose } from "../ui/prose";
 import { NPM_REMOTE_NAME } from "@/constants";
 import { Button } from "../ui/button";
+import { Heading } from "../ui/base";
 
 const mcpServerName = import.meta.env.DEV ? "sentry-dev" : "sentry";
 
@@ -42,44 +48,47 @@ export default function RemoteSetup() {
 
   return (
     <>
-      <Prose>
+      <Prose className="mb-6">
         <p>
           If you've got a client that natively supports the current MCP
           specification, including OAuth, you can connect directly.
         </p>
         <CodeSnippet snippet={endpoint} />
-        {/* Hidden for now - constraints not working correctly
         <p>
           <strong>Organization and Project Constraints:</strong> You can
-          optionally constrain your MCP session to specific organizations or
-          projects by including them in the URL path:
+          optionally constrain your MCP session to a specific organization and
+          project by including them in the URL path:
         </p>
         <ul>
           <li>
-            <code>{endpoint}/:organization</code> - Restricts session to a
+            <code>{endpoint}/:organization</code> — Restricts the session to a
             specific organization
           </li>
           <li>
-            <code>{endpoint}/:organization/:project</code> - Restricts session
-            to a specific organization and project
+            <code>{endpoint}/:organization/:project</code> — Restricts the
+            session to a specific organization and project
           </li>
         </ul>
-        */}
-        <p>
-          Sentry's MCP server supports both the SSE and HTTP Streaming
-          protocols, and will negotiate based on your client's capabilities. If
-          for some reason your client does not handle this well you can pin to
-          the SSE-only implementation with the following URL:
-        </p>
-        <CodeSnippet snippet={sseEndpoint} />
-        <p>
-          <strong>Note:</strong> SSE endpoints do not support organization and
-          project constraints. Use the main endpoint above if you need scoped
-          access.
-        </p>
-
-        <h3>Integration Guides</h3>
+        <Accordion type="single" collapsible>
+          <AccordionItem value="sse-deprecated">
+            <AccordionTrigger>SSE support is deprecated</AccordionTrigger>
+            <AccordionContent>
+              <p className="mb-2">
+                New clients should use HTTP Streaming via the main
+                <code>/mcp</code> endpoint. If you must use the SSE-only
+                implementation, use the following URL:
+              </p>
+              <CodeSnippet noMargin snippet={sseEndpoint} />
+              <p className="mt-2">
+                <strong>Limitations:</strong> SSE endpoints do not support
+                organization or project constraints. Use the main
+                <code>/mcp</code> endpoint if you need scoped access.
+              </p>
+            </AccordionContent>
+          </AccordionItem>
+        </Accordion>
       </Prose>
+      <Heading as="h3">Integration Guides</Heading>
       <Accordion type="single" collapsible>
         <SetupGuide id="cursor" title="Cursor">
           <Button
@@ -119,6 +128,10 @@ export default function RemoteSetup() {
                 )}
               />
             </li>
+            <li>
+              Optional: To use the service with <code>cursor-agent</code>:
+              <CodeSnippet noMargin snippet={`cursor-agent mcp login sentry`} />
+            </li>
           </ol>
         </SetupGuide>
 
@@ -135,6 +148,10 @@ export default function RemoteSetup() {
               This will trigger an OAuth authentication flow to connect Claude
               Code to your Sentry account.
             </li>
+            <li>
+              You may need to manually authenticate if it doesnt happen
+              automatically, which can be doe via <code>/mcp</code>.
+            </li>
           </ol>
           <p>
             <small>

packages/mcp-cloudflare/src/client/components/fragments/stdio-setup.tsx

@@ -1,5 +1,5 @@
 import { Accordion } from "../ui/accordion";
-import { Link } from "../ui/base";
+import { Heading, Link } from "../ui/base";
 import CodeSnippet from "../ui/code-snippet";
 import SetupGuide from "./setup-guide";
 import { NPM_PACKAGE_NAME, SCOPES } from "../../../constants";
@@ -22,7 +22,7 @@ export default function StdioSetup() {
 
   return (
     <>
-      <Prose>
+      <Prose className="mb-6">
         <p>
           The stdio client is made available on npm at{" "}
           <Link href={`https://www.npmjs.com/package/${NPM_PACKAGE_NAME}`}>
@@ -64,8 +64,47 @@ export default function StdioSetup() {
           sentry.io). If you wish to disable it, pass <code>--sentry-dsn=</code>{" "}
           with an empty value.
         </p>
-        <h3>Integration Guides</h3>
+
+        <p>
+          <strong>Constraints (stdio only):</strong> Restrict all tool calls to
+          a specific organization, and optionally to a project within that
+          organization using CLI flags.
+        </p>
+        <CodeSnippet
+          snippet={[
+            `${mcpStdioSnippet}`,
+            "--access-token=sentry-user-token",
+            "--host=sentry.io",
+            "--organization-slug=sentry",
+            "--project-slug=mcp-server",
+          ].join(" \\\n  ")}
+        />
+        <p>
+          You can provide just <code>--organization-slug</code> to scope to an
+          org, or include <code>--project-slug</code> to scope to a single
+          project within that org.
+        </p>
+
+        <p>
+          <strong>Scopes:</strong> The default configuration grants read-only
+          access (listed above). To grant full access to all available tools use
+          <code>--all-scopes</code>.
+        </p>
+        <CodeSnippet
+          snippet={[
+            `${mcpStdioSnippet}`,
+            "--access-token=sentry-user-token",
+            "--host=sentry.io",
+            "--all-scopes",
+          ].join(" \\\n  ")}
+        />
+        <p>
+          For more options and details, run{" "}
+          <code>npx @sentry/mcp-server@latest --help</code> — there are many
+          flags available.
+        </p>
       </Prose>
+      <Heading as="h3">Integration Guides</Heading>
       <Accordion type="single" collapsible>
         <SetupGuide id="cursor" title="Cursor">
           <ol>