Fix screenshot image format, add tool filtering, and CI/CD#1
Merged
Conversation
- Return MCP ImageContent from zaparoo_screenshot instead of JSON text - Add --allowed-tools/--blocked-tools config for tool allow/block lists - Add CI workflow (lint, build, test) and release workflow (npm publish) - Bump version to 1.1.0
npm 11.6.0 had a bug (npm/cli#8726) where peerOptional dependencies were not properly resolved in lockfiles, causing npm ci to fail on different platforms. Fixed in npm 11.10.1+.
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
1 participant
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.
Summary
zaparoo_screenshotnow returns MCPImageContent(type: 'image') instead of JSON-stringified base64 text, so clients can render the image natively--allowed-tools/ZAPAROO_ALLOWED_TOOLSand--blocked-tools/ZAPAROO_BLOCKED_TOOLSconfig options let users restrict which tools are exposed