Dev Mcp

com.sketchxflowPublished by sketchxflow.comOfficial publisherv0.4.0Updated Oct 27, 2026

SketchXFlow delivery team: pull client requirements, post updates, log time, move milestones.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

SketchXFlow delivery-team MCP server that lets an assistant pull client requirements, post updates, log time and move milestones.

What you can do
  • Pull client requirements from SketchXFlow
  • Post delivery updates
  • Log time entries
  • Move milestones
When to use it
Useful for delivery teams already working in SketchXFlow that want an assistant to fetch client requirements and keep updates, time logs and milestone status current without switching tools.
Requirements
Runs as a remote endpoint or as a local npm package over stdio. OAuth sign-in is required; an optional SKETCHXFLOW_API_KEY environment variable can override the signed-in key for CI or shared runners.
Before you install
The assistant can write to your SketchXFlow workspace: posting updates, logging time and moving milestones all change shared project data. The API key grants access to that workspace, so keep it out of shared or public runner logs.

Installation

In SourceWeft

  1. Open Dev Mcp in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.sketchxflow%2Fdev-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "dev": {
      "type": "http",
      "url": "https://mcp.sketchxflow.com/dev"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.4.0LatestSep 27, 2026
  2. v0.3.0Sep 20, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Sketchxflow integrations