Other · Remote MCP server
Working Machines MCP Server
Connect to 1,400+ apps and 15,000+ actions through one OAuth-protected MCP server.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.klei30/working-machines- Version
- 1.0.4
- Status
- Active
- Category
- other
- Transport
- Streamable HTTP
- Published
- 2026-09-05
- Updated
- 2026-09-05
- Publisher
- klei30 (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/klei30) · how
- Website
- www.workingmachines.dev
- Repository
- github.com/klei30/working-machines
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://app.workingmachines.dev/mcp | Authorization (required, secret) |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect Working Machines MCP Server
Working Machines MCP Server is a remote MCP server: there is nothing to install. Its endpoint is https://app.workingmachines.dev/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
The registry entry declares an HTTP header for the connection: Authorization (required, secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. 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 other servers
| Server | Runs |
|---|---|
| Work IQ User MCP ServerTools for retrieving user details, manager, team or direct reportees from Microsoft Graph. | Remote · HTTP |
| WorkbenchHosted DNA/RNA/protein tools: primers, oligos, PCR, cloning, CRISPR, alignment, batch & pipelines. | Remote · HTTPLive check: ✗ no handshake |
| WorkdayWorkday HCM MCP server for Model Context Protocol hosts - workers, profiles, organizations. | Local · stdio |
| WorkflowCreate, browse, remix, collaborate on, and run durable AI workflow nodes from MCP hosts. | Remote · HTTPLive check: ✗ no handshake |
| WorkixRemote jobs, freelance gigs, vacancies. 24 boards: Upwork, Freelancer, RemoteOK, hh.ru, Kwork. | Local · stdio |
| WorkizManage Workiz jobs and leads: create, update, assign team members and convert leads to jobs. | Remote · HTTPLive check: ✓ handshake |
| WorkledgeA growing notebook shared by every AI you use. Save in conversation, recall from any connected AI. | Remote · HTTPLive check: sign-in required |
| WorkloadtruthClassifies GPU workloads as inference or training from telemetry alone via MCP tools. | Local · stdio |