fix: Smithery installs (env token) + honest HTTP docs (#43)

* 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.

* 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).

* 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.

Author: johnxie

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
 

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",

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:
-    |-
-    (config) => ({ command: 'npx', args: ['-y', '@taskade/mcp-server', '--token', config.apiKey] })
+  commandFunction: |-
+    (config) => ({ command: 'npx', args: ['-y', '@taskade/mcp-server'], env: { TASKADE_API_KEY: config.apiKey } })