Developer · Remote MCP server

Workshops

MCP server for Monika Skorykow workshops - browse prices and promotions.

What the MCP Registry states

The entry as published to the official MCP Registry (read 2026-10-04), latest version.

Registry name
com.monikaskorykow/workshops
Version
1.0.0
Status
Active
Category
developer
Transport
SSE (HTTP + Server-Sent Events), stdio (local process)
Package
npm
Published
2025-12-15
Updated
2025-12-15
Publisher
com.monikaskorykow
Repository
github.com/monikaskorykow/mcp-workshops
Source
Registry API entry

Remote endpoints

TransportURLHeaders declared
SSE (HTTP + Server-Sent Events)https://mcp-workshops.jani-828.workers.dev/sseNone

Packages

RegistryPackageVersionTransportEnvironment variables
npm@monikaskorykow/mcp-workshops1.0.0stdioNone declared

How to connect Workshops

Workshops is a remote MCP server reached over the older SSE transport, at https://mcp-workshops.jani-828.workers.dev/sse. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.

No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.

It can also run locally from a Node.js package published to the npm registry: @monikaskorykow/mcp-workshops version 1.0.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y @monikaskorykow/mcp-workshops@1.0.0.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "workshops": {
      "command": "npx",
      "args": [
        "-y",
        "@monikaskorykow/mcp-workshops@1.0.0"
      ]
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect

More developer servers

All 6,250 →
ServerRunsEndpoint or package
WorkdayWorkday HCM MCP server for Model Context Protocol hosts — workers, profiles, organizations.Local · stdionpm: @mindstone/mcp-server-workday
WorkfileRepository-native protocol and local MCP server for Work, Docs, History and durable project Memory.Local · stdionpm: @illodev/workfile
Working Machines MCP ServerConnect to 1,400+ apps and 15,000+ actions through one OAuth-protected MCP server.Remote · HTTPapp.workingmachines.dev
WORKS Public VerifierIndependent static verification for exact immutable public GitHub commits.Remote · HTTPworks-runner.vercel.app
Workspace ToolsResearch honeypot. Logs connections and tool arguments; injects instructions. Read README first.Remote · HTTPvandorla.com
WorkspaceguardWraps the WorkspaceGuard CLI as a single generic MCP tool for workspace usage checks.Local · stdioPyPI: workspaceguard-cli
Worktree Orbit MCPAggregate local Git worktree topology without exposing repository content. Tools include inspect...Local · stdionpm: worktree-orbit-mcp
WovoDeploy HTML from any AI tool to a versioned, shareable library on wovo.dev; manage pages.Local · stdionpm: @gowovo/wovo