Working Machines MCP Server for Cursor

MCP serverSecurity

Connect to 1,400+ apps and 15,000+ actions through one OAuth-protected MCP server.

Available today. Use it from your connected AI after setup.

Connect ahel once, and every AI you use reads what you have installed.

Then ask your AI: use Working Machines MCP Server for Cursor

From the project's README

As published by klei30/working-machines in README.md.

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
└── .gitignore

Agent Workflow

Cursor agents follow the Working Machines discovery and execution sequence:

list_apps
      ↓
list_connections
      ↓
search_actions
      ↓
get_action_guide
      ↓
execute_action
      ↓
verify result
  1. list_apps: Discover available applications and tool integrations.
  2. list_connections: Verify active account authorizations and permissions.
  3. search_actions: Find machine actions by intent.
  4. get_action_guide: Retrieve validated schemas and input parameters.
  5. execute_action: Execute the action securely behind the boundary.
  6. Verify Result: Audit the structured execution response.

Validation

Verify repository manifest and component compliance:

node scripts/validate-template.mjs

Documentation & Links


License & Notice

  • Open-source plugin wrapper licensed under the MIT License.
  • See the NOTICE file regarding proprietary hosted infrastructure details.

Signals

Last commit
Sep 2026
Advanced
Delivery
working-machines MCP server β†’ your ahel gateway (mcp.ahel.ai) β†’ every connected AI client.
Catalog kind
mcp-server
Gateway key
io-github-klei30-working-machines
Source
github.com/klei30/working-machines
Hosted endpoint
https://app.workingmachines.dev/mcp