feat(connect-studio): Connect Studio modal for IDE MCP configuration#2765
Open
feat(connect-studio): Connect Studio modal for IDE MCP configuration#2765
Conversation
Contributor
Release OptionsShould a new version be published when this PR is merged? React with an emoji to vote on the release type:
Current version: Deployment
|
Contributor
🧪 BenchmarkShould we run the Virtual MCP strategy benchmark for this PR? React with 👍 to run the benchmark.
Benchmark will run on the next push after you react. |
![cubic-dev-ai[bot]](https://avatars.githubusercontent.com/in/1082092?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
3 issues found across 4 files
Prompt for AI agents (unresolved issues)
Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.
<file name="apps/mesh/src/web/components/connect-studio/connect-studio-modal.tsx">
<violation number="1" location="apps/mesh/src/web/components/connect-studio/connect-studio-modal.tsx:43">
P3: Local environment detection misses IPv6 loopback (`::1`), which can hide the Connect action during local development.</violation>
</file>
<file name="apps/mesh/src/api/routes/decopilot/routes.ts">
<violation number="1" location="apps/mesh/src/api/routes/decopilot/routes.ts:327">
P1: Use `getUserId(ctx)` instead of `ctx.auth?.user?.id` — this will incorrectly return 401 for requests authenticated via API key. The DELETE endpoint already uses `getUserId(ctx)` correctly.
(Based on your team's feedback about using getUserId(ctx) for user-based or API-key authentication.) [FEEDBACK_USED]</violation>
<violation number="2" location="apps/mesh/src/api/routes/decopilot/routes.ts:343">
P1: Use `getUserId(ctx)` instead of `ctx.auth?.user?.id` — under API-key auth, this returns `undefined`, causing a spurious 401 and embedding `"undefined"` in the created API key name.
(Based on your team's feedback about using getUserId(ctx) for user-based or API-key authentication.) [FEEDBACK_USED]</violation>
</file>
Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.
| app.post("/:org/decopilot/connect-studio", async (c) => { | ||
| const ctx = c.get("meshContext"); | ||
| const organization = ensureOrganization(c); | ||
| const userId = ctx.auth?.user?.id; |
Contributor
There was a problem hiding this comment.
P1: Use getUserId(ctx) instead of ctx.auth?.user?.id — under API-key auth, this returns undefined, causing a spurious 401 and embedding "undefined" in the created API key name.
(Based on your team's feedback about using getUserId(ctx) for user-based or API-key authentication.)
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At apps/mesh/src/api/routes/decopilot/routes.ts, line 343:
<comment>Use `getUserId(ctx)` instead of `ctx.auth?.user?.id` — under API-key auth, this returns `undefined`, causing a spurious 401 and embedding `"undefined"` in the created API key name.
(Based on your team's feedback about using getUserId(ctx) for user-based or API-key authentication.) </comment>
<file context>
@@ -192,6 +192,349 @@ export function createDecopilotRoutes(deps: DecopilotDeps) {
+ app.post("/:org/decopilot/connect-studio", async (c) => {
+ const ctx = c.get("meshContext");
+ const organization = ensureOrganization(c);
+ const userId = ctx.auth?.user?.id;
+ if (!userId) {
+ throw new HTTPException(401, { message: "Authentication required" });
</file context>
Suggested change
| const userId = ctx.auth?.user?.id; | |
| const userId = getUserId(ctx); |
|
|
||
| app.get("/:org/decopilot/connect-studio/status", async (c) => { | ||
| const ctx = c.get("meshContext"); | ||
| if (!ctx.auth?.user?.id) { |
Contributor
There was a problem hiding this comment.
P1: Use getUserId(ctx) instead of ctx.auth?.user?.id — this will incorrectly return 401 for requests authenticated via API key. The DELETE endpoint already uses getUserId(ctx) correctly.
(Based on your team's feedback about using getUserId(ctx) for user-based or API-key authentication.)
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At apps/mesh/src/api/routes/decopilot/routes.ts, line 327:
<comment>Use `getUserId(ctx)` instead of `ctx.auth?.user?.id` — this will incorrectly return 401 for requests authenticated via API key. The DELETE endpoint already uses `getUserId(ctx)` correctly.
(Based on your team's feedback about using getUserId(ctx) for user-based or API-key authentication.) </comment>
<file context>
@@ -192,6 +192,349 @@ export function createDecopilotRoutes(deps: DecopilotDeps) {
+
+ app.get("/:org/decopilot/connect-studio/status", async (c) => {
+ const ctx = c.get("meshContext");
+ if (!ctx.auth?.user?.id) {
+ throw new HTTPException(401, { message: "Authentication required" });
+ }
</file context>
Suggested change
| if (!ctx.auth?.user?.id) { | |
| if (!getUserId(ctx)) { |
| return ( | ||
| typeof window !== "undefined" && | ||
| (window.location.hostname === "localhost" || | ||
| window.location.hostname === "127.0.0.1") |
Contributor
There was a problem hiding this comment.
P3: Local environment detection misses IPv6 loopback (::1), which can hide the Connect action during local development.
Prompt for AI agents
Check if this issue is valid — if so, understand the root cause and fix it. At apps/mesh/src/web/components/connect-studio/connect-studio-modal.tsx, line 43:
<comment>Local environment detection misses IPv6 loopback (`::1`), which can hide the Connect action during local development.</comment>
<file context>
@@ -0,0 +1,379 @@
+ return (
+ typeof window !== "undefined" &&
+ (window.location.hostname === "localhost" ||
+ window.location.hostname === "127.0.0.1")
+ );
+}
</file context>
vibegui
force-pushed
the
feat/connect-studio
branch
3 times, most recently
from
685f855 to
01fbe89
Compare
6 tasks
Add a "Connect Studio" sidebar button that opens a modal allowing users to connect their Deco Studio as an MCP server to Claude Code, Cursor, or Codex. Supports one-click auto-configuration when running locally and copyable config snippets for hosted deployments. Each connection creates a per-user API key with full access to the studio's management MCP endpoint. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
vibegui
force-pushed
the
feat/connect-studio
branch
from
01fbe89 to
0daa3db
Compare
Replace placeholder values with actual origin/org-id in config snippets. Add "Generate API Key" button that creates a personal token and injects it into the snippet so users can copy a ready-to-use config. Support token-only mode in the backend for all targets. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
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
1 participant
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.
Summary
~/.cursor/mcp.json), and Codex (writes~/.codex/config.toml)Files Changed
apps/mesh/src/api/routes/decopilot/routes.ts— Connect Studio backend routes (GET status, POST connect, DELETE disconnect)apps/mesh/src/web/components/connect-studio/connect-studio-modal.tsx— New modal component with IDE tabsapps/mesh/src/web/components/sidebar/footer/inbox.tsx— Sidebar button triggerapps/mesh/src/web/lib/query-keys.ts— Query key for status cachingTest plan
bun run devclaude mcp get deco-studioworks~/.cursor/mcp.json~/.codex/config.toml🤖 Generated with Claude Code
Summary by cubic
Adds a Connect Studio modal and backend routes to connect Deco Studio as an MCP server in Claude Code, Cursor, and Codex. Enables one-click local setup, per-user API tokens, live connection status (with Claude auth), and ready-to-paste config with real origin/org values.
connect-studio-status.GET /:org/decopilot/connect-studio/status,POST /:org/decopilot/connect-studio,DELETE /:org/decopilot/connect-studio(auth required; status reports IDE connection and Claude auth; disconnect removes IDE config).claude mcp add-json --scope userafter removing any existing entry; Cursor merges~/.cursor/mcp.json; Codex replaces the section in~/.codex/config.toml. Falls back to copyable config if CLI/write fails.Authorization,x-org-id, and for Claude Codex-mesh-client.Written for commit 3326034. Summary will update on new commits.