EEasyRunCraft

Help

Working in your browser.

Open and save files

Use each editor’s File menu or supported drag-and-drop. Save and export before closing or switching away. Autosave and recovery support differ between tools; a shared account does not back up your files.

Switch tools

Open the tool menu beside the EasyRunCraft mark. Tool links open a new tab so the current workbench stays available. Export a compatible file to move content between tools.

AI access

Use your own provider key for supported models, or sign in to use shared EasyRunCraft credits. Own-key requests go directly from your browser to the provider. Credit requests use our account service. AI can make mistakes; review edits and use native undo where supported.

Desktop MCP

Some original desktop editions support MCP or other automation channels. The browser uses its in-page Agent bridge, not a local MCP listener. See each upstream project’s documentation for desktop setup.

Browse all guides →

EasyRunCraft MCP

  1. Create a token

    Create MCP token in Account

  2. Configure your client

    Set EASYRUNCRAFT_MCP_TOKEN in the environment your client launches from.

    Run this command once, then launch Codex with the token in its environment.

    codex mcp add easyruncraft --url https://easyruncraft.com/mcp --bearer-token-env-var EASYRUNCRAFT_MCP_TOKEN

    Add the server to your project’s .mcp.json, merging it into mcpServers if the file already exists.

    Claude Code configuration reference

    {
  "mcpServers": {
    "easyruncraft": {
      "type": "http",
      "url": "https://easyruncraft.com/mcp",
      "headers": {
        "Authorization": "Bearer ${EASYRUNCRAFT_MCP_TOKEN}"
      }
    }
  }
}

    Choose Streamable HTTP and configure the endpoint and Authorization header in your client. Resolve the token variable using your client’s secret settings.

    Endpoint  https://easyruncraft.com/mcp
Authorization: Bearer ${EASYRUNCRAFT_MCP_TOKEN}

  3. Try the connection

    Paste this request into your assistant. It works without uploading a file.

    Use EasyRunCraft MCP to check which file types and operations it supports.

Connected products

Connect once to use these products from your assistant.

How your assistant chooses a product

Name the file and say what you want to do. For example, “Use EasyRunCraft to rotate page 2 of report.pdf” points to PdfCraft. “Sort the Orders sheet in orders.xlsx” points to GridCraft. For images, Word documents and presentations, name the file and the output format, such as “Render slide 3 of kickoff.pptx as a PNG.” If several files match, say which one you want edited.

Missing an operation? Open the relevant product documentation above for its supported operations and feedback link.

Frequently asked questions

How do I manage my MCP token?

Sign in and choose Create MCP token in Account. Copy the token when it appears and keep it out of prompts and shared files. Tokens expire after 30 days and can be revoked from the same panel.

Which clients can connect?

Use a Streamable HTTP client that can send a dedicated Bearer token. To run file tasks, the assistant also needs access to the files and tools that can upload with HTTP PUT and download with HTTP GET.

What does it cost?

MCP file operations use zero EasyRunCraft AI credits. Your assistant’s provider may bill for its own usage. Built-in browser Agent and model features follow the EasyRunCraft pricing or your configured provider’s rates.

What are the file and task limits?

Each product guide lists its supported input formats and operation limits. Each input can be up to 20 MiB. Each account can have two active jobs. Each native command has a 45-second limit.

Where do my files and results go?

The service works on private copies and keeps files and jobs for up to 24 hours. Upload and download URLs expire after 10 minutes. Anyone with a valid link can perform its assigned action until it expires, including after a token is revoked. See the privacy policy.