@salesforce/mcp 0.17.1-dev.0 → 0.17.2-dev.1

package/README.md

@@ -1,263 +0,0 @@
-# mcp
-
-MCP Server for Interacting with Salesforce Orgs
-
-[![NPM](https://img.shields.io/npm/v/@salesforce/mcp.svg?label=@salesforce/mcp)](https://www.npmjs.com/package/@salesforce/mcp) [![License](https://img.shields.io/badge/License-Apache--2.0-blue.svg)](https://opensource.org/license/apache-2-0)
-
-## Overview of the Salesforce DX MCP Server (Developer Preview)
-
-The Salesforce DX MCP Server is a specialized Model Context Protocol (MCP) implementation designed to facilitate seamless interaction between large language models (LLMs) and Salesforce orgs. This MCP server provides a robust set of tools and capabilities that enable LLMs to read, manage, and operate Salesforce resources securely.
-
-Key Features:
-
-- Direct interaction with Salesforce orgs through LLM-driven tools.
-- Secure access using TypeScript libraries (not shelling out to the `sf` Salesforce CLI).
-- Improved security by avoiding the exposure of secrets in plain text.
-- Granular access control with org allowlisting.
-- Modular tool architecture for easy extensibility.
-
-**NOTE**: The Salesforce DX MCP Server is available as a developer preview. The feature isn’t generally available unless or until Salesforce announces its general availability in documentation or in press releases or public statements. All commands, parameters, and other features are subject to change or deprecation at any time, with or without notice. Don't implement functionality developed with these commands or tools. As we continue to enhance and refine the implementation, the available functionality and tools may evolve. We welcome feedback and contributions to help shape the future of this project.
-
-### Security Features
-
-The Salesforce DX MCP Server was designed with security as a top priority.
-
-- **Uses TypeScript libraries directly**
-
-  - Greatly decreases the size of the MCP Server.
-  - Significantly reduces the risk of remote code execution (RCE).
-
-- **No secrets needed in configuration**
-
-  - Eliminates the risk of plain text secret exposure.
-  - Accesses pre-existing (encrypted) auth files on the user's machine.
-  - Implements allowlisting for auth info key/values to prevent sensitive data exposure.
-
-- **No secrets exposed via MCP tools**
-
-  - Prevents other tools from accessing unencrypted tokens.
-  - Tools pass usernames around instead of tokens.
-
-- **Granular access control**
-
-  - MCP Server can access auth info for only orgs that have been explicitly allowlisted.
-  - Users specify allowed orgs when starting the server.
-
-## Get Started Using VS Code as the Client
-
-Want to jump in and see what all the fuss is about? Read on!
-
-This example uses Visual Studio Code (VS Code) as the MCP client because it's a standard Salesforce DX development tool. After you configure it with the Salesforce DX MCP Server, you then use GitHub Copilot and natural language to easily execute typical Salesforce DX development tasks, such as listing your authorized orgs, viewing org records, and deploying or retrieving metadata.
-
-But you're not limited to using only VS Code and Copilot! You can [configure many other clients](README.md#configure-other-clients-to-use-the-salesforce-dx-mcp-server) to use the Salesforce DX MCP Server, such as Cursor, Cline, Claude Desktop, Zed, Windsurf, and more.
-
-**Before You Begin**
-
-For the best getting-started experience, make sure that you have a Salesforce DX environment set up on your computer. In particular:
-
-- [Install Salesforce CLI](https://developer.salesforce.com/docs/atlas.en-us.sfdx_setup.meta/sfdx_setup/sfdx_setup_intro.htm) on your computer.
-- [Install VS Code](https://code.visualstudio.com/docs) on your computer.
-- [Create a Salesforce DX project](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_ws_create_new.htm) and open it in VS Code. You can also clone an example repo, such as [dreamhouse-lwc](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_intro_sample_repo.htm), which is a ready-to-use DX project that contains a simple Salesforce application, with metadata and test data.
-- [Authorize at least one Salesforce org](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_auth_web_flow.htm) to use with your DX project. You can also create a scratch org.
-
-**Let's Do It**
-
-1. Create a `.vscode/mcp.json` file at the root of your DX project and add this JSON:
-
-   ```json
-   {
-     "servers": {
-       "Salesforce DX": {
-         "type": "stdio",
-         "command": "npx",
-         "args": ["-y", "@salesforce/mcp", "--orgs", "DEFAULT_TARGET_ORG", "--toolsets", "all"]
-       }
-     }
-   }
-   ```
-
-   You can also configure the MCP server globally by editing the VS Code [settings.json](https://code.visualstudio.com/docs/configure/settings#_settings-file-locations) file and adding a similar JSON snippet but contained in an `mcp:servers` section.
-
-   The `--orgs` argument is required and specifies the authorized orgs you're allowing the MCP server to access. The `--toolsets` argument is optional and specifies the toolsets it should consult when determining the specific tool to run. See [Configure Orgs and Toolsets](README.md#configure-orgs-and-toolsets) for the available values for the two arguments.
-
-1. Open VS Code, go to **View -> Command Palette** and enter **MCP: List Servers**.
-
-   TIP: You can also get to the command palette by pressing press Ctrl+Shift+P (Windows or Linux) or Command-Shift-P (macOS).
-
-1. Click `Salesforce DX`, then **Start Server**.
-
-   Check the Output tab for the server status.
-
-1. Run **Chat: Open Chat (Agent)** from the command palette to start a new GitHub Copilot chat session.
-
-   Be sure your Copilot chat window is in `Agent` mode; if you're in `Ask` or `Edit` mode, use the [little drop-down](https://github.blog/ai-and-ml/github-copilot/copilot-ask-edit-and-agent-modes-what-they-do-and-when-to-use-them/) to switch.
-
-1. In the GitHub Copilot chat window, use natural language to explain what you want to do. The MCP server determines which configured tool to use, and then shows it to you along with other information. Click **Continue** to run the tool and see the results of your request.
-
-   Try out these examples:
-
-   - List all my orgs.
-   - Which are my active scratch orgs?
-   - Show me all the accounts in the org with alias my-org.
-   - Deploy everything in my project to the org with alias my-org.
-
-1. To stop, restart, or view the MCP server configuration, run the **MCP: List Servers** command, click `Salesforce DX`, then click the appropriate option.
-
-## Configure Orgs and Toolsets
-
-You configure the Salesforce DX MCP Server by specifying at least one authorized org and an optional list of MCP toolsets.
-
-### Configure Orgs
-
-The Salesforce MCP tools require an org, and so you must include the required `--orgs` argument to specify at least one authorized org when you configure the MCP server. Separate multiple values with commas.
-
-You must explicitly [authorize the orgs](https://developer.salesforce.com/docs/atlas.en-us.sfdx_dev.meta/sfdx_dev/sfdx_dev_auth_web_flow.htm) on your computer before the MCP server can access them. Use the `org login web` Salesforce CLI command or the VS Code **SFDX: Authorize an Org** command from the command palette.
-
-These are the available values for the `--orgs` argument:
-
-- `DEFAULT_TARGET_ORG` - Allow access to your default org. If you've set a local default org in your DX project, the MCP server uses it. If not, the server uses a globally-set default org.
-- `DEFAULT_TARGET_DEV_HUB` - Allow access to your default Dev Hub org. If you've set a local default Dev Hub org in your DX project, the MCP server uses it. If not, the server uses a globally-set default Dev Hub org.
-- `ALLOW_ALL_ORGS` - Allow access to all authorized orgs. Use this value with caution.
-- `<username or alias>` - Allow access to a specific org by specifying its username or alias.
-
-This example shows how to specify that the MCP tools run against your default org when you configure the MCP server for VS Code:
-
-```json
-     "mcp": {
-       "servers": {
-         "Salesforce DX": {
-           "type": "stdio",
-           "command": "npx",
-           "args": ["-y", "@salesforce/mcp", "--orgs", "DEFAULT_TARGET_ORG"]
-         }
-       }
-     }
-```
-
-This sample snippet shows how to configure access to your default Dev Hub org and an org with username `test-org@example.com`:
-
-```json
-           "args": ["-y", "@salesforce/mcp", "--orgs", "DEFAULT_TARGET_DEV_HUB,test-org@example.com"]
-```
-
-This sample snippet shows how to configure access to two orgs for which you specified aliases when you authorized them:
-
-```json
-           "args": ["-y", "@salesforce/mcp", "--orgs", "my-scratch-org,my-dev-hub"]
-```
-
-### Configure Toolsets
-
-The Salesforce DX MCP Server supports **toolsets** - a way to selectively enable different groups of MCP tools based on your needs. This allows you to run the MCP server with only the tools you require, which in turn reduces the context.
-
-Use the `--toolsets` (or short name `-t`) argument to specify the toolsets when you configure the Salesforce DX MCP Server. Separate multiple toolsets with commas. The `--toolsets` argument is optional; if you don't specify it, the MCP server is configured with all toolsets.
-
-These are the available toolsets:
-
-- `all` (default) - Enables all available tools from all toolsets.
-- `orgs` - [Tools to manage your authorized orgs.](README.md#orgs-toolset)
-- `data` - [Tools to manage the data in your org, such as listing all accounts.](README.md#data-toolset)
-- `users` - [Tools to manage org users, such as assigning a permission set.](README.md#users-toolset)
-- `metadata` - [Tools to deploy and retrieve metadata to and from your org and your DX project.](README.md#metadata-toolset)
-- `testing` - [Tools to test your code and features](README.md#testing-toolset)
-
-This example shows how to enable the `data`, `orgs`, and `metadata` toolsets when configuring the MCP server for VS Code:
-
-```json
-     "mcp": {
-       "servers": {
-         "Salesforce DX": {
-           "type": "stdio",
-           "command": "npx",
-           "args": ["-y", "@salesforce/mcp", "--orgs", "DEFAULT_TARGET_ORG", "--toolsets", "data,orgs,metadata"]
-         }
-       }
-     }
-```
-
-#### Dynamic Tools (Experimental)
-
-The `--dynamic-tools` flag enables dynamic tool discovery and loading. When this flag is set, the MCP server starts with a minimal set of core tools and will load new tools as the need arises. This is useful for reducing initial context size and improving LLM performance.
-
-**NOTE:** This feature works in VSCode and Cline but may not work in other environments.
-
-#### Core Toolset (always enabled)
-
-Includes these tools:
-
-- `sf-get-username` - Determines the appropriate username or alias for Salesforce operations, handling both default orgs and Dev Hubs.
-- `sf-resume` - Resumes a long-running operation that wasn't completed by another tool.
-- `sf-suggest-cli-command` - Suggests an `sf` Salesforce CLI command based on a natural language query. The tool finds relevant CLI commands from a local index and uses an LLM to construct the precise command to fulfill your request.
-
-#### Orgs Toolset
-
-Includes this tool:
-
-- `sf-list-all-orgs` - Lists all configured Salesforce orgs, with optional connection status checking.
-
-#### Data Toolset
-
-Includes this tool:
-
-- `sf-query-org` - Runs a SOQL query against a Salesforce org.
-
-#### Users Toolset
-
-Includes this tool:
-
-- `sf-assign-permission-set` - Assigns a permission set to the user or on behalf of another user.
-
-#### Metadata Toolset
-
-Includes these tools:
-
-- `sf-deploy-metadata` - Deploys metadata from your DX project to an org.
-- `sf-retrieve-metadata` - Retrieves metadata from your org to your DX project.
-
-#### Testing Toolset
-
-Includes these tools:
-
-- `sf-test-agents` - Executes agent tests in your org.
-- `sf-test-apex` - Executes apex tests in your org.
-
-## Configure Other Clients to Use the Salesforce DX MCP Server
-
-**Cursor**
-
-To configure [Cursor](https://www.cursor.com/) to work with Salesforce DX MCP Server, add this snippet to your Cursor `mcp.json` file:
-
-```json
-{
-  "mcpServers": {
-    "Salesforce DX": {
-      "command": "npx",
-      "args": ["-y", "@salesforce/mcp", "--orgs", "DEFAULT_TARGET_ORG", "--toolsets", "all"]
-    }
-  }
-}
-```
-
-**Cline**
-
-To configure [Cline](https://cline.bot), add this snippet to your Cline `cline_mcp_settings.json` file:
-
-```json
-{
-  "mcpServers": {
-    "Salesforce DX": {
-      "command": "npx",
-      "args": ["-y", "@salesforce/mcp", "--orgs", "DEFAULT_TARGET_ORG", "--toolsets", "all"]
-    }
-  }
-}
-```
-
-**Other Clients**
-
-For these other clients, refer to their documentation for adding MCP servers and follow the same pattern as in the preceding VS Code and Cursor JSON snippets:
-
-- [Claude Desktop](https://claude.ai/download)
-- [Zed](https://github.com/zed-industries/zed)
-- [Windsurf](https://www.windsurf.com/)
-- [Trae](https://trae.ai)

package/lib/assets.d.ts

@@ -1,44 +0,0 @@
-import faiss from 'faiss-node';
-import { FeatureExtractionPipeline } from '@huggingface/transformers';
-type CommandData = {
-    id: number;
-    command: string;
-    summary: string;
-    description: string;
-    examples?: string[];
-    flags?: Array<{
-        name: string;
-        description: string;
-        type?: string;
-        required?: boolean;
-        options?: string[];
-        atLeastOne?: boolean;
-        exactlyOne?: boolean;
-        relationships?: string[];
-        default?: string | boolean | number | string[];
-    }>;
-    embeddingText: string;
-};
-type Assets = {
-    commands: CommandData[];
-    commandNames: string[];
-    faissIndex: faiss.IndexFlatL2;
-    embedder: FeatureExtractionPipeline;
-};
-/**
- * Conditionally builds or rebuilds a FAISS index based on its existence and age.
- *
- * This function checks if a FAISS index file exists in the specified output directory.
- * If the index exists but is older than one week, it triggers a rebuild. If the index
- * doesn't exist, it initiates the initial build process. The build process can run as a
- * detached child process or in the same process depending on the detached parameter.
- *
- * @param outputDir - The directory path where the FAISS index should be located or created
- * @param detached - Whether to run the build process detached (default: true)
- *
- * @remarks
- * - Sets the global CACHED_DATA_DIR variable to the provided outputDir. This is used to locate the index file.
- */
-export declare function maybeBuildIndex(outputDir: string, detached?: boolean): Promise<void>;
-export declare function getAssets(): Promise<Assets>;
-export {};

package/lib/shared/params.d.ts

@@ -1,5 +0,0 @@
-import { z } from 'zod';
-export declare const usernameOrAliasParam: z.ZodString;
-export declare const useToolingApiParam: z.ZodOptional<z.ZodBoolean>;
-export declare const baseAbsolutePathParam: z.ZodEffects<z.ZodString, string, string>;
-export declare const directoryParam: z.ZodEffects<z.ZodString, string, string>;

package/lib/shared/params.js

@@ -1,46 +0,0 @@
-/*
- * Copyright 2025, Salesforce, Inc.
- *
- * Licensed under the Apache License, Version 2.0 (the "License");
- * you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- *
- *     http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-import { z } from 'zod';
-import { sanitizePath } from './utils.js';
-/*
- * A collection of reusable Tool parameters
- */
-export const usernameOrAliasParam = z.string()
-    .describe(`The username or alias for the Salesforce org to run this tool against.
-
-AGENT INSTRUCTIONS:
-If it is not clear what username or alias is, run the #sf-get-username tool.
-NEVER guess or make-up a username or alias, use #sf-get-username if you are not sure.
-DO NOT use #sf-get-username if the user mentions an alias or username, like "for my an-alias org" or "for my test-prgelc2petd9@example.com org".
-
-USAGE:
-...for the my-alias org
-...for my 'my-alias' user
-...for alias myAlias
-...for my 'test@example.com' user
-...for the 'test@example.com' org`);
-export const useToolingApiParam = z.boolean().optional().describe('Use Tooling API for the operation');
-export const baseAbsolutePathParam = z
-    .string()
-    .refine(sanitizePath, 'Invalid path: Must be an absolute path and cannot contain path traversal sequences');
-export const directoryParam = baseAbsolutePathParam.describe(`The directory to run this tool from.
-AGENT INSTRUCTIONS:
-We need to know where the user wants to run this tool from.
-Look at your current Workspace Context to determine this filepath.
-ALWAYS USE A FULL PATH TO THE DIRECTORY.
-Unless the user explicitly asks for a different directory, or a new directory is created from the action of a tool, use this same directory for future tool calls.
-`);
-//# sourceMappingURL=params.js.map

package/lib/shared/tools.d.ts

@@ -1,68 +0,0 @@
-import { RegisteredTool } from '@modelcontextprotocol/sdk/server/mcp.js';
-export declare const TOOLSETS: readonly ["orgs", "data", "users", "metadata", "testing", "experimental"];
-type Toolset = (typeof TOOLSETS)[number];
-export declare const CORE_TOOLS: string[];
-/**
- * Determines which toolsets should be enabled based on the provided toolsets array and dynamic tools flag.
- *
- * @param {Array<Toolset | 'all'>} toolsets - Array of toolsets to enable. Can include 'all' to enable all non-experimental toolsets.
- * @param {boolean} dynamicTools - Flag indicating whether dynamic tools should be enabled. When true, only core and dynamic toolsets are enabled.
- * @returns {Record<Toolset | 'dynamic' | 'core', boolean>} Object mapping each toolset to a boolean indicating whether it should be enabled.
- *
- * @example
- * // Enable all toolsets except experimental
- * determineToolsetsToEnable(['all'], false)
- * // Returns: { core: true, data: true, dynamic: false, experimental: false, metadata: true, orgs: true, testing: true, users: true }
- *
- * @example
- * // Enable only dynamic tools
- * determineToolsetsToEnable([], true)
- * // Returns: { core: true, data: false, dynamic: true, experimental: false, metadata: false, orgs: false, testing: false, users: false }
- *
- * @example
- * // Enable specific toolsets
- * determineToolsetsToEnable(['data', 'users'], false)
- * // Returns: { core: true, data: true, dynamic: false, experimental: false, metadata: false, orgs: false, testing: false, users: true }
- */
-export declare function determineToolsetsToEnable(toolsets: Array<Toolset | 'all'>, dynamicTools: boolean): Record<Toolset | 'dynamic' | 'core', boolean>;
-/**
- * Add a tool to the cache
- */
-export declare function addTool(tool: RegisteredTool, name: string): Promise<{
-    success: boolean;
-    message: string;
-}>;
-/**
- * Enable an individual tool
- */
-export declare function enableTool(toolName: string): Promise<{
-    success: boolean;
-    message: string;
-}>;
-export declare function enableTools(tools: string[]): Promise<Array<{
-    success: boolean;
-    message: string;
-}>>;
-/**
- * Disable an individual tool
- */
-export declare function disableTool(toolName: string): Promise<{
-    success: boolean;
-    message: string;
-}>;
-/**
- * Get individual tool status
- */
-export declare function getToolStatus(toolName: string): Promise<{
-    enabled: boolean;
-    description: string;
-} | undefined>;
-/**
- * List all individual tools with their status
- */
-export declare function listAllTools(): Promise<Array<{
-    name: string;
-    enabled: boolean;
-    description: string;
-}>>;
-export {};

package/lib/shared/types.d.ts

@@ -1,33 +0,0 @@
-import { ConfigInfo } from '@salesforce/core';
-import { type Nullable } from '@salesforce/ts-types';
-import { RegisteredTool } from '@modelcontextprotocol/sdk/server/mcp.js';
-export type ConfigInfoWithCache = {
-    key: string;
-    location?: ConfigInfo['location'];
-    value: string;
-    cached?: boolean;
-    path: string;
-};
-export type SanitizedOrgAuthorization = {
-    aliases?: Nullable<string[]>;
-    configs?: Nullable<string[]>;
-    username?: string;
-    instanceUrl?: string;
-    isScratchOrg?: boolean;
-    isDevHub?: boolean;
-    isSandbox?: boolean;
-    orgId?: string;
-    oauthMethod?: string;
-    isExpired?: boolean | 'unknown';
-};
-export type ToolTextResponse = {
-    isError: boolean;
-    content: Array<{
-        type: 'text';
-        text: string;
-    }>;
-};
-export type ToolInfo = {
-    tool: RegisteredTool;
-    name: string;
-};

package/lib/shared/utils.d.ts

@@ -1,11 +0,0 @@
-import { type ToolTextResponse } from './types.js';
-export declare function textResponse(text: string, isError?: boolean): ToolTextResponse;
-/**
- * Gets the enabled toolsets based on user input and validates against available toolsets
- *
- * @param availableToolsets - The list of available toolsets
- * @param toolsetsInput - The comma-separated list of toolsets
- * @returns A Set of enabled toolsets
- */
-export declare function getEnabledToolsets(availableToolsets: string[], toolsetsInput: string): Set<string>;
-export declare function sanitizePath(projectPath: string): boolean;

package/lib/shared/utils.js

@@ -1,71 +0,0 @@
-/*
- * Copyright 2025, Salesforce, Inc.
- *
- * Licensed under the Apache License, Version 2.0 (the "License");
- * you may not use this file except in compliance with the License.
- * You may obtain a copy of the License at
- *
- *     http://www.apache.org/licenses/LICENSE-2.0
- *
- * Unless required by applicable law or agreed to in writing, software
- * distributed under the License is distributed on an "AS IS" BASIS,
- * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
- * See the License for the specific language governing permissions and
- * limitations under the License.
- */
-/* eslint-disable no-console */
-import path from 'node:path';
-// TODO: break into two helpers? One for errors and one for success?
-export function textResponse(text, isError = false) {
-    if (text === '')
-        throw new Error('textResponse error: "text" cannot be empty');
-    return {
-        isError,
-        content: [
-            {
-                type: 'text',
-                text,
-            },
-        ],
-    };
-}
-/**
- * Gets the enabled toolsets based on user input and validates against available toolsets
- *
- * @param availableToolsets - The list of available toolsets
- * @param toolsetsInput - The comma-separated list of toolsets
- * @returns A Set of enabled toolsets
- */
-export function getEnabledToolsets(availableToolsets, toolsetsInput) {
-    const availableToolsetsSet = new Set(availableToolsets);
-    const passedToolsets = toolsetsInput.split(',').map((toolset) => toolset.trim());
-    // Check if any passed toolset is not in the available list
-    for (const toolset of passedToolsets) {
-        if (!availableToolsetsSet.has(toolset)) {
-            console.error(`Passed toolset "${toolset}" is not in the allowed toolset list. Available toolsets are "all (default), ${Array.from(availableToolsetsSet)
-                .filter((t) => t !== 'all')
-                .join(', ')}"`);
-            process.exit(1);
-        }
-    }
-    const enabledToolsets = new Set(passedToolsets.filter((toolset) => availableToolsetsSet.has(toolset)));
-    console.error('Enabling toolsets:', Array.from(enabledToolsets).join(', '));
-    return enabledToolsets;
-}
-export function sanitizePath(projectPath) {
-    // Decode URL-encoded sequences
-    const decodedProjectPath = decodeURIComponent(projectPath);
-    // Normalize Unicode characters
-    const normalizedProjectPath = decodedProjectPath.normalize();
-    // Check for various traversal patterns
-    const hasTraversal = normalizedProjectPath.includes('..') ||
-        normalizedProjectPath.includes('\u2025') || // Unicode horizontal ellipsis
-        normalizedProjectPath.includes('\u2026'); // Unicode vertical ellipsis
-    // `path.isAbsolute` doesn't cover Windows's drive-relative path:
-    // https://github.com/nodejs/node/issues/56766
-    //
-    // we can assume it's a drive-relative path if it's starts with `\`.
-    const isAbsolute = path.isAbsolute(projectPath) && (process.platform === 'win32' ? !projectPath.startsWith('\\') : true);
-    return !hasTraversal && isAbsolute;
-}
-//# sourceMappingURL=utils.js.map

package/lib/tools/core/index.d.ts

@@ -1,3 +0,0 @@
-export * from './sf-get-username.js';
-export * from './sf-resume.js';
-export * from './sf-suggest-cli-command.js';

package/lib/tools/core/sf-get-username.d.ts

@@ -1,17 +0,0 @@
-import { z } from 'zod';
-import { SfMcpServer } from '../../sf-mcp-server.js';
-export declare const getUsernameParamsSchema: z.ZodObject<{
-    defaultTargetOrg: z.ZodDefault<z.ZodOptional<z.ZodBoolean>>;
-    defaultDevHub: z.ZodDefault<z.ZodOptional<z.ZodBoolean>>;
-    directory: z.ZodEffects<z.ZodString, string, string>;
-}, "strip", z.ZodTypeAny, {
-    defaultTargetOrg: boolean;
-    defaultDevHub: boolean;
-    directory: string;
-}, {
-    directory: string;
-    defaultTargetOrg?: boolean | undefined;
-    defaultDevHub?: boolean | undefined;
-}>;
-export type GetUsernameParamsSchema = z.infer<typeof getUsernameParamsSchema>;
-export declare const registerToolGetUsername: (server: SfMcpServer) => void;