Agent 365 CLI develop command reference

Important

You need to be part of the Frontier preview program to get early access to Microsoft Agent 365. Frontier connects you directly with Microsoft’s latest AI innovations. Frontier previews are subject to the existing preview terms of your customer agreements. As these features are still in development, their availability and capabilities may change over time.

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 can be installed for use with your agent development.

list-available options

Option	Description
-c, --config <config>	Configuration file path (default: a365.config.json)
--dry-run	Show what would be done without executing
--skip-auth	Skip authentication (for testing only - will likely fail without valid auth)
-?, -h, --help	Show help and usage information

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 are currently configured in your local ToolingManifest.json file.

develop add-mcp-servers

Add MCP Servers to the current agent configuration.

a365 develop add-mcp-servers [<servers>...] [options]

This command adds specified MCP servers to your current agent configuration, enabling their use in your development environment.

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, including configuration file selection and dry-run testing.

Option	Description
-c, --config <config>	Configuration file path (default: a365.config.json)
--dry-run	Show what would be done without executing
-?, -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.

develop add-permissions

Add MCP server API permissions to Azure AD 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 would be done without making changes
-v, --verbose	Show detailed output
-?, -h, --help	Show help and usage information

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
-v, --verbose	Show detailed output including full token
-?, -h, --help	Show help and usage information