SketchXFlow developer MCP server — for the SketchXFlow delivery team: pull client requirements, post updates, log time and move milestones from Claude, Cursor, and any MCP client. Staff API keys only.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
SKETCHXFLOW_API_KEYAPI keyoptionalOptional. Overrides the key obtained by signing in with sketchxflow_dev_login — for CI or shared runners.
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
sketchxflow_dev_loginSign this machine in as a SketchXFlow team member — no API key to paste. Returns a link and a short code: the developer opens the link in a browser where they are signed in to the staff console, checks the code matches and approves. Call it again (or any other tool) after approving. Already signed…Sign this machine in as a SketchXFlow team member — no API key to paste. Returns a link and a short code: the developer opens the link in a browser where they are signed in to the staff console, checks the code matches and approves. Call it again (or any other tool) after approving. Already signed…
No input schema was published for this tool.
sketchxflow_dev_logoutForget this machine's key. To end it server-side as well, revoke the key named “Developer MCP · <machine>” in Account → API keys.Forget this machine's key. To end it server-side as well, revoke the key named “Developer MCP · <machine>” in Account → API keys.
No input schema was published for this tool.
sketchxflow_dev_versionReport which version of the SketchXFlow developer MCP is running, whether a newer one is published, and whether the configured SKETCHXFLOW_API_KEY (shown only by its sk_live_ab12cd… prefix) belongs to an active SketchXFlow team member. Free. Call it first when another tool refuses.Report which version of the SketchXFlow developer MCP is running, whether a newer one is published, and whether the configured SKETCHXFLOW_API_KEY (shown only by its sk_live_ab12cd… prefix) belongs to an active SketchXFlow team member. Free. Call it first when another tool refuses.
No input schema was published for this tool.
sketchxflow_dev_workLive development-services projects assigned to you, with state, progress and what needs attention. Set mine=false for every live project. Staff API keys only.Live development-services projects assigned to you, with state, progress and what needs attention. Set mine=false for every live project. Staff API keys only.
No input schema was published for this tool.
sketchxflow_dev_pullThe frozen requirements as text, the priced modules, the milestones with dates and the latest client messages — everything needed to start building. Staff API keys only.The frozen requirements as text, the priced modules, the milestones with dates and the latest client messages — everything needed to start building. Staff API keys only.
No input schema was published for this tool.
sketchxflow_dev_updatePost a progress update the client sees in their project room (markdown), optionally against a milestone. Staff API keys only.Post a progress update the client sees in their project room (markdown), optionally against a milestone. Staff API keys only.
No input schema was published for this tool.
sketchxflow_dev_messageSend a message in the project room. internal=true keeps it to the team. Staff API keys only.Send a message in the project room. internal=true keeps it to the team. Staff API keys only.
No input schema was published for this tool.
sketchxflow_dev_log_timeLog hours worked on a project (coarse — a day's hours), optionally against a module key or milestone. Staff API keys only.Log hours worked on a project (coarse — a day's hours), optionally against a module key or milestone. Staff API keys only.
No input schema was published for this tool.
sketchxflow_dev_milestoneMark a milestone as started, or submit it for the client's review (which starts their review window). Staff API keys only.Mark a milestone as started, or submit it for the client's review (which starts their review window). Staff API keys only.
No input schema was published for this tool.
9 of 9 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
SketchXFlow developer MCP server — for the SketchXFlow delivery team: pull client requirements, post updates, log time and move milestones from Claude, Cursor, and any MCP client. Staff API keys only.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the depth-4 limit. Anything below that level was never resolved.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+42 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.