Build and ship
136 toolsFrom a local edit to a verified deploy, without leaving the conversation.
- Files, git, shell, project42
- GitHub27
- Terraform20
- Docker18
- Vercel11
- Postgres and MySQL8
- Supabase6
- Workflows4
Causly Server gives your agent hands. Ship code, find clients, track deals, take meeting notes and run your calendar from one local MCP server, with guardrails on every risky action.
$ npm install -g causly-server$ causly-server initShip this change and open a pull request.
ship_change
Blocked: HIGH risk action, needs confirm: true
Go ahead.
ship_change { confirm: true }
✓ tests ✓ lint ✓ build
✓ branch pushed, pull request opened
Find companies hiring React developers and add the best three to my pipeline.
lead_hn_hiring → pipeline_add_lead ×3
✓ leads saved, follow-up reminder set
▍
01 / CAPABILITIES
Code is only part of a founder's week. Causly Server covers building, selling and operating, so your agent can carry work from one step to the next.
From a local edit to a verified deploy, without leaving the conversation.
Find clients, keep a pipeline, and fix your SEO from the same place you code.
Meetings, reminders and tickets that survive the end of a chat.
Read and send, with a confirmation step before anything leaves your machine.
Four tools chain several steps into one verified outcome. If a step fails, they stop and tell you exactly which one.
02 / HOW IT WORKS
Causly Server is a single Node.js process your editor starts over stdio. There is no network listener, no Causly cloud and no account.
One npm package. Needs Node.js 22.13 or newer and no API keys to start.
npm install -g causly-serverinit finds Claude Desktop, Cursor and Windsurf and wires them up for you.
causly-server initYour agent searches the tools, loads what it needs, and calls them by name.
“Prep me for my next meeting.”High-risk actions need an explicit confirm. Every call lands in an activity log.
confirm: trueYour agent
Claude Desktop, Cursor, Windsurf, your own
Causly Server
MCP over stdio
Tool router
search_tools, load_toolset, use_tool
Safety layer
Permissions, workspace limit, redaction
Tool packs
Loaded on demand, not all at once
Local store
SQLite, encrypted secrets, your keys
Your services
GitHub, Vercel, Google, Slack, Telegram, more
03 / SECURITY
Every tool has a risk level. The server enforces it, whichever agent or editor is calling.
READ
No side effects
runs immediately
LOW
Small, easy to undo
runs immediately
MEDIUM
Changes files or state
runs immediately
HIGH
Hard to undo or visible to others
needs confirm: true
DESTRUCTIVE
Deletes or cannot be reversed
needs confirm: true
Confine file and command tools to the folders you choose. Symbolic links are resolved first.
Catastrophic shell commands are blocked. Risky ones are flagged in the audit log.
Tokens and passwords are removed from inputs and errors before anything is logged.
A local store using AES-256-GCM, under a master key only you hold.
One structured line for every tool call, including the ones that were blocked.
No Causly cloud or account. Data only leaves for services you configured yourself.
Guardrails, not a sandbox. The approval gate is a flag the agent must pass, and the workspace limit checks path arguments. Use scoped keys and an agent you trust. The docs list exactly what is and is not protected.
Read the security model04 / WORKS WITH
Claude Desktop
Wired by init
Cursor
Wired by init
Windsurf
Wired by init
Claude Code
One command, printed by init
Your own agent
Tested with plain JavaScript and LangChain (JS)
05 / FAQ
Yes. It is open source under the MIT license. You pay only for the third-party services you choose to connect, such as GitHub or Groq, under their own terms.
Causly has no cloud and no account. Your keys live in ~/.causly/.env and your pipeline, meetings and reminders are in a local SQLite file. Data goes only to services you configured, and only when a tool for that service runs. The status and doctor commands check the npm registry for a newer version at most once a day, and you can turn that off.
Any client that can start a stdio MCP server. The init command sets up Claude Desktop, Cursor and Windsurf, and prints a one-line command for Claude Code. It has also been tested with a plain JavaScript MCP client and LangChain (JS).
No. Files, git, shell, Docker and Terraform work without any keys, and so do the pipeline, leads and research tools. Add keys later, one service at a time, with causly-server setup.
High-risk and destructive tools are refused unless the call includes confirm: true, and a well-behaved agent asks you first. That gate is a safety measure, not a separate approval screen, so scope your keys and use the workspace limit for a harder boundary.
Windows, macOS and Linux. The test suite runs on all three on every change, and Windows has had the most hands-on use. It needs Node.js 22.13 or newer.
Install it, connect your editor, and ask for the first thing on your list.
$ npm install -g causly-server