@flytrap-qa/mcp 0.1.2 → 0.1.3

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@flytrap-qa/mcp",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "MCP server that lets your coding agent read FlyTrap crawl results: bugs with evidence, screen graphs, network hosts, SDKs and build diffs for your own apps.",
   "license": "MIT",
   "type": "module",

package/src/client.js

@@ -16,7 +16,7 @@ const hintFor = (status, hasKey) => {
             ? 'The key was rejected. It may be revoked or expired; create a new one under Settings > API keys.'
             : 'This tool needs FLYTRAP_API_KEY. Create a key in the FlyTrap dashboard under Settings > API keys.'
     if (status === 403)
-        return 'The key does not have the scope for this action. start_crawl needs a key created with the "crawl" scope.'
+        return 'The key does not have the scope for this action. start_crawl, add_competitor and remove_competitor need a key created with the "crawl" scope.'
     if (status === 404)
         return 'Not found, or the key owner has no access to this project.'
     if (status === 429)

package/src/index.js

@@ -13,7 +13,7 @@ const INSTRUCTIONS = `FlyTrap crawls real Android and iOS builds on devices and
 screenshots and logs, network traffic, SDKs and permissions, performance. Public catalog tools (lookup_app,
 get_app_profile, lookup_sdk, lookup_permission) need no key. Project tools need FLYTRAP_API_KEY and only see the
 key owner's projects. Typical flow: list_projects -> list_bugs -> get_bug_evidence (cite run.crawl_run_id and the
-screenshot path). start_crawl is the only mutating tool; ask the user before calling it.`
+screenshot path). start_crawl, add_competitor and remove_competitor are the only mutating tools; ask the user before calling them.`
 
 export const createServer = ({config, fetchImpl} = {}) => {
     const resolved = config ?? loadConfig()