MCP declarative-agent template cannot be used non-interactively and leaves a partial scaffold
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 22
- Forks
- 4
- Avg merge
- 6h 20m
- Merged PRs (30d)
- 4
Description
Observed with WIQD 0.12.2 on Windows.
Problem
The declarative-agent-with-action-from-mcp template cannot be used non-interactively, even though
it is returned by wiqd agent create list.
Steps to reproduce
-
Run:
wiqd agent create --template declarative-agent-with-action-from-mcp --name mcp-test --output ./mcp-test -
Observe exit code 1 and:
Scaffold.InputValidationFailed: mcpServerUrl is required when --api-plugin-type is mcp -
Run
wiqd agent create --help. It exposes only the template, name, and output options. -
Try supplying the required URL with
--mcp-server-url,--mcpServerUrl, or--server-url.
Each is rejected as an unknown option. -
Inspect the output directory left by the failed command.
Actual behavior
There is no exposed CLI option for supplying the required MCP server URL. Despite returning exit
code 1, the command leaves a partial scaffold containing appPackage/ai-plugin.json with empty
functions and runtimes. The partial project omits files produced by a successful base scaffold,
including:
m365agents.local.ymlenv/.env.local.vscode/tasks.json
Continuing from this residue produces a project that cannot provision normally. The practical
workaround is to delete the partial project, scaffold the base declarative-agent template, and
author the MCP plugin manifest manually.
Expected behavior
- The template should expose and document a non-interactive option for the MCP server URL.
- A successful invocation should produce a complete project.
- If input validation fails before scaffolding, the operation should be atomic and leave no partial
project on disk.
Environment
| Component | Value |
|---|---|
| WIQD | 0.12.2 |
| OS | Windows (win32) |
| Node.js | v24.19.0 |
| GitHub CLI | 2.87.3 |
| Shell | PowerShell |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the wiqd agent create command and trace how the declarative-agent-with-action-from-mcp template exposes options, validates mcpServerUrl, and writes the output directory. Inspect the generated appPackage/ai-plugin.json and compare it with the listed files from a successful base scaffold; done means the URL is supported non-interactively and validation leaves no partial project.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- node.js, powershell
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100