Working Machines MCP Server

Registre officiel Autres

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

Que pouvez-vous faire avec Working Machines MCP Server ?

  • 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.

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

Remote (streamable-http)
Claude Code
claude mcp add --transport http working-machines-mcp-server 'https://app.workingmachines.dev/mcp' --header 'Authorization: <Your Working Machines OAuth bearer token. Format: '\''Bearer <token>'\''>'
Configuration JSON (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "working-machines-mcp-server": {
            "type": "http",
            "url": "https://app.workingmachines.dev/mcp",
            "headers": {
                "Authorization": "<Your Working Machines OAuth bearer token. Format: 'Bearer <token>'>"
            }
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. Working Machines MCP Server for Cursor
  2. Remote Access to 1,400+ Apps & 15,000+ Tools
  3. Safety & Security Architecture
  4. Repository Structure
  5. Agent Workflow
  6. Validation
  7. Documentation & Links
  8. License & Notice

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


License & Notice

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

Questions fréquentes

Qu'est-ce que Working Machines MCP Server ?

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

Comment installer Working Machines MCP Server ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http working-machines-mcp-server 'https://app.workingmachines.dev/mcp' --header 'Authorization: <Your Working Machines OAuth bearer token. Format: '\''Bearer <token>'\''>'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour Working Machines MCP Server ?

Oui. Il attend Authorization, à renseigner dans sa configuration.

Working Machines MCP Server est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient Working Machines MCP Server ?

Il est publié par klei30. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.