MCP server for Claude

One conversation. Your whole stack.

Causly Server gives Claude 181 tools to build, deploy, containerize, and manage a real product end to end — code, databases, infrastructure, monitoring, all of it — running locally on your own machine.

View on GitHub Read the docs

logs/activity.log

$ship_changeMEDIUMok 842ms

$run_testsREADok 1204ms

$docker_buildHIGHconfirm:trueok

$terraform_applyDESTRUCTIVEconfirm:true

$deploy_projectHIGHconfirm:trueok

$http_checkREAD200 healthy

$sentry_list_issuesREAD0 open

// the product lifecycle

Every stage of shipping something real, in one place

Not a pile of generic integrations — a set of tools that follows the shape of an actual project, from an empty repo to something live and monitored.

Code

Read, write, edit, move, and search files and directories.

Version control

Full git lifecycle plus the complete GitHub PR and Actions/CI flow.

Databases

Generic Postgres and MySQL, plus Supabase.

Containers

Docker — build, run, inspect, compose. Docker Desktop or WSL-only.

Infrastructure

Terraform — plan, apply, destroy, state, plus a CI plan-comment hook.

Secrets

A built-in local encrypted vault — no external service required.

Monitoring

Sentry — list, search, and triage errors from the same chat.

Docs & knowledge

Notion — pages, databases, blocks, comments.

Communication

Slack and Gmail — read, search, send, reply.

Deployment

Vercel — deploy, verify, roll back, check health.

// safety model

It can genuinely change your systems — so every call is classified first

Risky actions don't run silently. Every tool carries a permission level, and the ones that matter wait for your explicit confirmation.

READLOWMEDIUMHIGH — needs confirm:trueDESTRUCTIVE — needs confirm:true

→

Secret redaction

Tokens, passwords, and keys are stripped before anything touches a log line.

→

Command risk scanning

Force-push, DROP TABLE, curl-pipe-bash, sudo — flagged and surfaced, not silently allowed.

→

Path protection

Writes and deletes inside protected system directories are blocked outright.

→

Structured audit log

Every call appended to logs/activity.log — one JSON line: risk, status, duration.

// vs. zapier / composio-style platforms

The workflow is already built — and it never leaves your machine

	Causly Server	Zapier / Composio-style
Setup	Fill in a token — the workflow already exists	You wire up the automation yourself, every time
Your data	Local-first, never leaves your machine	Cloud-hosted, passes through their servers
Depth	Product-lifecycle-aware, expert-tuned tools	Generic, one-action-at-a-time integrations
Limits	None — free and open-source (MIT)	Usage tiers, task limits, seat pricing

// get started

Running in under five minutes

Node.js 18+ and Claude Desktop (or any MCP client). Everything else is optional, only needed for the tools you use.

$ git clone https://github.com/KNIHAL/causly-server

$ cd causly-server && npm install

$ cp .env.example .env

$ npm run setup