From 06c36fee6f30de8d0cbd0779e8e258a2c26bda5b Mon Sep 17 00:00:00 2001 From: johnxie Date: Fri, 5 Jun 2026 04:15:14 -0700 Subject: [PATCH 1/3] fix: pass Smithery API key via env, not the ignored --token flag The published CLI reads only the TASKADE_API_KEY env var and parses no argv, so smithery.yaml passing ['--token', config.apiKey] meant every Smithery stdio install started with no token and exited with the validateAccessToken error. Switch the commandFunction to set env: { TASKADE_API_KEY: config.apiKey }. Also correct the n8n example docs: the --http/--token flags are not supported by the published CLI (stdio only); point HTTP/remote use to hosted endpoint #6. --- examples/README.md | 10 +--------- smithery.yaml | 2 +- 2 files changed, 2 insertions(+), 10 deletions(-) diff --git a/examples/README.md b/examples/README.md index 463e078..80eb058 100644 --- a/examples/README.md +++ b/examples/README.md @@ -29,15 +29,7 @@ Ask the AI agent natural language questions like: - "What tasks are overdue?" - "Create an AI agent that monitors project deadlines" -### Alternative: HTTP/SSE mode - -If you prefer to run the MCP server as a standalone HTTP service: - -```bash -PORT=3001 npx @taskade/mcp-server --http --token YOUR_TASKADE_API_KEY -``` - -Then configure the n8n MCP node to use **HTTP Streamable** transport with URL `http://localhost:3001/mcp`. +> **Note:** The published `@taskade/mcp-server` CLI runs over **stdio** only — configure the n8n MCP Client node with the command `npx -y @taskade/mcp-server` and a `TASKADE_API_KEY` environment variable. The `--http`/`--token` flags are **not** supported by the published CLI. A standalone HTTP/SSE transport is not yet exposed; track the hosted remote endpoint at [#6](https://github.com/taskade/mcp/issues/6). ## More examples coming soon diff --git a/smithery.yaml b/smithery.yaml index e3eca7d..da715a4 100644 --- a/smithery.yaml +++ b/smithery.yaml @@ -12,4 +12,4 @@ startCommand: description: "Your Taskade API key. Get it from Taskade Settings > API." commandFunction: |- - (config) => ({ command: 'npx', args: ['-y', '@taskade/mcp-server', '--token', config.apiKey] }) + (config) => ({ command: 'npx', args: ['-y', '@taskade/mcp-server'], env: { TASKADE_API_KEY: config.apiKey } }) From 5917f7e019805de0a0fb03aeb19ed1bc9da98655 Mon Sep 17 00:00:00 2001 From: johnxie Date: Fri, 5 Jun 2026 04:31:19 -0700 Subject: [PATCH 2/3] fix(examples): n8n workflow passes token via environments, not --token Addresses Copilot review: the n8n workflow node still used the ignored --token CLI flag. Pass TASKADE_API_KEY via the node's environments field so the imported workflow actually authenticates (consistent with the stdio docs). --- examples/n8n-taskade-mcp-workflow.json | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/examples/n8n-taskade-mcp-workflow.json b/examples/n8n-taskade-mcp-workflow.json index 24293d3..9c1e221 100644 --- a/examples/n8n-taskade-mcp-workflow.json +++ b/examples/n8n-taskade-mcp-workflow.json @@ -43,7 +43,8 @@ "parameters": { "connectionType": "stdio", "command": "npx", - "arguments": "-y @taskade/mcp-server --token YOUR_TASKADE_API_KEY" + "arguments": "-y @taskade/mcp-server", + "environments": "TASKADE_API_KEY=YOUR_TASKADE_API_KEY" }, "id": "mcp-taskade", "name": "Taskade MCP", From 22988309ebe9f124a0d1b0c3f0dd5d90879b68af Mon Sep 17 00:00:00 2001 From: johnxie Date: Fri, 5 Jun 2026 04:49:52 -0700 Subject: [PATCH 3/3] style(smithery): use canonical block-scalar header on commandFunction Move the |- block-scalar indicator onto the key line (commandFunction: |-) so the YAML is unambiguous for stricter parsers. Parsed value is identical. --- smithery.yaml | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/smithery.yaml b/smithery.yaml index da715a4..0a7e512 100644 --- a/smithery.yaml +++ b/smithery.yaml @@ -10,6 +10,5 @@ startCommand: type: string title: "Taskade API Key" description: "Your Taskade API key. Get it from Taskade Settings > API." - commandFunction: - |- + commandFunction: |- (config) => ({ command: 'npx', args: ['-y', '@taskade/mcp-server'], env: { TASKADE_API_KEY: config.apiKey } })