We’re building Ever Works in public. Some things may be incomplete, missing, or broken while we continue improving the platform.We’re building Ever Works in public — expect a few rough edges.
Feature · Developers
The dashboard is one client among several. Everything it does is an authenticated REST call, so the same Works, Missions, Tasks and Knowledge Base are reachable from an MCP-compatible assistant, a terminal, a CI job or a Slack channel — and the platform reports back through signed webhooks. You bring Ever Works into the tools you already use, rather than moving your work into it.
Every surface below is a thin client over the same API, with the same credentials and the same access controls.
Point Claude Desktop, Claude Code or any MCP-compatible client at the Ever Works MCP server and it can list, create, generate, deploy and schedule Works, drive Missions, Ideas and Tasks, and read and lock Knowledge Base documents. Its tools are generated from the API’s own OpenAPI spec through a curated whitelist, so they stay in sync. Run it over stdio, as a container, or use the hosted endpoint.
Every route the dashboard uses is described by one OpenAPI document. Create an ew_live_ key under Settings → API Keys — shown once, stored only as a hash — and call the API from scripts and CI.
Register HTTPS endpoints to receive signed events when a Work is created, a generation completes, or a deployment starts, finishes or fails. In the other direction, an inbound trigger gives you a signed URL that turns each verified call into a Task for the Agent you nominate.
npm install -g ever-works-cli gives you four command groups — auth, work, plugins and kb — to create, generate and deploy Works, manage plugins, and upload or lock Knowledge Base documents from a terminal.
Any client that lets you set a custom base URL can talk to Ever Works through POST /api/v1/chat/completions. Send an x-work-id header and the reply answers in that Work’s context, citing its Knowledge Base.
Mention @works in Slack to drive the platform from a channel, bring in Linear issues, Notion documents and meeting transcripts as context, and swap any provider — models, search, Git, deploy, email — through the plugin catalog without touching a Work.
The MCP route is the shortest path from an agent you already use to Works it can manage.
Settings → API Keys → Create API Key. Copy it when it is shown — it is never shown again — and keep one key per client so revoking one never breaks the rest.
Start the stdio entrypoint with your key and API URL for a local client, or run the published container image, which serves the streamable-HTTP transport.
Add an mcpServers entry to your client’s configuration — claude_desktop_config.json, a project .mcp.json, or the equivalent file elsewhere.
Call ping to confirm the connection, then just ask: list my Works, generate ten more items, deploy it, set a weekly refresh.
Because every surface is the same API underneath, what one of them cannot do yet, another usually can. These are the edges worth knowing before you build on them.