Cannot create ToolingManifest.json without project path anymore (Agent 365 x n8n)

[pdwarf]

Description

For setting up an Agent 365-powered Agent=AI Teammate in n8n, in the past you'd run something like a365 develop add-mcp-servers mcp_M365Copilot mcp_CalendarTools mcp_MailTools mcp_SharePointRemoteServer mcp_OneDriveRemoteServer mcp_TeamsServer mcp_WordServer in any local directory that you're creating a new Blueprint in. It would create the ToolingManifest.json file if none existed, and add the respective entries.

Now, this produces an error that there is no agent project directory found. This is expected when building with n8n, as you're not writing an Agent with code, but the n8n Agent 365 Trigger node is handling this.

Expected behavior

• Running a365 develop add-mcp-servers [...] should behave as it did, allowing creating of a ToolingManifest.json file without the need to specify a project path.

SDK Version

n/a

Language/Runtime

n/a

OS

macOS

How to Reproduce

1. run the above command in a blank directory
2. get the error

Output

See above

Screenshots

See above

Code of Conduct

• I agree to follow the Microsoft Open Source Code of Conduct.