Skip to content

refactor(mcp): cleanup auth and reorganize tools - #979

Merged
saddlepaddle merged 5 commits into
mainfrom
mcp-cleanup
Jan 27, 2026
Merged

saddlepaddle merged 5 commits into
mainfrom
mcp-cleanup

Conversation

@saddlepaddle

@saddlepaddle saddlepaddle commented Jan 26, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

  • Replace @vercel/mcp-adapter with mcp-handler package
  • Reorganize monolithic tools.ts (1126 lines) into domain folders per AGENTS.md co-location guidelines
  • Fix organization scope not being passed through OAuth consent flow
  • Add typed registerTool helper for cleaner tool registration
  • Simplify McpContext to only required fields (userId, organizationId)

Changes

Package & Config

  • Replace @vercel/mcp-adapter with mcp-handler
  • Add KV_URL to env validation and deployment workflows

Auth Simplification

  • Simplify auth.ts to just the McpContext interface
  • Streamline route.ts auth logic

Tool Reorganization

apps/api/src/lib/mcp/tools/
├── index.ts                 # Central registration
├── utils/
│   ├── register-tool.ts     # Typed helper
│   └── execute-on-device.ts # Device command utility
├── tasks/                   # Task domain tools
├── organizations/           # Org domain tools
└── devices/                 # Device domain tools

OAuth Scope Fix

Better Auth's consent endpoint doesn't accept scope in the body, so the organization scope selected on the consent screen was being ignored.

  • Add custom /oauth/add-org-scope endpoint that updates the verification value before consent
  • Update consent form to call this endpoint before submitting

Test plan

  • bun run lint:fix - passes (only expected warnings)
  • bun run typecheck - passes
  • bun test - 1193 pass, 7 skip
  • Manual test: MCP authentication works with organization scope

Summary by CodeRabbit

  • New Features

    • Device workspace management: create, delete, list, navigate, and switch workspaces on devices
    • Task management: create, update, delete, list, and view task details
    • Organization member listing and device discovery with online/offline status
    • OAuth consent flow: supports adding organization-scoped consent before submission
  • Refactor

    • Reworked MCP tooling into modular registrations and streamlined auth plumbing
  • Chores

    • Deployment workflows updated to propagate a new KV_URL runtime variable

✏️ Tip: You can customize this high-level summary in your review settings.

Better Auth's consent endpoint doesn't accept scope in the body, so the
organization scope selected on the consent screen was being ignored.

- Add custom /oauth/add-org-scope endpoint that updates the verification
  value with the organization scope before consent is processed
- Update consent form to call this endpoint before submitting consent
- Add KV_URL to env and deployment workflows for Redis connection
- Remove fallback logic that looked up a random organization
@coderabbitai

coderabbitai Bot commented Jan 26, 2026 •

Copy link
Copy Markdown
Contributor
📝 Walkthrough

Walkthrough

High-level changes: Added KV_URL env propagation in GH workflows; replaced @vercel/mcp-adapter with mcp-handler and reshaped MCP auth; removed legacy registerMcpTools and replaced with new modular tool registrations (many new tool modules and utils including executeOnDevice); added KV_URL to API env schema; added OAuth add-org-scope endpoint and consent-flow change.

Changes

Cohort / File(s) Summary of changes
Workflows
.github/workflows/deploy-preview.yml, .../deploy-production.yml
Added KV_URL secret to environment and passed it into Vercel CLI invocations (--env KV_URL=$KV_URL) across deploy jobs.
API env & deps
apps/api/src/env.ts, apps/api/package.json
Added KV_URL: z.string().url() to server environment schema; replaced @vercel/mcp-adapter with mcp-handler and added mcp-handler dependency.
MCP auth & route
apps/api/src/lib/mcp/auth.ts, apps/api/src/app/api/agent/[transport]/route.ts
Simplified McpContext (userId, organizationId), removed buildMcpContext/db lookups, rewrote token handling to inline mcpContext, switched registerMcpTools → registerTools and adjusted register/auth wrapper usage.
Tools registry (removed → new modular registration)
apps/api/src/lib/mcp/tools.ts (removed) → apps/api/src/lib/mcp/tools/index.ts (added)
Deleted large legacy monolith registerMcpTools; added registerTools(server) aggregator that wires per-category registrations.
Tool implementations — devices
apps/api/src/lib/mcp/tools/devices/* (create-workspace, delete-workspace, get-app-context, list-devices, list-projects, list-workspaces, navigate-to-workspace, switch-workspace + index files)
Added many device-targeted tool registrations; each validates inputs and typically delegates to executeOnDevice. Barrel index files added for exports.
Tool implementations — tasks & organizations
apps/api/src/lib/mcp/tools/tasks/*, .../organizations/list-members/*
Added task tool handlers (create_task, update_task, delete_task, get_task, list_tasks, list_task_statuses) and organization member listing tool; re-export barrels added. Several handlers use DB transactions and slug/uniqueness logic.
Tools utilities & register-tool
apps/api/src/lib/mcp/tools/utils/register-tool.ts, .../utils/execute-on-device.ts, .../utils/index.ts
Added registerTool utility; added executeOnDevice with device-presence check, command creation (agentCommands), polling loop, timeout handling, and exported DEVICE_ONLINE_THRESHOLD_MS; re-exports wired.
MCP tools removal/cleanup
apps/api/src/lib/mcp/tools/* (legacy large file removal)
Removed legacy monolithic MCP tools implementation (many handlers and device-command orchestration deleted).
OAuth consent & auth server
apps/web/src/app/oauth/.../ConsentForm.tsx, packages/auth/src/lib/oauth-org-scope-endpoint.ts, packages/auth/src/server.ts
Consent flow changed to call new /oauth/add-org-scope endpoint when org selected, and consent request no longer sends scope field; added new oauthOrgScopeEndpoint and registered it in auth server plugins.

Sequence Diagram(s)

sequenceDiagram
  participant Client
  participant API
  participant DB as Database
  participant Agent as Device/Agent

  Client->>API: call tool endpoint (e.g., create_workspace)
  API->>API: registerTool wrapper validates auth (extract mcpContext)
  API->>DB: check device presence (devicePresence by deviceId)
  alt device offline
    API-->>Client: return { isError: true, message: "device offline" }
  else device online
    API->>DB: insert agentCommand (status: pending, params, timeoutAt)
    API->>DB: poll agentCommand status periodically
    Agent->>DB: update agentCommand status to "completed" or "failed" with result
    DB-->>API: poll sees "completed" -> returns result
    API-->>Client: respond with tool result payload
  end
Loading

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~60 minutes

Possibly related PRs

Poem

"I hopped through code with nimble feet,
KV_URL tucked safe and neat.
Tools sprouted, devices hummed,
Commands queued and agents drummed.
A rabbit cheers — deploys complete! 🐇"

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 warning)
Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title 'refactor(mcp): cleanup auth and reorganize tools' accurately captures the main refactoring objective—cleaning up MCP authentication and reorganizing tools from a monolithic structure into domain-based folders.
Description check ✅ Passed The PR description comprehensively covers all major changes: package replacement, tool reorganization, auth simplification, OAuth scope fix, and environment configuration—exceeding the template requirements with detailed context and test results.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions

github-actions Bot commented Jan 26, 2026 •

Copy link
Copy Markdown
Contributor

🧹 Preview Cleanup Complete

The following preview resources have been cleaned up:

  • ✅ Neon database branch
  • ✅ Electric Fly.io app

Thank you for your contribution! 🎉

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Actionable comments posted: 8

🤖 Fix all issues with AI agents
In `@apps/api/src/lib/mcp/tools/devices/create-workspace/create-workspace.ts`:
- Around line 22-25: The input schema declares taskId but it is never forwarded
to executeOnDevice; update the params object (the one passed into
executeOnDevice) to include taskId from the handler input (preserve optional
behavior), e.g., add taskId: input.taskId (or equivalent variable) to the params
passed to executeOnDevice so create-workspace logic receives the task
association; locate the params construction and the executeOnDevice call in
create-workspace.ts and add the field there.

In `@apps/api/src/lib/mcp/tools/organizations/list-members/list-members.ts`:
- Around line 48-51: The LIKE pattern currently interpolates raw user input into
ilike(users.name, `%${search}%`) allowing wildcard injection; add a helper
(e.g., escapeLikePattern) that escapes %, _, and backslash in the incoming
search string, call it before building the pattern, and use the escaped value in
the ilike calls (e.g., ilike(users.name, `%${escaped}%`) and ilike(users.email,
`%${escaped}%`) so user-supplied %/_ do not act as wildcards while keeping
parameterization intact.

In `@apps/api/src/lib/mcp/tools/tasks/create-task/create-task.ts`:
- Around line 129-145: The current return builds JSON from result.task using
optional chaining, which can produce undefined fields if no row was inserted;
update the create-task logic to explicitly check if result.task exists (inspect
result.task) before constructing the response and handle the missing-case by
either throwing a descriptive error or returning an error payload that includes
result.txid and a clear failure message; ensure you update the return block that
currently JSON.stringify({ id: result.task?.id, slug: result.task?.slug, title:
result.task?.title, txid: result.txid }) to only read id/slug/title when
result.task is present and to provide a deterministic fallback otherwise.

In `@apps/api/src/lib/mcp/tools/tasks/delete-task/delete-task.ts`:
- Around line 42-64: The response uses a different new Date() than the one
persisted; fix by generating a single deletedAt timestamp and using it both in
the transaction update (tx.update(tasks).set({ deletedAt })) and in the returned
JSON (replacing the separate new Date().toISOString()), ensuring you still call
getCurrentTxid(tx) and return result.txid from dbWs.transaction so the persisted
timestamp and the response timestamp match.

In `@apps/api/src/lib/mcp/tools/tasks/update-task/update-task.ts`:
- Around line 75-83: After the transaction returns, add a post-transaction guard
that checks whether result.task is undefined (i.e., the UPDATE affected zero
rows) and if so convert that case into a not-found error instead of returning
success; specifically, after the dbWs.transaction(...) call that returns { task,
txid } from the inner tx update, verify the returned task exists and throw or
return a 404/not-found error (using the same error type/flow the service uses)
referencing the existingTask.id so callers know which id was missing.
- Around line 60-73: The update handler builds updateData from params but
doesn't guard against an empty payload, causing Drizzle's .set() to throw "No
values to set"; before calling the DB update (where updateData is used, e.g., in
the function that constructs updateData in update-task.ts), check if
Object.keys(updateData).length === 0 and return an early error (or throw a
controlled error/BadRequest) indicating no updatable fields were provided so the
code never calls the DB with an empty object; reference the updateData variable
and the params input to implement this validation.

In `@apps/api/src/lib/mcp/tools/utils/execute-on-device.ts`:
- Around line 106-109: The unconditional update using
db.update(agentCommands).set({ status: "timeout" }).where(eq(agentCommands.id,
cmd.id)) can overwrite a command that finished just before the timeout; change
it to first read the current status for the specific command id (eg. query
agentCommands where id == cmd.id), and only perform the update to status =
"timeout" if the current status is still a pending/running state (not
"completed", "failed", or other final states). Use the same unique symbols
(agentCommands, cmd.id, db) and perform the conditional update transactionally
or by adding the current-status check in the WHERE clause to avoid race
conditions.

In `@packages/auth/src/lib/oauth-org-scope-endpoint.ts`:
- Around line 59-84: When parsing verification.value in the oauth-org-scope
logic, guard JSON.parse and log parse failures with a prefixed message (e.g.,
"oauth-org-scope: failed to parse verification value") instead of letting it
throw; then ensure you replace any existing organization:* scope rather than
skipping when one already exists: parse verification.value into value, normalize
value.scope into an array (currentScopes), remove any entries that
startWith("organization:"), push the new orgScope
(`organization:${organizationId}`), and write back via
db.update(verifications).set({ value: JSON.stringify({...value, scope:
currentScopes}) }).where(eq(verifications.id, verification.id)).
🧹 Nitpick comments (9)
apps/api/src/env.ts (1)

31-33: Consider aligning URL validation across KV variables.

KV_URL uses .url() validation while KV_REST_API_URL on line 31 does not. If both are expected to be valid URLs, consider adding .url() to KV_REST_API_URL for consistency.

Suggested alignment
-		KV_REST_API_URL: z.string(),
+		KV_REST_API_URL: z.string().url(),
 		KV_REST_API_TOKEN: z.string(),
 		KV_URL: z.string().url(),
apps/api/src/lib/mcp/tools/devices/list-workspaces/list-workspaces.ts (1)

13-20: Consider removing redundant validation or enforcing non-empty at schema level.

Since z.string() already rejects undefined/null, Zod validation should fail before the handler runs if deviceId is missing. The as string cast and subsequent check are redundant for that case.

If the intent is to reject empty strings, use z.string().min(1) in the schema (line 9) for clearer validation at the boundary.

Suggested schema-level validation
 inputSchema: {
-  deviceId: z.string().describe("Target device ID"),
+  deviceId: z.string().min(1).describe("Target device ID"),
 },

Then remove the redundant handler check:

 async (params, ctx) => {
-  const deviceId = params.deviceId as string;
-
-  if (!deviceId) {
-    return {
-      content: [{ type: "text", text: "Error: deviceId is required" }],
-      isError: true,
-    };
-  }
+  const { deviceId } = params;

   return executeOnDevice({
apps/api/src/app/api/agent/[transport]/route.ts (1)

66-66: Simplify callback to direct function reference.

The wrapper function is unnecessary since registerTools already has the expected signature.

Suggested change
 const baseHandler = createMcpHandler(
-  (server) => registerTools(server),
+  registerTools,
   { capabilities: { tools: {} } },
apps/api/src/lib/mcp/tools/devices/create-workspace/create-workspace.ts (1)

29-36: Redundant validation: Zod schema already enforces deviceId as required.

The z.string() schema for deviceId ensures it cannot be undefined. The manual if (!deviceId) check is defensive but technically unnecessary. This pattern is consistent across other device tools, so keeping it for defense-in-depth is acceptable.

apps/api/src/lib/mcp/tools/tasks/create-task/create-task.ts (1)

90-105: Slug uniqueness query may fetch more rows than necessary.

The ilike(tasks.slug, \${baseSlug}%`)query matches any slug starting withbaseSlug, potentially including unrelated slugs (e.g., baseSlug="task"matches both"task-1"and"task-unrelated-feature"). The logic is correct since the Setcheck verifies exact matches, but a more precise pattern like${baseSlug}or${baseSlug}-[0-9]+` would reduce unnecessary data transfer.

apps/api/src/lib/mcp/tools/utils/register-tool.ts (1)

29-31: Consider adding logging before throwing the authentication error.

Per coding guidelines, errors should be logged with context. Adding a log statement would help with debugging authentication issues in production.

♻️ Proposed enhancement
 				const ctx = authInfo?.extra?.mcpContext;
 				if (!ctx) {
+					console.error("[mcp/register-tool] No MCP context available - authentication required");
 					throw new Error("No MCP context available - authentication required");
 				}
apps/api/src/lib/mcp/tools/organizations/list-members/list-members.ts (1)

21-55: Query construction is duplicated; consider using a dynamic approach.

The select clause and join are duplicated between the base query (lines 21-32) and the search-filtered query (lines 35-54). A dynamic where clause builder would reduce duplication and maintenance burden.

♻️ Simplified approach using dynamic conditions
-		let query = db
-			.select({
-				id: users.id,
-				name: users.name,
-				email: users.email,
-				image: users.image,
-				role: members.role,
-			})
-			.from(members)
-			.innerJoin(users, eq(members.userId, users.id))
-			.where(and(...conditions))
-			.limit(limit);
-
-		if (search) {
-			query = db
-				.select({
-					id: users.id,
-					name: users.name,
-					email: users.email,
-					image: users.image,
-					role: members.role,
-				})
-				.from(members)
-				.innerJoin(users, eq(members.userId, users.id))
-				.where(
-					and(
-						...conditions,
-						or(
-							ilike(users.name, `%${search}%`),
-							ilike(users.email, `%${search}%`),
-						),
-					),
-				)
-				.limit(limit);
-		}
+		if (search) {
+			conditions.push(
+				or(
+					ilike(users.name, `%${search}%`),
+					ilike(users.email, `%${search}%`),
+				)!,
+			);
+		}
+
+		const query = db
+			.select({
+				id: users.id,
+				name: users.name,
+				email: users.email,
+				image: users.image,
+				role: members.role,
+			})
+			.from(members)
+			.innerJoin(users, eq(members.userId, users.id))
+			.where(and(...conditions))
+			.limit(limit);
apps/api/src/lib/mcp/tools/tasks/get-task/get-task.ts (1)

12-14: Consider adding .min(1) to the taskId schema to reject empty strings.

The current z.string() allows empty strings, which would fail the UUID check and fall back to slug lookup with an empty string. Adding .min(1) would provide clearer validation.

♻️ Proposed schema enhancement
 		inputSchema: {
-			taskId: z.string().describe("Task ID (uuid) or slug"),
+			taskId: z.string().min(1).describe("Task ID (uuid) or slug"),
 		},
apps/api/src/lib/mcp/tools/devices/list-devices/list-devices.ts (1)

20-31: Extract the offline window multiplier into a named constant.

Helps avoid magic numbers and makes the intent clearer. As per coding guidelines, avoid magic numbers.

♻️ Suggested refactor
+const OFFLINE_THRESHOLD_MULTIPLIER = 10;
+
 		const threshold = new Date(Date.now() - DEVICE_ONLINE_THRESHOLD_MS);
 		const offlineThreshold = new Date(
-			Date.now() - DEVICE_ONLINE_THRESHOLD_MS * 10,
+			Date.now() - DEVICE_ONLINE_THRESHOLD_MS * OFFLINE_THRESHOLD_MULTIPLIER,
 		);

Comment on lines +48 to +51
or(
ilike(users.name, `%${search}%`),
ilike(users.email, `%${search}%`),
),

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

User input in LIKE pattern allows wildcard injection.

The search parameter is interpolated directly into the LIKE pattern (%${search}%). While Drizzle parameterizes values preventing SQL injection, a user can still inject LIKE wildcards (e.g., % or _) to alter query behavior. Consider escaping LIKE special characters if strict matching is desired.

♻️ Optional: Escape LIKE wildcards
// Helper to escape LIKE special characters
function escapeLikePattern(str: string): string {
  return str.replace(/[%_\\]/g, '\\$&');
}

// Usage
const escaped = escapeLikePattern(search);
ilike(users.name, `%${escaped}%`)
🤖 Prompt for AI Agents
In `@apps/api/src/lib/mcp/tools/organizations/list-members/list-members.ts` around
lines 48 - 51, The LIKE pattern currently interpolates raw user input into
ilike(users.name, `%${search}%`) allowing wildcard injection; add a helper
(e.g., escapeLikePattern) that escapes %, _, and backslash in the incoming
search string, call it before building the pattern, and use the escaped value in
the ilike calls (e.g., ilike(users.name, `%${escaped}%`) and ilike(users.email,
`%${escaped}%`) so user-supplied %/_ do not act as wildcards while keeping
parameterization intact.

Comment on lines +75 to +83
const result = await dbWs.transaction(async (tx) => {
const [task] = await tx
.update(tasks)
.set(updateData)
.where(eq(tasks.id, existingTask.id))
.returning();

const txid = await getCurrentTxid(tx);
return { task, txid };

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

Handle zero-row updates inside the transaction.

If the task is deleted between the initial read and the UPDATE, result.task can be undefined and the response will still look successful. Consider a post-transaction guard to return a not‑found error instead.

🧯 Guard against missing updated row
 const result = await dbWs.transaction(async (tx) => {
 	const [task] = await tx
 		.update(tasks)
 		.set(updateData)
 		.where(eq(tasks.id, existingTask.id))
 		.returning();

 	const txid = await getCurrentTxid(tx);
 	return { task, txid };
 });
+
+ if (!result.task) {
+ 	return {
+ 		content: [{ type: "text", text: "Error: Task not found" }],
+ 		isError: true,
+ 	};
+ }
🤖 Prompt for AI Agents
In `@apps/api/src/lib/mcp/tools/tasks/update-task/update-task.ts` around lines 75
- 83, After the transaction returns, add a post-transaction guard that checks
whether result.task is undefined (i.e., the UPDATE affected zero rows) and if so
convert that case into a not-found error instead of returning success;
specifically, after the dbWs.transaction(...) call that returns { task, txid }
from the inner tx update, verify the returned task exists and throw or return a
404/not-found error (using the same error type/flow the service uses)
referencing the existingTask.id so callers know which id was missing.

Comment on lines +59 to +84
// Parse the stored value and add organization scope
const value = JSON.parse(verification.value);
const orgScope = `organization:${organizationId}`;

// Ensure scope is an array
const currentScopes = Array.isArray(value.scope)
? value.scope
: typeof value.scope === "string"
? value.scope.split(" ")
: [];

// Add org scope if not already present
if (!currentScopes.some((s: string) => s.startsWith("organization:"))) {
currentScopes.push(orgScope);
}

// Update the verification value with the new scopes
await db
.update(verifications)
.set({
value: JSON.stringify({
...value,
scope: currentScopes,
}),
})
.where(eq(verifications.id, verification.id));

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

Replace existing organization scopes and guard malformed verification payloads.

If a consent code already contains an organization: scope and the user changes selection, the current check skips updating the scope, so consent can be applied to the wrong org. Also, JSON.parse can throw on a corrupted verification value; handle it explicitly and log with a prefix. As per coding guidelines, log parse failures with a prefixed message.

🛠️ Suggested fix
-				const value = JSON.parse(verification.value);
+				let value: { scope?: string | string[] } = {};
+				try {
+					value = JSON.parse(verification.value);
+				} catch (err) {
+					console.error(
+						"[auth/oauth] Failed to parse consent verification value",
+						err,
+					);
+					return ctx.json({ error: "Invalid consent payload" }, { status: 400 });
+				}
@@
-				const currentScopes = Array.isArray(value.scope)
+				const currentScopes = Array.isArray(value.scope)
 					? value.scope
 					: typeof value.scope === "string"
 						? value.scope.split(" ")
 						: [];
-
-				// Add org scope if not already present
-				if (!currentScopes.some((s: string) => s.startsWith("organization:"))) {
-					currentScopes.push(orgScope);
-				}
+				const normalizedScopes = currentScopes.filter(
+					(s: string) => !s.startsWith("organization:"),
+				);
+				normalizedScopes.push(orgScope);
@@
-							scope: currentScopes,
+							scope: normalizedScopes,
🤖 Prompt for AI Agents
In `@packages/auth/src/lib/oauth-org-scope-endpoint.ts` around lines 59 - 84, When
parsing verification.value in the oauth-org-scope logic, guard JSON.parse and
log parse failures with a prefixed message (e.g., "oauth-org-scope: failed to
parse verification value") instead of letting it throw; then ensure you replace
any existing organization:* scope rather than skipping when one already exists:
parse verification.value into value, normalize value.scope into an array
(currentScopes), remove any entries that startWith("organization:"), push the
new orgScope (`organization:${organizationId}`), and write back via
db.update(verifications).set({ value: JSON.stringify({...value, scope:
currentScopes}) }).where(eq(verifications.id, verification.id)).

- Forward taskId parameter in create-workspace tool
- Add explicit error handling when task insert returns nothing
- Use single timestamp for deletedAt in delete-task
- Validate updateData is not empty before DB update in update-task
- Add status check to timeout update to prevent race condition
- Add JSON.parse error guard in oauth-org-scope endpoint
@saddlepaddle
saddlepaddle merged commit 4d78850 into main Jan 27, 2026
13 checks passed
@coderabbitai coderabbitai Bot mentioned this pull request Jan 31, 2026
3 of 6 tasks
@Kitenite
Kitenite deleted the mcp-cleanup branch February 4, 2026 20:43

This branch was previously deployed

1 inactive deployment
preview — 01d494bb Deployed Jan 27, 2026 by saddlepaddle via Deploy Marketing #1183
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.

1 participant