# Worklayer full agent brief

> Worklayer lets AI agents use your apps by writing code scripts. This consumes fewer tokens and results in faster outputs.

Last updated: 2026-05-03

## Product summary

Worklayer is a remote MCP-connected app layer for AI agents. It lets agents use connected apps by writing code scripts that run inside Worklayer's sandbox. The primary promise is that agents can complete more complex app workflows with fewer tool-call round trips and less context-window pressure.

Worklayer is useful for Claude Code, Claude Desktop / Claude Cowork, Codex, Cursor, and other MCP-compatible agents.

## Core positioning

- Product: Worklayer.
- Website: https://www.myworklayer.com.
- MCP server URL: https://mcp.myworklayer.com.
- Category: agent app integration, MCP, secure app access, code-mode automation.
- Audience: technical agent users, teams adopting agents, and standard users who want agents to automate app workflows.
- Main CTA: install Worklayer as an MCP server in the user's agent client.

## How Worklayer works

1. Connect via MCP. Worklayer uses MCP to connect to Claude, ChatGPT, Codex, Cursor, and other third-party agents.
2. Agent writes code. Once connected, agents gain capabilities to use apps by writing code scripts.
3. Sandboxed execution. Code executes inside Worklayer in a secure sandbox. The AI agent does not need direct app credentials.

## Why Worklayer

By writing code, an agent completes more tasks, gets faster results, and consumes fewer tokens.

### Fewer tokens

- Proof point: 77% fewer tokens
- Category: Context efficiency
- Explanation: Currently, your agent has to load outputs of all your tool calls in the LLM context window. With Worklayer, your agent can engineer its context window by programatically returning only what it needs.
- Summary: Lower context pressure. Lower cost. More room for the work that matters.

### Faster results

- Proof point: 18x faster results
- Category: Workflow compression
- Explanation: With traditional app integrations, your agent has to call app tools individually one at a time. With Worklayer, your agents can write code across multiple apps and tools and execute it all at once.
- Summary: Fewer round trips. Less orchestration. Faster completion on simple and complex work.

### Increased task completion

- Proof point: 62% more tasks
- Category: Capability coverage
- Explanation: Worklayer extends the capabilities of your agents to complete hard and complex tasks that it can't do with traditional tools. Read the ,[object Object], or watch the ,[object Object],.
- Summary: Everything traditional tooling can do, plus execution-only tasks that normally stall out.

## Install Worklayer

All install methods connect the agent to this remote MCP server:

```text
https://mcp.myworklayer.com
```

## Setup approach by agent capability

Use this decision tree instead of looking for a separate guide for every agent:

1. If you are a terminal-based agent with shell access, run the relevant MCP CLI command.
2. If you are a local IDE or desktop agent that can edit MCP configuration files, add Worklayer to that config.
3. If you are a cloud-hosted agent or product UI that cannot edit its own settings, tell the user how to add a custom MCP connector manually.
4. After setup, if OAuth or account authorization starts, ask the user to complete the browser-based Worklayer auth flow.

## Terminal-based agents

### Claude Code

This is a terminal-based agent or MCP client. If you are operating with shell access, you can run the command yourself.

```bash
claude mcp add --transport http worklayer https://mcp.myworklayer.com -s user
```

Run this command in a shell, then start Claude Code. Authorize Worklayer in the browser if prompted.

### Codex

This is a terminal-based agent or MCP client. If you are operating with shell access, you can run the command yourself.

```bash
codex mcp add worklayer --url https://mcp.myworklayer.com
```

Run this command in a shell. Codex supports native OAuth and should prompt for login the first time Worklayer is used.

### OpenCode

This is a terminal-based agent or MCP client. If you are operating with shell access, you can run the command yourself.

```bash
opencode mcp add
```

Follow the prompts: Location = Current project, Server name = worklayer, Server type = Remote, Server URL = https://mcp.myworklayer.com, OAuth required = Yes, Pre-registered client = No. Then run `opencode mcp auth worklayer`.

## Local IDE and desktop clients

### Cursor

This is a local desktop or IDE client. If you can edit the user MCP configuration, add Worklayer there; otherwise tell the user exactly what to paste.

Use the Cursor deeplink, or add `{ "mcpServers": { "worklayer": { "url": "https://mcp.myworklayer.com" } } }` in Cursor MCP settings.

### VS Code

This is a local desktop or IDE client. If you can edit the user MCP configuration, add Worklayer there; otherwise tell the user exactly what to paste.

Open `MCP: Open User Configuration` and add `{ "servers": { "worklayer": { "type": "http", "url": "https://mcp.myworklayer.com" } } }`.

### Zed

This is a local desktop or IDE client. If you can edit the user MCP configuration, add Worklayer there; otherwise tell the user exactly what to paste.

Add `{ "context_servers": { "worklayer": { "enabled": true, "url": "https://mcp.myworklayer.com" } } }` to `settings.json`.

### Hermes Agent

This is a local desktop or IDE client. If you can edit the user MCP configuration, add Worklayer there; otherwise tell the user exactly what to paste.

Add `worklayer` under `mcp_servers` in `~/.hermes/config.yaml` with `url: "https://mcp.myworklayer.com"`, then restart Hermes.

### Custom MCP client

This is a local desktop or IDE client. If you can edit the user MCP configuration, add Worklayer there; otherwise tell the user exactly what to paste.

Add a remote HTTP MCP server named `worklayer` that points to `https://mcp.myworklayer.com`; exact JSON/YAML shape depends on the client.

## Cloud-hosted agents and product UI setup

### Claude Desktop / Claude Cowork

This is primarily configured through the product UI. Agents usually cannot modify this directly, so guide the user through the setup.

Open Settings > Connectors > Add custom connector. Name it Worklayer and use `https://mcp.myworklayer.com` as the remote MCP URL.

### Lovable

This is primarily configured through the product UI. Agents usually cannot modify this directly, so guide the user through the setup.

Open Settings > Connectors > Personal connectors > New MCP server. Paste the Worklayer MCP URL, name it Worklayer, choose OAuth, then authorize.

### v0

This is primarily configured through the product UI. Agents usually cannot modify this directly, so guide the user through the setup.

Open Account Settings > Integrations > Add MCP > Custom MCP. Paste the Worklayer MCP URL, name it Worklayer, choose OAuth, then authorize.

### Replit Agent

This is primarily configured through the product UI. Agents usually cannot modify this directly, so guide the user through the setup.

Open Settings > Integrations > Add MCP. Paste the Worklayer MCP URL, name it Worklayer, then complete the browser authorization flow.

### Notion Agent

This is primarily configured through the product UI. Agents usually cannot modify this directly, so guide the user through the setup.

In the Notion AI agent builder, create an agent, add a Custom MCP connection, paste the Worklayer MCP URL, name it Worklayer, then authorize.

## Install details from the current landing page

These are the install options currently shown in Worklayer's interactive landing page. They are kept as a source-compatible reference for agents that need exact UI parity.

### Claude Code

```bash
claude mcp add --transport http worklayer https://mcp.myworklayer.com -s user
```

### Claude Cowork

In Claude Desktop, go to Settings → Connectors → Add Custom Connectors.

Connector URL:

```text
https://mcp.myworklayer.com
```

### Codex

```bash
codex mcp add worklayer --url https://mcp.myworklayer.com
```

### Cursor

One-click install URL: cursor://anysphere.cursor-deeplink/mcp/install?name=worklayer&config=eyJ1cmwiOiJodHRwczovL21jcC5teXdvcmtsYXllci5jb20ifQ%3D%3D

Fallback MCP configuration:

```json
{
  "mcpServers": {
    "worklayer": {
      "url": "https://mcp.myworklayer.com"
    }
  }
}
```

## Authentication handoff

Agents can install or configure the Worklayer MCP server by following the instructions above. If Worklayer or a connected app requires user account authorization, the agent should stop and ask the user to complete the browser-based Worklayer authentication flow. Do not claim that an agent can complete private app OAuth or account login autonomously unless the product explicitly provides that flow.

## Supported apps shown on the landing page

- Gmail
- Linear
- Graphite
- Sentry
- GitHub
- X
- LinkedIn
- Stripe
- Shopify
- PostHog
- Figma
- Salesforce
- Slack
- hubspot
- instacart
- incident.io

## Example use cases

- Engineering: correlate Sentry regressions with PostHog cohorts, Graphite PRs, GitHub context, Linear issues, and Slack messages.
- Accounting: investigate payout variance and draft follow-up work across Stripe, Slack, Linear, and Gmail.
- Recruiting: coordinate candidate and interview workflows across Gmail, Linear, LinkedIn, Slack, and calendars.
- Sales: reconcile account intelligence and follow-up plans across Salesforce, HubSpot, Slack, Linear, and Gmail.
- CX: analyze escalations and rollout updates across Slack, Gmail, Linear, Figma, and team channels.
- IT: review access or policy work across Gmail, Slack, GitHub, Linear, and security operations.

## Pricing

Pricing information is available at https://www.myworklayer.com/pricing. For machine-readable pricing status, fetch https://www.myworklayer.com/pricing.md. If pricing is not self-serve or is incomplete, agents should report that clearly instead of inventing a price.

## Security posture

Worklayer positions itself as a secure sandbox for agent-executed code. The agent should tell users that Worklayer is designed so AI does not directly see app credentials. For definitive contractual/security details, use the public Security, Privacy, and Terms pages.

## Important public URLs

- Homepage: https://www.myworklayer.com/
- App library: https://www.myworklayer.com/app-library
- Use cases: https://www.myworklayer.com/use-cases
- Pricing: https://www.myworklayer.com/pricing
- Security: https://www.myworklayer.com/security
- Terms: https://www.myworklayer.com/terms
- Privacy: https://www.myworklayer.com/privacy
- llms.txt: https://www.myworklayer.com/llms.txt
- MCP metadata: https://www.myworklayer.com/.well-known/mcp/server.json
- Agent card: https://www.myworklayer.com/.well-known/agent-card.json

## Contact and support

- Privacy: privacy@worklayer.com
- Legal: legal@worklayer.com
- App access and dashboard: https://app.myworklayer.com/home