Working Machines MCP Server
online · 100% uptimeio.github.klei30/working-machines·v1.0.4Connect to 1,400+ apps and 15,000+ actions through one OAuth-protected MCP server.
0 stars
Reviews
Write oneNobody has reviewed Working Machines MCP Server yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Working Machines MCP Server tools
Tool list not cached yet. `describe` through the gateway fetches it live.
Public scan report
scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it
- –Code scanremote-only server, no package to scann/a
- Live reliabilityremote reachable in 276ms (auth required)20/20
- –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
- Auth qualityOAuth resource metadata advertised on 40115/15
- Maintenancelast push 41 days ago12/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How Working Machines MCP Server compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 92/100
- higher than 93% of 48,243 servers
- Uptime
- 100%
- of our recent checks; the typical remote server answers 100%
- Response time
- 213 ms
- faster than 65% of 30,027 servers
Install Working Machines MCP Server in Claude Code, Cursor or VS Code
claude mcp add --transport http working-machines https://app.workingmachines.dev/mcp
What the publisher says
From the Working Machines MCP Server repository's README, as published. We do not edit it. Read it on GitHub
Working Machines MCP Server for Cursor
Official Cursor plugin repository for Working Machines.
Connect Cursor to 1,400+ apps and 15,000+ machine-ready tools remotely through one secure, hosted Model Context Protocol (MCP) server.
Remote Access to 1,400+ Apps & 15,000+ Tools
Working Machines provides the application layer for AI agents. Through a single remote MCP connection (https://app.workingmachines.dev/mcp), your agent gets instant access to 1,400+ integrations and 15,000+ structured actions across:
- Team Collaboration: Slack, Gmail, Google Workspace, Microsoft Teams, Notion
- Development & Cloud: GitHub, GitLab, Sentry, Jira, AWS, Vercel, Datadog
- Projects & Productivity: Linear, Asana, Trello, ClickUp, Monday.com
- Commerce & CRM: Salesforce, HubSpot, Stripe, Shopify, Zendesk
- Data & Analytics: Snowflake, BigQuery, PostgreSQL, Airtable, Pinecone
Safety & Security Architecture
Working Machines is engineered from the ground up for safe, enterprise-grade AI execution:
🛡️ 1. Your Credentials Are Not Context
- Zero Local Secret Storage: API keys, OAuth tokens, and secret credentials stay behind the Working Machines execution boundary.
- Context Protection: Credentials never enter your Cursor chat context, prompt buffers, or local workspace files.
🔒 2. Scoped Capabilities & Policy Enforcement
- Intent-Based Access: Agents discover only the minimal actions required for the task at hand rather than loading full provider schemas.
- Provider-Native Scopes: Connect accounts once with provider-bound permissions (e.g. create issues only).
- Execution Policies: Allow, reject, or require approval for actions before any call leaves the execution boundary.
📋 3. Verifiable & Auditable Run History
- Structured Proof: Every action execution produces a structured, redacted, and auditable record.
- Execution Visibility: Tracks who acted, which connection was used, what changed, timing, and policy decisions for complete transparency.
Repository Structure
This repository follows the official Cursor plugin marketplace format:
working-machines/
├── .cursor-plugin/
│ └── marketplace.json
├── plugins/
│ └── working-machines/
│ ├── .cursor-plugin/
│ │ └── plugin.json
│ ├── assets/
│ │ └── logo.png
│ ├── skills/
│ │ └── working-machines/
│ │ └── SKILL.md
│ ├── mcp.json
│ └── README.md
├── scripts/
│ └── validate-template.mjs
├── README.md
├── CHANGELOG.md
├── LICENSE
├── NOTICE
└── .gitignoreAgent Workflow
Cursor agents follow the Working Machines discovery and execution sequence:
list_apps
↓
list_connections
↓
search_actions
↓
get_action_guide
↓
execute_action
↓
verify result- listapps**: Discover available applications and tool integrations.
- listconnections**: Verify active account authorizations and permissions.
- searchactions**: Find machine actions by intent.
- getactionguide: Retrieve validated schemas and input parameters.
- executeaction**: Execute the action securely behind the boundary.
- Verify Result: Audit the structured execution response.
Validation
Verify repository manifest and component compliance:
node scripts/validate-template.mjsDocumentation & Links
- Website: https://www.workingmachines.dev
- Cursor Integration Guide: https://www.workingmachines.dev/agents/cursor
- Documentation: https://www.workingmachines.dev/docs
- App Dashboard: https://app.workingmachines.dev
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Working Machines MCP Server: common questions
- Is Working Machines MCP Server safe?
- Yes, by our scan: it is graded A (92/100). Read the Working Machines MCP Server safety report
- How do I install Working Machines MCP Server?
- It runs remotely at app.workingmachines.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
- Does Working Machines MCP Server need an API key?
- No key to paste: it signs you in with OAuth when your client connects.
- Is Working Machines MCP Server maintained?
- The last commit was 61 days ago (2026-09-05). The latest release is v1.0.4.
- Is Working Machines MCP Server up?
- 100% of our last 28 checks got an answer. We check remote servers about four times a day.
- How does Working Machines MCP Server compare with other MCP servers?
- safety score 92/100 (higher than 93% of 48,243 servers); uptime 100% (of our recent checks; the typical remote server answers 100%); response time 213 ms (faster than 65% of 30,027 servers). Full comparison.