feat: expose the full DeployGate public API as MCP tools (apps, projects, workspaces)

[tnj]

Summary

Expand the MCP server from upload/distribution/basic-member management to near-complete coverage of the DeployGate public API. ~39 new tools across apps/binaries, keystores, distributions, projects (organizations), and workspaces (enterprises), plus two client robustness fixes.

Phase 1 — apps / binaries / distributions / keystores

• apps.ts: get_app, list/get/update/delete/protect/unprotect/search app revisions (8)
• app-members.ts: list_app_members
• keystores.ts: get/create/update/delete/download_keystore (Android, 5)
• distributions.ts: delete_distribution_by_name, update_distribution_revision, + IP-restriction params on update_distribution

Phase 2 — projects (organizations)

• projects.ts: get/update/delete_project, list_project_apps, list_project_members (5)
• app-members.ts: list/remove app teams, list/remove app shared teams (4)
• list_members widened to accept arbitrary/custom team names

Phase 3 — workspaces (enterprises)

• workspace-members.ts: list/get/add/remove workspace members (4)
• workspace-projects.ts: list_workspace_projects, create_project, list_workspace_project_members, add/remove_project_member (5)
• shared-teams.ts: list/delete shared teams, list/remove shared-team members (4)
• workspace-saml.ts: update_saml_certificate (1)

Client fixes

• Correct shared_teams API path (was sharedteams)
• request() tolerates empty-body responses (204 → null, empty → {} on SyntaxError)

Testing

• npm run build && npm test — 368 tests pass.
• All tools live-verified against the real API (read-only with real data; mutating ops via safe error-path checks; destructive/SAML not run live).

Notes

• This PR also stops tracking docs/superpowers/ (agent design docs) and gitignores it.
• The branch contains feat!: commits internally; please squash-merge with this feat: title so release-please cuts a minor bump (1.5.0, since 1.4.0 already shipped on main).

🤖 Generated with Claude Code

[tnj]

/gemini review

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.

[tnj]

/gemini review

[gemini-code-assist]

Code Review

This pull request significantly expands the DeployGate MCP server by adding a comprehensive set of new tools and client methods. These cover app revisions, app members/teams, Android keystores, project details, workspace members, workspace projects, and SAML certificate updates, along with extensive test coverage. The review feedback highlights opportunities to improve robustness and user experience by dynamically resolving home directory paths (~/) in file-reading methods and enforcing described input constraints locally within the Zod schemas and tool handlers.

[gemini-code-assist]

The filePath parameter is read directly using readFile. If the user or agent provides a path starting with ~/ (e.g., ~/certs/idp.pem), readFile will fail with ENOENT because Node.js does not automatically resolve the home directory. Resolving the home directory path dynamically makes the tool much more robust and user-friendly.

  async updateSamlCertificate(
    workspace: string,
    filePath: string,
  ): Promise<unknown> {
    const { homedir } = await import("node:os");
    const { join } = await import("node:path");
    const resolvedPath = filePath.startsWith("~/")
      ? join(homedir(), filePath.slice(2))
      : filePath;
    const fileBuffer = await readFile(resolvedPath);
    const fileName = basename(resolvedPath);
    const formData = new FormData();
    formData.append("idp_cert", new Blob([fileBuffer]), fileName);
    return this.request(
      "PUT",
      `/api/enterprises/${workspace}/saml_settings/update_certificate`,
      { formData },
    );
  }

[gemini-code-assist]

Similar to updateSamlCertificate, the filePath parameter in updateKeystore is read directly using readFile. Resolving paths starting with ~/ dynamically prevents ENOENT errors when users or agents specify paths relative to their home directory.

  async updateKeystore(
    owner: string,
    appId: string,
    params: { 
      filePath: string;
      aliasName: string;
      keystorePassword: string;
      keyPassword: string;
    },
  ): Promise<unknown> {
    const { homedir } = await import("node:os");
    const { join } = await import("node:path");
    const resolvedPath = params.filePath.startsWith("~/")
      ? join(homedir(), params.filePath.slice(2))
      : params.filePath;
    const fileBuffer = await readFile(resolvedPath);
    const fileName = basename(resolvedPath);
    const formData = new FormData();
    formData.append("file", new Blob([fileBuffer]), fileName);
    formData.append("alias_name", params.aliasName);
    formData.append("keystore_password", params.keystorePassword);
    formData.append("key_password", params.keyPassword);
    return this.request("PUT", this.keystoreBase(owner, appId), {
      formData,
    });
  }

[gemini-code-assist]

The update_project tool description states: "Provide at least one of display_name or description." However, the handler does not validate this constraint. If both are omitted, the tool will send an empty payload to the DeployGate API. Adding a local validation check prevents unnecessary API calls and provides immediate feedback to the agent.

    async (args) => {
      if (args.display_name === undefined && args.description === undefined) {
        return {
          content: [
            {
              type: "text",
              text: "Error: At least one of display_name or description must be provided.",
            },
          ],
          isError: true,
        };
      }
      const results = await client.updateProject(args.project, {
        display_name: args.display_name,
        description: args.description,
      });
      return { content: [{ type: "text", text: JSON.stringify(results, null, 2) }] };
    },

[gemini-code-assist]

The get_workspace_member tool description states that the member name or email "must be at least 3 characters". Enforcing this constraint locally using Zod's .min(3) validation prevents invalid API requests and provides immediate feedback to the agent.

Suggested change

	{ workspace: workspaceArg, id: z.string().describe("Member name or email") },
	{ workspace: workspaceArg, id: z.string().min(3).describe("Member name or email (must be at least 3 characters)") },

[gemini-code-assist]

The create_project tool description states that the project name "must be 3-28 chars (letters/digits/hyphens/underscores, starting and ending with a letter or digit)". Enforcing these constraints locally using Zod's .min(3), .max(28), and .regex() validation ensures robust input validation and prevents invalid API requests.

      name: z
        .string()
        .min(3)
        .max(28)
        .regex(/^[a-zA-Z0-9][a-zA-Z0-9_-]*[a-zA-Z0-9]$/, "Project name must be 3-28 characters, contain only letters, digits, hyphens, or underscores, and start/end with a letter or digit")
        .describe("Project name (3-28 chars, globally unique)"),