← smithai.me

INDIVIDUAL MCP TOOL

get_case_study

Returns the vetted summary of one of Ryan Smith's four signature case studies, with a link to the full write-up on smithai.me.

smithai.menone authenticationAvailability not checked

LIVE ENDPOINT

https://smithai.me/api/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_case_study and invoke it with your own arguments.

Indexed 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 server

smithai.me

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.smithai-me]
url = "https://smithai.me/api/mcp"
enabled = true
Claude Code

.mcp.json

{
  "mcpServers": {
    "smithai-me": {
      "type": "http",
      "url": "https://smithai.me/api/mcp"
    }
  }
}
Claude Desktop

Settings → Connectors → Add custom connector

Name: smithai-me
Remote MCP URL: https://smithai.me/api/mcp

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": {
    "smithai-me": {
      "url": "https://smithai.me/api/mcp"
    }
  }
}
Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code
{
  "servers": {
    "smithai-me": {
      "type": "http",
      "url": "https://smithai.me/api/mcp"
    }
  }
}
Generic MCP

Client-specific MCP configuration

{
  "name": "smithai-me",
  "transport": "streamable-http",
  "url": "https://smithai.me/api/mcp"
}
MCP Inspector

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

Related tools

  • ask_about_ryan — Ask a question about Ryan Smith's work history, AI product leadership, metrics, leadership style, or background.
  • check_fit — Paste a job description and get an honest, structured fit read for Ryan Smith: where he's strong (tied to specific projects), what's adjacent, and candid gaps relative to the role — gaps are named, never papered over.
  • get_beyond_the_resume — Depth that doesn't land on a résumé: the technologies Ryan Smith actually works with (honestly tiered, including what he does NOT claim), a side build, what he values, and how he works.