-
Notifications
You must be signed in to change notification settings - Fork 631
🐞 Bug: Since the update my taskmaster is not working #316
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
Can I see your mcp.json config ? |
MCP is pointing as a variable to .env -- this exact setup was working this weekend. {
"mcpServers": {
"context7": {
"command": "npx",
"args": ["-y", "@upstash/context7-mcp@latest"]
},
"taskmaster-ai": {
"command": "npx",
"args": ["-y", "task-master-mcp"],
"env": {
"ANTHROPIC_API_KEY": "${ANTHROPIC_API_KEY}",
"PERPLEXITY_API_KEY": "${PERPLEXITY_API_KEY}",
"MODEL": "${MODEL}",
"PERPLEXITY_MODEL": "${PERPLEXITY_MODEL}",
"MAX_TOKENS": "${MAX_TOKENS}",
"TEMPERATURE": "${TEMPERATURE}",
"DEFAULT_SUBTASKS": "${DEFAULT_SUBTASKS}",
"DEFAULT_PRIORITY": "${DEFAULT_PRIORITY}"
}
},
"notionApi": {
"command": "npx",
"args": ["-y", "@notionhq/notion-mcp-server"],
"env": {
"OPENAPI_MCP_HEADERS": "{\"Authorization\": \"Bearer ${NOTION_API_KEY}\", \"Notion-Version\": \"2022-06-28\" }"
}
},
"browserbase": {
"command": "node",
"args": ["path/to/mcp-server-browserbase/browserbase/dist/index.js"],
"env": {
"BROWSERBASE_API_KEY": "<YOUR_BROWSERBASE_API_KEY>",
"BROWSERBASE_PROJECT_ID": "<YOUR_BROWSERBASE_PROJECT_ID>"
}
}
}
} here's my .env file # Required
ANTHROPIC_API_KEY=sk-ant-api03-blahblahbalbabh-U9hhfwAA
PERPLEXITY_API_KEY=pplx-YcuzPblabhalhbabalhbalhabaBxo0untrfuuuSlaK8i
NOTION_API_KEY=ntn_2292397blahablabhablahb
# Optional - defaults shown
MODEL=claude-3-7-sonnet-20250219 # Recommended models: claude-3-7-sonnet-20250219, claude-3-opus-20240229 (Required)
PERPLEXITY_MODEL=sonar-pro # Make sure you have access to sonar-pro otherwise you can use sonar regular (Optional)
MAX_TOKENS=64000 # Maximum tokens for model responses (Required)
TEMPERATURE=0.6 # Temperature for model responses (0.0-1.0) - lower = less creativity and follow your prompt closely (Required)
DEBUG=true # Enable debug logging (true/false)
LOG_LEVEL=info # Log level (debug, info, warn, error)
DEFAULT_SUBTASKS=5 # Default number of subtasks when expanding
DEFAULT_PRIORITY=medium # Default priority for generated tasks (high, medium, low)
PROJECT_NAME=mermaidlens-opacity-fade # Project name for tasks.json metadata |
I have a similar problem, I am not using MCP, the error occurred when I tried to run the basic "expand" command for the specified task. |
wondering if the issue is the fact that you're using ${ENV_VARIABLE} instead of the actual variable, haven't really tested that out much |
I also have the same problem. I tried using the actual variable instead of ${ENV_VARIABLE}, but I still get the same error. |
I'm having the same issue |
Never share your API keys. Make sure you roll the API keys in your .env. If you share your .env make sure to remove the API keys. The issue is you are using incorrect args Change from To IF YOU ARE HAVING ISSUES PLEASE RE READ THE README AND VERIFY YOU ARE USING THE CORRECT ARGUMENTS PER THE LAST VERSION. |
To @thisoceanfox did this work for you? I still have the same problem.... |
No it didn't work |
Ok, I found an issue. Remove ALL the comments after parameter definitions like: |
What just worked is running a chained terminal command export ANTHROPIC_API_KEY=your-key-here && tm parse-prd path-to-prd.txt |
Yes, just clean up your .env from all the comments and it should work |
Cleaned the comments. Seems like some tool calls to the MCP are working while others aren't. I supposed it's backfalling to terminal commands when the MCP fails? Also when it finishes because it maxed out tool calls (25 tool calls), I click Happened twice so far, same situation. End of thread, continue, connection error. Definitely don't have internet or VPN issues. |
Same issue -- cleaning up the env file didn't work. |
Could it be that the And Cursor respects everything in And at the moment The Cursor Agent can't read the Suspicion inspired by me trying to put my secret key in Cursor sends a warning that it can't see the MCP configuration. Could it be...? |
Hmm, interesting use case, I've never had an issue with gitignoring the mcp.json, but definitely something I need to try out and test |
I'm sorry guys, I feel like you are all describing the same issue, but my gut tells me you're all experiencing different causes of the same issue. There are multiple factors to consider:
So bear with me while I try to resolve all your issues. We have many issues that you can find regarding windows, mac, etc.. Please stay active on these issues and lets figure out a solution to everyone. If we have to do bug fixes we will, if we have to improve the readme, we will. etc... |
Thanks for your attention @Crunchyman-ralph I tried checking out this dude's thing but it doesn't seem to work: The secure(ish) workaround for this... for now... Make a Notepad with this info. Happy hunting 🌊🦊🩵 tm-workaround-for-api-issuesAlways use taskmaster CLI commands instead of MCP. Taskmaster is having an issue reading the API keys, so whenever we need to run these commands, run them in terminal and prepend my keys in a chained command, like so: export ANTHROPIC_API_KEY=sk-ant-api03-blahblahblahblah-Mgn3VTBPkZBUIjuHUpbHEw-U9hhfwAA && export PERPLEXITY_API_KEY=pplx-blahblahblahblah0untrfuuuSlaK8i && task-master # Continue with the desired command and its options detailed below Here's the filtered list of commands that require the Claude and Perplexity API keys, with complete CLI command examples including all options:
|
Thanks for this -- the workaround worked for me. Importantly / perhaps obviously, this requires folks to manually paste these in the terminal when you ask the agent to prepare it -- ie if you're parsing a new project PRD and generating your first set of tasks -- it will look something like this depending on your setup.
|
No, th answer is not to manually paste sensitive ENV keys anywhere. If you use CLI commands, it will pull the ENV from the local .env file. If the keys are not working, it's either because the arguments for the MCP server are incorrect or malformed. Comments in the mcp.json shouldn't be there to begin with. Comments in the .env file are fine. It's important that you share your mcp.json (without keys!) so I can check for any issues. The fact thousands of users on the same version are using it without problem points to this most likely being a config issue. |
Had great success before the most recent update.
Error message
Originally posted by @thisoceanfox in #294
The text was updated successfully, but these errors were encountered: