Booking made
Booking → lead
Create the contact and a deal in Lead, send the confirmation, add the visit prep checklist.
Local-first business app In development
Customers, deals, quotes, invoices, calendar, projects, stock and team, in one native app. Your AI agent works inside it through MCP. Automations do the routine work while you do the real work.
One app instead of
MCP server, built in
Philo speaks the Model Context Protocol. Connect Claude Desktop, Claude Code or any MCP client, and the agent can read your business, draft the work and, with your approval, act on it. Every call shows up live in the Agent panel.
Scripted demo. Tool names and scopes are the planned MCP interface.
On your desktop · claude_desktop_config.json
{
"mcpServers": {
"philo": {
"command": "philo",
"args": ["mcp", "--scope", "sales.read,finance.read,email.draft"]
}
}
}
From anywhere · remote MCP on your hub
claude mcp add --transport http philo \
https://hub.olive-oak.example/mcp
Sign-in with OAuth. You pick the scopes on the consent screen.
| sales.read | search get_contact get_contact_timeline list_deals get_pipeline |
|---|---|
| sales.write | create_contact update_deal move_deal add_note merge_contacts |
| finance.read | list_invoices get_cashflow list_expenses vat_summary |
| finance.write | draft_quote draft_invoice record_expense match_payment |
| work | create_task list_projects log_time get_calendar find_free_slot |
| email.draft | draft_emails list_email_templates summarize_thread |
| stock | list_products get_stock draft_purchase_order list_low_stock |
| automate | list_automations draft_automation test_automation get_runs |
| reports | run_report get_metric sql_readonly |
| always asks | send_emails send_quote issue_invoice refund delete_* enable_automation |
Automations
An automation is a short rule: when something happens, check a condition, do the work. Rules run on your hub, so they fire at 3 a.m. with every laptop closed. Build them by hand, or describe one in a sentence and let the agent draft it.
A record changes, a time arrives, or the outside world calls in: a booking, a form, an email, a Stripe payment, a webhook.
Filters on any field, tag, owner, amount or custom field. Combine with and, or, not.
Create, update, email, SMS, task, invoice, move a deal, call a webhook. Steps run in order and can branch.
For a time, a date field, or an event, such as “until paid”. Waiting runs survive restarts.
A step that hands the context to your agent: draft a reply, classify an email, pick a slot. Its output is a draft that waits for approval.
Booking made
Create the contact and a deal in Lead, send the confirmation, add the visit prep checklist.
Quote accepted
Move the deal to Won, issue the deposit invoice, start the project from a template, tell the team.
Invoice 7 days late
Reminder with a payment link. Still unpaid after 5 days: a personal draft and a call task.
Email received
The agent tags the email as lead, support or invoice, files it on the right contact and opens a ticket when needed.
Stock below minimum
Draft a purchase order to the usual supplier with the usual quantity. You approve and it goes out.
No reply in 3 days
A gentle follow-up on a sent quote. Stops by itself when the client opens or answers.
Every Monday 08:00
The agent writes the week: meetings, deals to push, money due in and out. It lands in your inbox.
Month end
Invoices, expenses, receipts, VAT summary and payroll prep in one export, sent to your accountant.
From a sentence
“When a quote has been open for a week and the client looked at it, remind me to call them.”
draft_automation → When quote.age = 7 days · Only if quote.viewed and not quote.accepted · Do create_task(owner, "Call about {quote}") · draft
The agent drafts. Test runs the rule on a real record without side effects. You switch it on.
A look around
All features
Each module is a switch per workspace. A bakery turns on booking, stock and the shop. A design studio turns on quotes, projects and timesheets. Same app.
How it works
A native Rust app for Linux, Windows and macOS. Each workspace is a SQLite file on your disk. Lists, search and reports run locally, so they are instant and they work on a plane.
A small Rust server. It syncs the team, runs automations on time, serves the client portal and booking page, and takes calls from Stripe, your bank and your mail. Use ours, or run it on your own box with one Docker image.
On the desktop, the app is an MCP server for local clients. On the hub, the same tools are available over HTTPS with OAuth, for agents on the web or on a phone.
FAQ
No. The app, the automations and every module work without an agent. The agent is an extra that you connect when you want it.
Any client that speaks MCP: Claude Desktop, Claude Code and others. The local server uses stdio. The hub serves streamable HTTP with OAuth.
Only if you allow it. By default, sending, issuing, refunding, deleting and switching on automations wait for a person to approve. Each approval is in the audit log.
No. Philo has no model of its own. Your MCP client reads what its scopes allow, and that client talks to the model you chose.
You keep working on your local copy. Changes sync when you are back. Automations and the portal keep running on the hub.
Yes. The hub is one Docker image with one data folder. Each workspace stays a SQLite file you can copy.
Yes. Import contacts, companies, deals and invoices from CSV, with a mapping step and a duplicate check.
Philo is in development. The current web version runs contacts, deals, tasks, Stripe and the client portal. The desktop app and the modules on this page come next. Early access members get each part first.
Early access
We open Philo to small teams in waves. Tell us what your business does and which tools you want to drop.
support@cgeosoft.com