INDIVIDUAL MCP TOOL

get_design_system

John's Design System, @thejspro/ui, which thejspro.com is built on: the public Storybook, the component and token packages, how the site uses them, and every component and foundation page with a link to its documentation, read live from the published Storybook.

thejspro.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://mcp.thejspro.com/mcp

No auth detected

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

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

A tool name, description or schema mentions credentials.

Parent server

thejspro.com

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.thejspro]
url = "https://mcp.thejspro.com/mcp"
enabled = true

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: thejspro
Remote MCP URL: https://mcp.thejspro.com/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": {
    "thejspro": {
      "url": "https://mcp.thejspro.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "thejspro": {
      "type": "http",
      "url": "https://mcp.thejspro.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "thejspro",
  "transport": "streamable-http",
  "url": "https://mcp.thejspro.com/mcp"
}

MCP Inspector

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

Related tools

get_profile — Who John Jost is, in his own published words: name, title, positioning, location, languages, availability, his core focus areas, the About page in his own words, the span of published projects and the most recent one, and links to the site, the CV (PDF first, then the printable HTML page), the Design System's Storybook and his public profiles.
get_contact — How to reach John, as text and structured data on any host: email, UK and Polish phone numbers, LinkedIn and GitHub, the availability note the site's footer carries, and the CV links.
get_contact_card — John's business card, built from the site's own Design System, for clients that support UI over MCP (MCP apps): his title, name, the availability note the site's footer carries, and his contact channels.
get_availability — Whether John is available and how he can be engaged: fully remote, worldwide, through a UK limited company or a Polish JDG, and open to permanent, fixed-term, contract or B2B on that basis.
get_skills — The skills the site publishes: his core focus areas, each with his own description of the work, and the technology stack by category, each listing its tools.
get_projects — The published projects, newest first: client, agency, year, the title held on that engagement, a summary, tags and sectors.
check_experience — Ask whether the published site documents a topic: a technology, a discipline, a role, a sector or a client.
get_attestations — What named third parties say about John's work, verbatim, with links to confirm each author independently of him, the engagement they speak to, and whether the site itself quotes them.