@opsee/mcp-server 0.9.60 → 0.10.2

package/src/tools/docs.ts

@@ -39,11 +39,8 @@ export function registerDocTools(
     async ({ projectId }) => {
       try {
         const clients = getClients();
-        // project_id goes on the request itself, as with doc pages: the backend
-        // scopes the list with GetDocSpacesRequest.project_id, and a generic
-        // ProjectId filter cannot stand in for it -- scopes.ParseFilterOptions
-        // drops that key as security-sensitive, which returned every doc space
-        // in the company.
+        // project_id must ride on the request: ParseFilterOptions drops it from generic filters as
+        // security-sensitive, which returned every doc space in the company.
         const res = await clients.docSpaces.getDocSpaces({
           projectId,
           pagination: overridePagination(),
@@ -65,11 +62,8 @@ export function registerDocTools(
     async ({ projectId }) => {
       try {
         const clients = getClients();
-        // Doc pages hang off the project, not off a doc space: model.DocPage has
-        // no doc_space_id column (only the legacy proto field), and the backend
-        // scopes the list with the request's own project_id, which the validator
-        // requires to be >= 1. A generic ProjectId filter cannot substitute for
-        // it -- scopes.ParseFilterOptions drops that key as security-sensitive.
+        // Doc pages hang off the project, and the request's own project_id (validated >= 1) is what
+        // scopes the list; a generic filter is dropped as security-sensitive.
         const res = await clients.docPages.getDocPages({
           projectId,
           pagination: overridePagination(),
@@ -121,7 +115,6 @@ export function registerDocTools(
       try {
         const clients = getClients();
 
-        // Resolve current user for createdByUserId
         let userId = Number(authManager.getUserId()) || 0;
         if (!userId) {
           const meRes = await clients.users.getMe({});
@@ -235,10 +228,8 @@ export function registerDocTools(
           isRoot: existing.isRoot,
           isArchived: existing.isArchived,
           displayOrder: existing.displayOrder,
-          // EditDocPageRequest carries project_id, but the DocPage message read
-          // back from GetDocPage (proto/api/v1/models.proto) has no project_id
-          // field -- only the unused legacy doc_space_id -- so there is no way
-          // to read the existing value back to resend it here. Left unset.
+          // Left unset: EditDocPageRequest carries project_id but the DocPage message has no such
+          // field, so the existing value cannot be read back.
           parentPageId: existing.parentPageId,
           createdByUserId: existing.createdByUserId,
           updatedByUserId: userId,
@@ -260,10 +251,8 @@ export function registerDocTools(
               createdByUserId: userId,
             });
           } catch (snapshotError) {
-            // The page edit already committed, so this is reported rather than
-            // raised: the content is saved either way. Name the version number
-            // so the gap between the page counter and version history can be
-            // reconciled by hand.
+            // The edit already committed, so report rather than raise, naming the version so the gap
+            // against version history can be reconciled by hand.
             warning = `\n\nWarning: the page was saved, but recording version ${nextVersionNumber} in page history failed: ${formatError(snapshotError)}\nThe page now reports version ${nextVersionNumber} with no matching history entry. Re-running this tool creates version ${nextVersionNumber + 1} rather than backfilling ${nextVersionNumber}.`;
           }
         }

package/src/tools/notifications.ts

@@ -9,12 +9,8 @@ import {
   FilterSchema,
 } from "../../gen/api/v1/filter_pb.js";
 
-// Notifications are user-scoped server-side (the GetNotifications RPC reads
-// the user_id off the auth context), so there's no per-call user parameter.
-// notification_type values are free-form strings produced by the backend
-// (e.g. "task_assigned", "comment_added", "task_blocked_unblocked",
-// "mention", "ai_workflow_status_change"). Treat them as opaque tags;
-// callers can filter via the unreadOnly param or post-process by type.
+// Notifications are user-scoped server-side (GetNotifications reads user_id off the auth context), so
+// there is no user parameter. notification_type values are backend-defined opaque tags.
 
 function formatNotification(n: {
   id: number;

package/src/tools/tasks-bulk.ts

@@ -4,14 +4,9 @@ import type { ApiClients } from "../client/api.js";
 import { formatError } from "../utils/format.js";
 import { BULK_PROJECT_ID } from "./descriptions.js";
 
-// Multi-task edits. These go through the backend BulkEditTasks RPC, which
-// applies every change in one transaction and silently skips task ids the
-// caller cannot see - hence the "n of m" wording in the response.
-//
-// OPS-203: the per-field convenience wrappers (bulk_assign, bulk_set_priority,
-// bulk_move_to_column, bulk_move_to_cycle) were removed. Each was a strict
-// subset of opsee_bulk_update_tasks with a single field set, and four extra
-// tool definitions cost more context on every request than they saved.
+// Multi-task edits via BulkEditTasks, which applies everything in one transaction and silently skips
+// invisible task ids, hence the "n of m" response wording. The per-field wrappers were removed:
+// each was opsee_bulk_update_tasks with one field set, and cost context on every request.
 export function registerTaskBulkTools(
   server: McpServer,
   getClients: () => ApiClients,

package/src/tools/tasks-read-write.ts

@@ -204,18 +204,15 @@ export function registerTaskReadWriteTools(
       try {
         const clients = getClients();
 
-        // Auto-resolve defaults
         let resolvedBoardId = 0;
         let resolvedColumnId = boardColumnId || 0;
         let resolvedTaskTypeId = taskTypeId || 0;
         let resolvedPriorityId = priorityId || 0;
 
-        // Get default board
         const boardsRes = await clients.boards.getBoards({ projectId });
         if (boardsRes.boards?.length) {
           resolvedBoardId = boardsRes.boards[0].id;
 
-          // Get first column if not specified
           if (!boardColumnId) {
             const colsRes = await clients.boardColumns.getBoardColumns({
               boardId: resolvedBoardId,
@@ -226,7 +223,6 @@ export function registerTaskReadWriteTools(
           }
         }
 
-        // Get first task type if not specified
         if (!taskTypeId) {
           const typesRes = await clients.taskTypes.getTaskTypes({ projectId });
           if (typesRes.taskTypes?.length) {
@@ -234,7 +230,6 @@ export function registerTaskReadWriteTools(
           }
         }
 
-        // Get first priority if not specified
         if (!priorityId) {
           const priRes = await clients.taskPriorities.getTaskPriorities({ projectId });
           if (priRes.taskPriorities?.length) {
@@ -242,7 +237,6 @@ export function registerTaskReadWriteTools(
           }
         }
 
-        // Get reporter (current user)
         let reporterUserId = 0;
         const userId = authManager.getUserId();
         if (userId) {
@@ -312,13 +306,12 @@ export function registerTaskReadWriteTools(
       try {
         const clients = getClients();
 
-        // Read current task
         const getRes = await clients.tasks.getTask({ id: taskId });
         const task = getRes.task;
         if (!task)
           return { content: [{ type: "text", text: "Task not found. Use opsee_list_tasks to see available tasks." }] };
 
-        // Merge changes into full EditTaskRequest
+        // EditTaskRequest is a full replacement, so merge onto the current task.
         const res = await clients.tasks.editTask({
           id: task.id,
           identifier: task.identifier,

package/src/utils/format/blocknote.ts

@@ -1,11 +1,5 @@
-// ---------------------------------------------------------------------------
-// BlockNote JSON → Markdown
-// ---------------------------------------------------------------------------
-
-// `strike` is the key the BlockNote default schema uses, and it is what both Go
-// writers persist (backend/service/task.go parseInlineMarkdown and
-// orchestrator/internal/util/blocknote.go). `strikethrough` is accepted too so a
-// payload using the long spelling is not silently dropped.
+// `strike` is the BlockNote default schema's key and what both Go writers persist;
+// `strikethrough` is accepted too so the long spelling is not silently dropped.
 type BNInlineStyle = {
   bold?: boolean;
   italic?: boolean;
@@ -31,14 +25,12 @@ function renderInline(content: BNInlineContent[]): string {
       const inner = renderInline(node.content ?? []);
       return `[${inner}](${node.href})`;
     }
-    // text node
     const t = node as BNTextContent;
     let s = t.text ?? "";
     if (t.styles?.code) s = `\`${s}\``;
     if (t.styles?.bold) s = `**${s}**`;
     if (t.styles?.italic) s = `*${s}*`;
-    // Struck-through text usually means "decided against this". Dropping the
-    // markers would present an abandoned plan item as a live one.
+    // Keep the markers: struck text means "decided against", not a live plan item.
     if (t.styles?.strike || t.styles?.strikethrough) s = `~~${s}~~`;
     if (t.styles?.underline) s = `<u>${s}</u>`;
     return s;
@@ -70,8 +62,7 @@ function renderBlock(block: BNBlock, indent: string): string[] {
     case "codeBlock": {
       const lang = (block.props?.language as string) || "";
       lines.push(`${indent}\`\`\`${lang}`);
-      // A code block's text is one node containing newlines. Indent every line,
-      // not just the first, or the rest escapes the list item it is nested in.
+      // A code block is one node with newlines; indent every line or it escapes the enclosing list item.
       for (const body of inline.split("\n")) lines.push(`${indent}${body}`);
       lines.push(`${indent}\`\`\``);
       break;
@@ -94,12 +85,9 @@ function renderBlock(block: BNBlock, indent: string): string[] {
   return lines;
 }
 
-// Mirrors the two existing product-side detectors so a page written through MCP
-// is labelled exactly as the same bytes would be from the web UI:
-// frontend/src/pages/Docs/hooks/useDocTreeMutations.js (JSON.parse + Array.isArray)
-// and backend/service/mentions.go IsBlockNoteJSON (unmarshal into []interface{}).
-// A JSON array is the only shape BlockNote persists, so an object or a bare
-// scalar is content, not a document body.
+// Mirrors the product-side detectors (useDocTreeMutations.js, mentions.go IsBlockNoteJSON) so MCP and
+// the web UI label identical bytes alike. BlockNote persists only arrays, so an object or scalar is
+// content, not a document body.
 export function isBlockNoteJSON(content: string): boolean {
   try {
     return Array.isArray(JSON.parse(content));
@@ -108,9 +96,7 @@ export function isBlockNoteJSON(content: string): boolean {
   }
 }
 
-// The reader (frontend/src/pages/Docs/DocPage.jsx) only JSON-parses when
-// contentType is "json" and otherwise wraps the raw string in a paragraph, so
-// mislabelling markdown as "json" renders an empty page.
+// DocPage.jsx only JSON-parses when contentType is "json", so mislabelling markdown renders an empty page.
 export function detectDocContentType(content: string): "text" | "json" {
   return isBlockNoteJSON(content) ? "json" : "text";
 }
@@ -126,7 +112,6 @@ export function blockNoteToMarkdown(content: string): string {
       if (typeof block !== "object" || block === null || !block.type) return content;
       const blockLines = renderBlock(block, "");
       mdLines.push(...blockLines);
-      // Separate top-level blocks with a blank line (except last)
       if (i < parsed.length - 1) mdLines.push("");
     }
     return mdLines.join("\n");

package/src/utils/tool-schema.ts

@@ -1,24 +1,10 @@
 import type { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
 import { ListToolsRequestSchema } from "@modelcontextprotocol/sdk/types.js";
 
-// Every tool definition is re-sent on every AI request, so the tools/list
-// payload is a permanent tax on the context window. Three constructs the SDK
-// emits carry no information for a caller:
-//
-//   "$schema": "http://json-schema.org/draft-07/schema#"   (once per tool)
-//   "maximum": 9007199254740991                            (per unbounded int)
-//   "minimum": -9007199254740991                           (per unbounded int)
-//   "execution": {"taskSupport": "forbidden"}              (once per tool)
-//
-// The bounds are Number.MAX/MIN_SAFE_INTEGER, which `z.number().int()` records
-// on any int field that doesn't declare its own; no caller is going to pass an
-// id near 2^53, and the server-side Zod schema still rejects one if they do.
-// Stripping them leaves the advertised schema a valid, strictly weaker JSON
-// Schema — an explicit bound like `.min(1)` is left alone.
-//
-// `execution.taskSupport` is optional in the protocol and clients only act on
-// "required"/"optional" (see the SDK client's callTool path) — an absent field
-// and an explicit "forbidden" are the same thing to them.
+// tools/list is re-sent on every AI request, so these no-information SDK constructs are stripped:
+// "$schema", the MAX/MIN_SAFE_INTEGER bounds z.number().int() adds to undeclared int fields, and
+// "execution": {"taskSupport": "forbidden"}. Explicit bounds like .min(1) are left alone, the server-side
+// Zod schema still enforces the removed ones, and clients treat absent taskSupport as "forbidden".
 function stripSafeIntBounds(node: unknown): void {
   if (Array.isArray(node)) {
     for (const child of node) stripSafeIntBounds(child);
@@ -54,17 +40,9 @@ function compactTool(tool: ToolDefinition): void {
   }
 }
 
-/**
- * Wrap the SDK's tools/list handler so every advertised tool definition is
- * compacted on the way out. The SDK builds the JSON Schema internally (tools
- * are registered as Zod shapes and converted inside its list handler), so
- * post-processing the response is the only place this can happen.
- *
- * Degrades to a no-op if the SDK ever stops storing handlers where we look for
- * them — the definitions go back to being verbose, nothing breaks. The test in
- * tool-schema.test.ts asserts the compaction is live so that degradation is
- * caught in CI rather than in production token bills.
- */
+/** Wraps the SDK's tools/list handler to compact each definition on the way out; the SDK converts Zod
+ * to JSON Schema internally, so the response is the only interception point. Degrades to a no-op if the
+ * SDK moves its handlers, which tool-schema.test.ts asserts against so CI catches it, not token bills. */
 export function compactToolDefinitions(server: McpServer): void {
   const handlers = (
     server.server as unknown as {

package/README.md

@@ -1,304 +0,0 @@
-# Opsee MCP Server
-
-Manage your Opsee projects, tasks, docs, and cycles directly from AI-powered coding environments like Claude Code and Cursor.
-
-## Quick Start
-
-### 1. Authenticate
-
-```bash
-npx @opsee/mcp-server login
-```
-
-This opens your browser to sign in to Opsee. Your credentials are saved to `~/.opsee/credentials.json`.
-
-### 2. Add to Claude Code
-
-```bash
-claude mcp add opsee -- npx @opsee/mcp-server serve
-```
-
-### 3. Restart Claude Code
-
-Exit and reopen Claude Code. Run `/mcp` to verify `opsee` shows as connected.
-
-### 4. Start using it
-
-Ask Claude things like:
-- "List my Opsee projects"
-- "Show tasks in project Codlas"
-- "Create a task called 'Fix login bug' in project 1"
-- "What cycles are active in project 1?"
-- "Show me the docs in project 1"
-
-## Available Tools (47)
-
-| Tool | Description |
-|------|-------------|
-| `opsee_get_me` | Get your profile info |
-| `opsee_list_users` | List company users (resolve assignee IDs) |
-| `opsee_get_user` | Get user details |
-| `opsee_list_projects` | List all projects |
-| `opsee_get_project` | Get project details |
-| `opsee_list_tasks` | List tasks with filters |
-| `opsee_get_task` | Get task details; `includeContext: true` adds labels, comments, dependencies, parent, subtasks in the same call |
-| `opsee_create_task` | Create a new task (accepts inline labelIds[] to skip follow-up attach calls) |
-| `opsee_update_task` | Update task fields (accepts labelIds[] with replace-set semantics) |
-| `opsee_bulk_update_tasks` | Update many tasks in one transaction — assignee, priority, column, cycle, storyPoints, estimatedHours, parentTaskId, labelIds |
-| `opsee_replace_task_labels` | Replace a single task's full set of labels |
-| `opsee_delete_task` | Delete a task by ID |
-| `opsee_bulk_delete_tasks` | Delete many tasks in one call |
-| `opsee_list_comments` | List comments on a task |
-| `opsee_add_comment` | Add a comment to a task |
-| `opsee_edit_comment` | Edit an existing comment |
-| `opsee_delete_comment` | Delete a comment |
-| `opsee_list_labels` | List labels in a project |
-| `opsee_get_label` | Get label details |
-| `opsee_create_label` | Create a label |
-| `opsee_update_label` | Update a label |
-| `opsee_delete_label` | Delete a label |
-| `opsee_attach_label_to_task` | Attach a label to a task |
-| `opsee_detach_label_from_task` | Detach a label from a task (pass TaskLabel join-row id) |
-| `opsee_list_task_labels` | List labels attached to a task |
-| `opsee_create_task_dependency` | Add a typed task-to-task relation (BLOCKS / BLOCKED_BY / DUPLICATES / RELATES_TO) |
-| `opsee_list_task_dependencies` | List a task's dependencies (both directions) |
-| `opsee_delete_task_dependency` | Delete a task dependency by ID |
-| `opsee_list_task_types` | Get task types (Bug, Feature, etc.) |
-| `opsee_list_task_priorities` | Get priority levels |
-| `opsee_list_boards` | List Kanban boards |
-| `opsee_list_board_columns` | Get board columns/statuses |
-| `opsee_list_cycles` | List cycles/sprints |
-| `opsee_get_cycle` | Get cycle details |
-| `opsee_create_cycle` | Create a new cycle |
-| `opsee_update_cycle` | Update a cycle's fields |
-| `opsee_delete_cycle` | Delete a cycle |
-| `opsee_list_doc_spaces` | List doc spaces in a project |
-| `opsee_get_doc_space` | Get doc space details |
-| `opsee_create_doc_space` | Create a doc space |
-| `opsee_update_doc_space` | Update a doc space |
-| `opsee_delete_doc_space` | Delete a doc space |
-| `opsee_list_doc_pages` | List pages in a doc space |
-| `opsee_get_doc_page` | Read a doc page |
-| `opsee_create_doc_page` | Create a new doc page |
-| `opsee_update_doc_page` | Update a doc page (read-merge-write, with version snapshotting) |
-| `opsee_delete_doc_page` | Delete a doc page |
-| `opsee_set_doc_page_archived` | Archive or unarchive a doc page |
-| `opsee_list_doc_templates` | List doc templates in a project |
-| `opsee_create_doc_template` | Create a doc template |
-| `opsee_update_doc_template` | Update a doc template |
-| `opsee_delete_doc_template` | Delete a doc template |
-| `opsee_list_task_doc_pages` | List doc pages attached to a task |
-| `opsee_list_milestone_doc_pages` | List doc pages attached to a milestone |
-| `opsee_attach_doc_page` | Attach a doc page to a task or a milestone |
-| `opsee_detach_doc_page` | Detach a doc page from a task or a milestone |
-| `opsee_list_repositories` | List connected repositories |
-
-## Task description format
-
-The `description` field on tasks accepts and returns user-supplied text, but the Opsee backend may normalize the stored representation. The exact round-trip behavior depends on the backend version and is not yet fully documented here.
-
-### Acceptance criteria → description checklist
-
-Write acceptance criteria **inline in the task description** using a `## Acceptance criteria` heading followed by markdown checkbox lines. The frontend (BlockNote) renders those as clickable checkboxes; users can toggle them in the UI.
-
-```
-## Acceptance criteria
-
-- [ ] WaiveLateFee RPC compiles and builds
-- [ ] Admin can waive full or partial late fee with reason
-- [ ] Apply-as-credit reduces next payment amount
-- [x] Audit log entry with before/after snapshots
-- [ ] Modal UI matches mockup
-- [ ] Non-admin users cannot access waive action
-```
-
-This is the path `/tpm` and any other AI agent should use when creating or updating tasks via `opsee_create_task` / `opsee_update_task`. The heading casing doesn't matter to the parser (`## Acceptance Criteria` works too).
-
-**Do not use the structured `opsee_add_acceptance_criterion` tool for typical AC.** That tool writes to a separate `acceptance_criteria` DB table that does NOT surface in the task detail UI; it's reserved for automation paths that need machine-trackable criteria outside the description (PR-to-criterion mapping, AI workflow outputs, reporting).
-
-### What's confirmed
-
-- The MCP wrapper passes `description` to the backend unmodified. Whatever transformation happens is server-side.
-- Read tools (`opsee_get_task`, `opsee_list_tasks`) return whatever the backend has stored, byte-for-byte.
-
-### What needs empirical verification
-
-The following test plan, run against a live Opsee instance, captures round-trip behavior for the three common input forms. **Results have not yet been recorded here — run the test and fill in the observed strings below.**
-
-```text
-# Plain text with separator and trailer
-opsee_create_task(projectId=<P>, title="rt plain",
-  description="line one\nline two\n---\nLabels: x")
-opsee_get_task(taskId=<id>) → record exact returned description
-
-# Markdown with headers, list, fenced code
-opsee_create_task(projectId=<P>, title="rt md",
-  description="# H1\n- bullet\n\n```ts\ncode\n```")
-opsee_get_task(taskId=<id>) → record exact returned description
-
-# BlockNote JSON
-opsee_create_task(projectId=<P>, title="rt blocknote",
-  description='[{"type":"paragraph","content":[{"type":"text","text":"x"}]}]')
-opsee_get_task(taskId=<id>) → record exact returned description
-```
-
-### Observed round-trip outcomes
-
-| Input form | Stored form (from `opsee_get_task`) | Notes |
-|---|---|---|
-| Plain text | _Pending empirical verification_ | |
-| Markdown | _Pending empirical verification_ | |
-| BlockNote JSON | _Pending empirical verification_ | |
-
-> If the round trip is lossy (e.g. plain text becomes BlockNote JSON on read), callers relying on byte-identical round-trip should treat `description` as backend-defined and avoid parsing trailers; use first-class fields (`opsee_attach_label_to_task`, `opsee_add_comment`, etc.) for structured metadata instead.
-
-## Remote MCP Server (Recommended)
-
-The remote server runs in the cloud with OAuth 2.0 authentication - no local setup or tokens needed.
-
-### Environments
-
-| Environment | URL | Opsee Instance |
-|-------------|-----|----------------|
-| **Production** | `https://mcp.api.opsee.ai/mcp` | `https://opsee.ai` |
-| **Development** | `https://opsee-development.mcp.cls.codilas.link/mcp` | `https://opsee-development.cdn.codilas.link` |
-
-### Claude Code
-
-```bash
-# Production
-claude mcp add opsee --transport http https://mcp.api.opsee.ai/mcp
-
-# Development
-claude mcp add opsee-dev --transport http https://opsee-development.mcp.cls.codilas.link/mcp
-```
-
-Restart Claude Code. On first use, your browser opens for Opsee login. After authenticating, all tools are available immediately.
-
-You can have both environments connected at the same time - use tools prefixed with the server name (e.g. `opsee` for production, `opsee-dev` for development).
-
-### Cursor / Other MCP Clients
-
-```json
-{
-  "mcpServers": {
-    "opsee": {
-      "type": "http",
-      "url": "https://mcp.api.opsee.ai/mcp"
-    }
-  }
-}
-```
-
-Replace the URL with the development endpoint if targeting that environment.
-
-Your MCP client handles the OAuth flow automatically - just sign in when prompted.
-
-### How it works
-
-1. Client connects to the MCP endpoint (e.g. `https://mcp.api.opsee.ai/mcp`)
-2. Server returns 401 with OAuth discovery metadata
-3. Client registers itself and opens the Opsee login page in your browser
-4. After login, the client exchanges the auth code for an access token
-5. All subsequent tool calls use the token automatically
-
-## Local MCP Server (Alternative)
-
-Run the MCP server locally via npx. Requires a one-time login to get a token.
-
-### 1. Authenticate
-
-```bash
-npx @opsee/mcp-server login
-```
-
-### 2. Add to Claude Code
-
-```bash
-claude mcp add opsee -- npx @opsee/mcp-server serve
-```
-
-### Cursor / Other MCP Clients (Local)
-
-```json
-{
-  "mcpServers": {
-    "opsee": {
-      "command": "npx",
-      "args": ["@opsee/mcp-server", "serve"]
-    }
-  }
-}
-```
-
-### CI / Headless Environments
-
-Skip the browser login by setting a token directly:
-
-```json
-{
-  "mcpServers": {
-    "opsee": {
-      "command": "npx",
-      "args": ["@opsee/mcp-server", "serve"],
-      "env": {
-        "OPSEE_API_TOKEN": "your-jwt-token"
-      }
-    }
-  }
-}
-```
-
-## Self-Hosting the Remote Server
-
-Deploy the MCP server in your own infrastructure using Docker.
-
-### Docker
-
-```bash
-docker build -f mcp/Dockerfile . -t opsee-mcp-server
-
-docker run -p 3100:3100 \
-  -e MCP_SERVER_URL=https://mcp.yourdomain.com \
-  -e OPSEE_API_URL=http://your-backend:8080 \
-  -e OPSEE_APP_URL=https://your-frontend.com \
-  opsee-mcp-server
-```
-
-### Kubernetes
-
-The server includes Kustomize configs following the same pattern as the backend:
-
-```bash
-# Development
-kubectl apply -k mcp/k8/environments/development/ -n opsee-development
-
-# Production
-kubectl apply -k mcp/k8/environments/production/ -n opsee-production
-```
-
-### Environment Variables
-
-| Variable | Description | Default |
-|----------|-------------|---------|
-| `MCP_SERVER_URL` | Public URL of this MCP server (for OAuth redirects) | `http://localhost:3100` |
-| `MCP_HOST` | Bind host | `0.0.0.0` |
-| `MCP_PORT` | Bind port | `3100` |
-| `OPSEE_API_URL` | Backend Connect RPC URL | `https://grpc.api.opsee.ai` |
-| `OPSEE_APP_URL` | Frontend URL (OAuth login page) | `https://opsee.ai` |
-| `OPSEE_API_TOKEN` | Direct JWT token for local mode | - |
-| `OPSEE_CREDENTIALS_PATH` | Override credential file path | `~/.opsee/credentials.json` |
-
-## Local Development
-
-```bash
-# Start backend + frontend locally, then:
-
-# Local mode (stdio):
-OPSEE_APP_URL=http://localhost:5173 OPSEE_API_URL=http://localhost:9990 npx @opsee/mcp-server login
-claude mcp add opsee -e OPSEE_API_URL=http://localhost:9990 -- npx @opsee/mcp-server serve
-
-# Remote mode (HTTP):
-MCP_SERVER_URL=http://localhost:3100 OPSEE_API_URL=http://localhost:9990 OPSEE_APP_URL=http://localhost:5173 npx @opsee/mcp-server serve-remote
-claude mcp add opsee-local --transport http http://localhost:3100/mcp
-```