Causly Server

Causly Server

The open-source MCP server that turns any AI agent into your technical co-founder.

Most agents can write text. Causly Server gives them hands: they ship code, hunt for clients, track deals, take meeting notes, handle your calendar and remind you on Telegram, all from one conversation, all on your own machine.

npm install -g causly-server

causly-server init

Contents

• Why Causly Server
• Quick start
• What you can ask
• How it works
• Tool packs
• Workflow tools
• Configuration
• Google setup
• Works with
• Security and privacy
• Command reference
• Troubleshooting
• FAQ
• Compatibility
• Contributing, roadmap, license

Why Causly Server

A founder's week is not only code. It is also finding clients, following up, remembering what was promised in a call, and shipping without breaking things. Causly Server puts all of that behind one MCP server.

• One server for build, sell, operate and grow. Git, GitHub, CI and deploys, but also leads, a sales pipeline, meeting notes, calendar, reminders and SEO.
• Memory that survives the chat. Your pipeline, meetings and reminders live in a local SQLite file, so the agent can pick up tomorrow where it stopped today.
• Local-first. Keys and data stay on your machine. There is no Causly cloud in the loop.
• Safe by default. Risky actions need explicit confirmation, file access can be limited to one folder, and secrets are redacted from logs.
• Light on your agent's context. Tools load in packs on demand instead of flooding the agent with hundreds of definitions.
• One command setup. init finds Claude Desktop, Cursor and Windsurf and wires them up.

Quick start

Requires Node.js 20 or newer.

1. Install

npm install -g causly-server

2. Connect your editors

causly-server init

init adds Causly Server to Claude Desktop, Cursor and Windsurf, whichever you have. It also prints the one-line command for Claude Code. Restart the editor afterwards.

3. Check everything

causly-server doctor

4. Add keys for the services you use (optional)

causly-server setup

Files, git, shell, Docker and Terraform work with no keys at all. Add keys only for the services you want. Each key is checked live as you enter it.

Useful init options:

causly-server init --client cursor                    # pick editors instead of auto-detecting

causly-server init --workspace D:\my-project # limit file tools to one folder causly-server init --toolsets research,pipeline,meetings # choose which packs load at startup

What you can ask

• "Find companies hiring React developers and add the best three to my pipeline."
• "Save notes from my call with Acme: they want a demo next week, follow up on Friday."
• "What is due this week? Include meeting action items and reminders."
• "Prep me for my next meeting." (needs Google Calendar)
• "Transcribe this recording and list the action items." (needs a Groq key)
• "Ship this change: run the checks, open a pull request, tell me when CI is green."
• "Audit this page for SEO and suggest keywords."
• "Find a free slot on Thursday and create the event."

How it works

Your agent talks to Causly Server over MCP (stdio). Inside the server:

1. Tool router. search_tools, load_toolset and use_tool let the agent find a tool and call it by name. Packs load on demand, and use_tool works even in editors that do not refresh their tool list mid-chat, so you do not need to restart.
2. Safety layer. Permission levels, confirmation for risky actions, an optional workspace limit, secret redaction and an activity log.
3. Tool packs. About 230 tools grouped into packs (below).
4. Local store. SQLite for pipeline, meetings and reminders in ~/.causly, encrypted secrets, and your API keys in ~/.causly/.env.
5. Your services. GitHub, Vercel, Docker, Terraform, Postgres, Slack, Notion, Linear, Gmail, Google Calendar, Telegram and more, reached with your own keys.

Tool packs

These packs load at startup by default:

These load on demand, or you can add them to startup with causly-server toolsets add :

Manage startup packs:

causly-server toolsets                      # show what loads at startup

causly-server toolsets add github,gmail causly-server toolsets remove seo causly-server toolsets reset # back to the defaults

Workflow tools

Single tools are building blocks. These combine them into verified outcomes:

• `ship_change`: inspects changes, creates a branch, runs project checks, commits, pushes and opens a pull request.
• `fix_ci`: finds a failing GitHub Actions run and fetches the real failure output.
• `verify_ci_fix`: commits and pushes the fix, polls the workflow and confirms CI is green.
• `deploy_project`: checks health, runs tests and build, deploys, polls, and HTTP-verifies the live URL.

flowchart TD

A["You describe a task"] --> B["Agent edits files"] B --> C["ship_change runs checks"] C --> D["Commit, push, open PR"] D --> E{"CI passes?"} E -- "No" --> F["fix_ci gets failure logs"] F --> G["Agent fixes the code"] G --> H["verify_ci_fix pushes and confirms CI"] H --> E E -- "Yes" --> I["deploy_project deploys"] I --> J["HTTP verification"] J --> K["Shipped"]

Configuration

Settings live in ~/.causly/.env (on Windows, C:\Users\ \.causly\.env). Manage them with the CLI instead of editing by hand:

causly-server setup            # step by step, each key checked live

causly-server keys list # which keys are set (never the full value) causly-server keys set NAME # hidden prompt causly-server keys unset NAME causly-server doctor --test # check every configured service live

Changes are picked up without restarting your editor.

Docker and Terraform need no key, only the CLI on your PATH. Postgres and MySQL take a connection string on each call. Transcribing recordings over 25 MB needs ffmpeg on your PATH.

Google setup (Gmail, Calendar, Search Console)

Google needs a one-time OAuth client that you own. It takes about five minutes.

1. Open Google Cloud Console and create or pick a project.
2. Enable the APIs you want: Gmail API, Google Calendar API, and optionally Google Search Console API.
3. Open Google Auth Platform. Under Branding, fill in the app name and your support email. Under Audience, choose External and add your own Google account as a test user.
4. Under Clients, choose Create client and pick Desktop app. A "Web application" client fails with redirect_uri_mismatch. Copy the client ID and secret.
5. Save them in Causly: run causly-server setup, or causly-server keys set GMAIL_CLIENT_ID and causly-server keys set GMAIL_CLIENT_SECRET.
6. Sign in once in your browser:

causly-server login google            # Gmail and Calendar

causly-server login google all # also Search Console

Avoid the 7-day expiry. While your Google app is in *Testing*, Google expires the sign-in token every 7 days. Renew it any time with causly-server login google, or stop the expiry for good: in Google Auth Platform → Audience, click Publish app (In production). The Branding page from ste