-
Notifications
You must be signed in to change notification settings - Fork 78
chore(claude-code): limit MCP tools for task reporting #507
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
Conversation
We only need the single `report tasks` tool for tasks reporting. Also, you don't need to inject all Coder tools when no task reporting is required. Coder MCP tools are usually useful when used from an external system rather than within Coder Tasks.
Moved the `CODER_MCP_ALLOWED_TOOLS` export to the `start.sh` script for task reporting. This change clarifies tool permissions at startup.
|
@DevelopmentCats can you help here? Mainly testing. I moved the env to |
|
@matifali This seems fine to me after testing. The ai seems to only be aware of the
|
|
What if we move it back to the |
setting up to pull locally so I can test this |
|
@DevelopmentCats can I get an approval then? |
❌ Version Bump Validation FailedBump Type: Module versions need to be updated but haven't been bumped yet. Required Actions:
Script Output:
|
|
@DevelopmentCats this is a false positive - boundary_version = "main"
+ boundary_version = "3.3.1" |
|
post-merge 👍 |


We only need the single
coder_report_tasktool for task reporting. Also, you don't need to use all Coder tools when no task reporting is required.Coder MCP tools are usually helpful when used from an external system rather than within Coder Tasks.
Description
Type of Change
Module Information
Path:
registry/coder/modules/claude-codeNew version:
v3.3.1Breaking change: [ ] Yes [x] No
Testing & Validation
bun test)bun fmt)Related Issues