← stumason.dev

INDIVIDUAL MCP TOOL

list-case-studies

Project write-ups: the client, the challenge, what Stu did, and the outcome.

stumason.devnone authenticationAvailability not checked

Input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

  • A tool name or description contains a write-action term.

Parent endpoint

stumason.dev

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.stumason-dev]
url = "https://ai.stumason.dev/mcp/stu"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "stumason-dev": {
      "type": "http",
      "url": "https://ai.stumason.dev/mcp/stu"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: stumason-dev
Remote MCP URL: https://ai.stumason.dev/mcp/stu

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "stumason-dev": {
      "url": "https://ai.stumason.dev/mcp/stu"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "stumason-dev": {
      "type": "http",
      "url": "https://ai.stumason.dev/mcp/stu"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "stumason-dev",
  "transport": "streamable-http",
  "url": "https://ai.stumason.dev/mcp/stu"
}
MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

  • get-offer — Who Stu Mason is and what he offers, in one call: a plain-English summary, the white-label offer pillars, and where to find the proof and make contact.
  • list-proof — The proof library: real, shipped AI work you can open and inspect.
  • get-proof — Full detail on one proof item by its key (from list-proof), including its URL and machine-readable .md twin where one exists.
  • list-reviews — Real, named reviews of working with Stu, from people at real companies (not anonymous quotes).
  • get-faq — The questions agencies usually ask before hiring Stu, with his answers: rate model, capacity and lead time, stack and what he will not touch, white-label working, how he keeps AI-written code safe, references, insurance (PI/public/employers), IP and NDAs, and the solo-operator continuity plan.
  • send-message — Send a short message to Stu, on your human's behalf.
  • request-scope — Hand Stu a structured brief for a piece of work, on your human's behalf: what they want to build, their stack, timeline and budget.