Update README.md with MCP setup details for Warp#1268
Closed
TheLazyIndianTechie wants to merge 2 commits intoeyaltoledano:mainfrom
Closed
Update README.md with MCP setup details for Warp#1268TheLazyIndianTechie wants to merge 2 commits intoeyaltoledano:mainfrom
TheLazyIndianTechie wants to merge 2 commits intoeyaltoledano:mainfrom
Conversation
Added 3 ways of adding Task Master MCP to Warp
|
Contributor
WalkthroughAdds a new Warp (mcpServers) usage section to README.md with a JSON example and step-by-step setup instructions (slash command, Settings path, Command Palette). No code or public API changes. Changes
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
Suggested reviewers
Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
📜 Recent review detailsConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro 📒 Files selected for processing (1)
🧰 Additional context used🧠 Learnings (6)📚 Learning: 2025-09-24T15:12:58.855ZApplied to files:
📚 Learning: 2025-07-18T17:06:04.909ZApplied to files:
📚 Learning: 2025-07-18T17:10:53.657ZApplied to files:
📚 Learning: 2025-07-31T22:08:16.039ZApplied to files:
📚 Learning: 2025-07-18T17:10:02.683ZApplied to files:
📚 Learning: 2025-07-31T22:08:16.039ZApplied to files:
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Actionable comments posted: 1
📜 Review details
Configuration used: Path: .coderabbit.yaml
Review profile: ASSERTIVE
Plan: Pro
📒 Files selected for processing (1)
README.md(1 hunks)
🧰 Additional context used
🧠 Learnings (6)
📚 Learning: 2025-09-24T15:12:58.855Z
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: assets/AGENTS.md:0-0
Timestamp: 2025-09-24T15:12:58.855Z
Learning: Applies to assets/**/.mcp.json : Configure the Task Master MCP server in .mcp.json under mcpServers.task-master-ai using npx task-master-ai and provide required API key env vars
Applied to files:
README.md
📚 Learning: 2025-07-18T17:06:04.909Z
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/ai_providers.mdc:0-0
Timestamp: 2025-07-18T17:06:04.909Z
Learning: Applies to .cursor/mcp.json.example : Add the new PROVIDER_API_KEY with its placeholder to the env section for taskmaster-ai in .cursor/mcp.json.example.
Applied to files:
README.md
📚 Learning: 2025-07-31T22:08:16.039Z
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/taskmaster.mdc:0-0
Timestamp: 2025-07-31T22:08:16.039Z
Learning: Applies to {.env,.cursor/mcp.json} : Set API keys for AI providers (e.g., ANTHROPIC_API_KEY, OPENAI_API_KEY, etc.) in your .env file in the project root (for CLI use) or within the env section of your .cursor/mcp.json file (for MCP/Cursor integration).
Applied to files:
README.md
📚 Learning: 2025-07-18T17:10:53.657Z
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/glossary.mdc:0-0
Timestamp: 2025-07-18T17:10:53.657Z
Learning: Guidelines for implementing and interacting with the Task Master MCP Server (mcp.mdc).
Applied to files:
README.md
📚 Learning: 2025-07-18T17:10:02.683Z
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/dev_workflow.mdc:0-0
Timestamp: 2025-07-18T17:10:02.683Z
Learning: Applies to {.env,.cursor/mcp.json} : Store sensitive API keys and endpoint URLs for Taskmaster in a `.env` file (for CLI usage) or in the `env` section of `.cursor/mcp.json` (for MCP/Cursor integration). Do not store non-API key settings in these files.
Applied to files:
README.md
📚 Learning: 2025-07-31T22:08:16.039Z
Learnt from: CR
PR: eyaltoledano/claude-task-master#0
File: .cursor/rules/taskmaster.mdc:0-0
Timestamp: 2025-07-31T22:08:16.039Z
Learning: Applies to .cursor/mcp.json : When using MCP/Cursor integration, ensure that the required API keys are present in the env section of .cursor/mcp.json.
Applied to files:
README.md
🪛 markdownlint-cli2 (0.18.1)
README.md
158-158: Fenced code blocks should be surrounded by blank lines
(MD031, blanks-around-fences)
179-179: Fenced code blocks should be surrounded by blank lines
(MD031, blanks-around-fences)
182-182: Ordered list item prefix
Expected: 1; Actual: 2; Style: 1/2/3
(MD029, ol-prefix)
183-183: Ordered list item prefix
Expected: 2; Actual: 3; Style: 1/2/3
(MD029, ol-prefix)
- Add blank line before JSON code fence to fix MD031 violation - Indent code fence and blockquote with 3 spaces to maintain list structure - Fix list numbering continuity (MD029) by proper nesting - Ensure proper spacing between elements for better readability
Crunchyman-ralph
requested changes
Oct 3, 2025
Collaborator
Crunchyman-ralph
left a comment
Crunchyman-ralph
left a comment
There was a problem hiding this comment.
@TheLazyIndianTechie instead of adding it directly to the readme, making it redundant and making the list too long, maybe you can add it to the docs inside apps/docs, thats where we store the docs for docs.task-master.dev
Collaborator
|
Closing this, feel free to take my considerations and create a new PR based on my requested changes. Thanks for contributing! |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Added explicit documentation in README.md describing 3 ways to add Task Master MCP to Warp, including JSON setup, UI instructions, and command palette usage.
What type of PR is this?
Description
This PR adds detailed documentation for integrating Task Master MCP with Warp, including step-by-step configuration instructions for the mcpServers section, replacing API keys, and UI-based methods for adding and enabling the MCP server. This improves clarity for new users on setting up Warp integration.
Related Issues
How to Test This
Review the updated README.md section on Warp MCP setup. Follow the instructions to configure Task Master MCP in Warp using one of the described methods.
Expected result:
Users should be able to set up Task Master MCP in Warp following the documentation.
Contributor Checklist
npm run changesetnpm testnpm run format-check(ornpm run formatto fix)Changelog Entry
Added Warp setup instructions for Task Master MCP in README.
For Maintainers
Summary by CodeRabbit