Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Agent 365 CLI
Manage MCP tool servers for agent development. The develop command provides options to manage MCP (Model Context Protocol) tool servers for agent development. You can list available servers, view configured servers, and add or remove MCP servers from your agent configuration.
Minimum role required: None (local manifest management)
Syntax
a365 develop [command] [options]
Options
| Option | Description |
|---|---|
-c, --config <config> |
Configuration file path. Default: a365.config.json |
-v, --verbose |
Enable verbose logging |
-?, -h, --help |
Show help and usage information. |
develop list-available
List all MCP servers available in the catalog (what you can install).
a365 develop list-available [options]
This command displays all MCP servers that are available in the catalog and you can install them for use with your agent development.
list-available options
| Option | Description |
|---|---|
--dry-run |
Show what the command would do without executing it. |
--skip-auth |
Skip authentication. For testing only. The command likely fails without valid authentication. |
-?, -h, --help |
Show help and usage information. |
Note
develop list-available doesn't require a365.config.json. It reads the environment from the A365_ENVIRONMENT environment variable (defaults to prod).
develop list-configured
List currently configured MCP servers from your local ToolingManifest.json.
a365 develop list-configured [options]
This command shows all MCP servers that you currently configured in your local ToolingManifest.json file.
list-configured options
| Option | Description |
|---|---|
--project-path <path> |
Path to the agent project directory containing ToolingManifest.json. Overrides DeploymentProjectPath from a365.config.json. |
--dry-run |
Show what the command would do without executing it. |
-?, -h, --help |
Show help and usage information. |
develop add-mcp-servers
Add MCP Servers to the current agent configuration.
a365 develop add-mcp-servers [<servers>...] [options]
This command adds the specified MCP servers to ToolingManifest.json in your project folder. It doesn't grant permissions to the agent blueprint.
Important
This command only updates ToolingManifest.json - it doesn't grant permissions to the agent blueprint. How you apply permissions depends on where you are in the setup process:
- Before initial setup: Proceed with
a365 setup all. MCP permissions are applied as part of the initial blueprint creation. - After the blueprint already exists: A Global Administrator must run
a365 setup permissions mcpseparately. The admin must verify thatdeploymentProjectPathpoints to the project folder containing the updatedToolingManifest.json.
add-mcp-servers arguments
Specify one or more MCP server names to add to your agent configuration. You can provide multiple server names separated by spaces.
| Argument | Description |
|---|---|
<servers> |
Names of the MCP servers to add |
add-mcp-servers options
Use these options to customize the behavior of the add-mcp-servers command.
| Option | Description |
|---|---|
--project-path <path> |
Path to the agent project directory containing ToolingManifest.json. Overrides DeploymentProjectPath from a365.config.json. |
--dry-run |
Show what the command would do without executing it. |
-?, -h, --help |
Show help and usage information. |
develop remove-mcp-servers
Remove MCP Servers from the current agent configuration.
a365 develop remove-mcp-servers [<servers>...] [options]
This command removes specified MCP servers from your current agent configuration.
remove-mcp-servers arguments
| Argument | Description |
|---|---|
<servers> |
Names of the MCP servers to remove |
remove-mcp-servers options
| Option | Description |
|---|---|
--project-path <path> |
Path to the agent project directory containing ToolingManifest.json. Overrides DeploymentProjectPath from a365.config.json. |
--dry-run |
Show what the command would do without executing it. |
-?, -h, --help |
Show help and usage information. |
develop add-permissions
Add MCP server API permissions to Microsoft Entra applications for development scenarios where you need to configure custom applications to access MCP servers.
a365 develop add-permissions [options]
add-permissions options
Use these options to add required API permissions and scopes to your app registration, leveraging values from the tooling manifest.
| Option | Description |
|---|---|
-c, --config <config> |
Configuration file path (default: a365.config.json) |
-m, --manifest <manifest> |
Path to ToolingManifest.json (default: <deploymentProjectPath>/ToolingManifest.json) |
--app-id <app-id> |
Application (client) ID to add permissions to (default: clientAppId from config) |
--scopes <scopes> |
Specific scopes to add (space-separated) (default: All scopes from ToolingManifest.json) |
--dry-run |
Show what the command would do without making changes |
-v, --verbose |
Show detailed output |
-?, -h, --help |
Show help and usage information. |
Important
The application specified by --app-id or clientAppId must have the Application.ReadWrite.All permission in Microsoft Entra. This command is for custom client applications. To configure permissions for agent blueprints, use a365 setup permissions mcp instead.
develop get-token
Retrieve bearer tokens for testing MCP servers during development using interactive browser authentication.
a365 develop get-token [options]
get-token options
Use these options to request an access token, control scopes, refresh behavior, and choose the output format.
| Option | Description |
|---|---|
-c, --config <config> |
Configuration file path (default: a365.config.json) |
--app-id <app-id> |
Application (client) ID for authentication (default: clientAppId from config) |
-m, --manifest <manifest> |
Path to ToolingManifest.json (default: <deploymentProjectPath>/ToolingManifest.json) |
--scopes <scopes> |
Specific scopes to request (space-separated) (default: Read from ToolingManifest.json) |
-o, --output <output> |
Output format: table, json, or raw (default: table) |
--force-refresh |
Force token refresh bypassing cache |
--resource <resource> |
Resource keyword to get token for: mcp (default) or powerplatform |
--resource-id <resource-id> |
Custom resource application ID (GUID) for resources not covered by --resource keywords |
-v, --verbose |
Show detailed output including full token |
-?, -h, --help |
Show help and usage information. |
get-token resource options
Use the --resource and --resource-id options to get tokens for different Azure resources:
--resource: Use a keyword to select a predefined resource:mcp(default): Agent 365 Tools for MCP serverspowerplatform: Power Platform API
--resource-id: Enter a custom resource application ID (GUID) for resources not covered by keywords
Important
You can't use --resource and --resource-id together. When you use either option, include --scopes. Only the default MCP flow supports manifest-based scope resolution.
develop start-mock-tooling-server
Start a mock tooling server for testing and development purposes.
a365 develop start-mock-tooling-server [options]
This command starts a mock tooling server for testing and development purposes. By using this server, you can simulate MCP server interactions without requiring actual server implementations.
start-mock-tooling-server options
Use these options to customize the behavior of the start-mock-tooling-server command.
| Option | Description | Default |
|---|---|---|
-p, --port <port> |
Port number for the mock server | 5309 |
-v, --verbose |
Enable verbose logging | false |
-?, -h, --help |
Show help and usage information | - |
-bg |
Run the server on a new terminal | - |