Connect Green Trees to your AI

Green Trees is a remote MCP server. There is no app to install and nothing to configure — you add it to Claude, ChatGPT or Cursor, sign in once, and start asking.

Before you start

You need a Green Trees workspace. If you don't have one, create one — it takes a minute — enter your email, type the six-digit code we send, done. The connect step below is the same for every seat.

https://mcp.greentrees.ai/mcp
OAuth 2.1 · dynamic client registration · streamable HTTP

Add the connector

$ claude mcp add --transport http greentrees https://mcp.greentrees.ai/mcp
Opening browser to sign in…  ✓ Connected as scott@acme.co

{ "mcpServers": { "greentrees": { "url": "https://mcp.greentrees.ai/mcp" } } }

Your first five minutes

Say “GT,” at the start of a request when you want to be sure your AI reaches for the CRM. It isn't required — the model will usually infer it — but it's a good habit while you're both learning.

› GT, what's changed since yesterday?
› GT, add Acme Industrial, Dana Cruz is the ops director, we met at the Atlanta trade show.
› GT, which accounts went quiet this month that we were about to close?
› GT, just got off the phone with Dana — she wants pricing before Friday. Log it.
› GT, show me my board.

What your AI can do

Tools are generated from one registry, so the manifest below is the product. Read tools are cheap and unlimited within your plan; write tools file a receipt to the audit log.

Approve, dismiss and cancel are deliberately not tools. A person does those, on a channel you chose.

Next

• Sequences — build, enroll, and stop by asking; sends as you, replies stop runs
• Activity & connections — how the record keeps itself without an app in the middle
• Approvals — the one-click channel that makes autonomy safe
• Migrate from HubSpot — the fifteen-minute conversation
• Board & rituals — see your workspace, and let the mornings run themselves

Built in a sentence, stopped by a reply

Tell your AI the cadence you want — steps, delays, the copy in your voice — and it builds the sequence with create_sequence. Enroll contacts by name or email (enroll_in_sequence, up to 200 at a time); anyone opted out, already in a live run, or on your own team is skipped and you're told why. Nothing about building or enrolling sends anything: every email step mints a draft that waits for your one-click approval when it comes due.

› GT, build a 3-step intro sequence for the Atlanta caterers list. Keep it short, no Fridays.
› GT, enroll everyone from yesterday's sourcing run.
› GT, how's the caterers sequence doing?
› GT, stop the sequence for Northway — Marcus replied on LinkedIn.

Sends as you. Connect your own mailbox once (connect_gmail or connect_outlook — your AI reads you the data-processing disclosure and hands you the provider's own consent link) and sequence email leaves from your address, threaded, inside your quiet hours and daily caps. A reply pauses the run in the same transaction that records it — there is no window where both are true. Replies to threads are answered from Gmail; Outlook covers fresh outbound today.

The record keeps itself

There's no app sitting between you and your email, calendar, or phone — so Green Trees earns the activity stream two ways, and marks each honestly.

Connected. That one mailbox connect is also the activity spine: email to and from known contacts lands on their records automatically (in and out), and with Google the same grant syncs your meetings. Provider-verified history, no logging ritual.

Reported. Everything else, you already say out loud to your AI — and it files it. “Just got off the phone with Dana” becomes a call on her record; “lunch with the Acme team, $214” becomes a note with the amount, on the company. Reported activity is first-class and labeled as yours — the record shows what was verified and what you told it, side by side.

A person clicks. Always.

Anything send-adjacent — an email draft, a sequence step, a text — creates a waiting card, never a send. Cards reach you wherever you are: say “email me my approvals” or hand your AI a Slack incoming-webhook URL, and each card arrives with the full draft and one-click Approve & send / Dismiss buttons. The links act as you, keep the usual undo window, expire in about three days, and leave a receipt — and they are deliberately not tools, so the AI can never click them itself.

Your board, and the mornings that run themselves

Ask your AI to show me my board and it renders a live snapshot of your workspace — pipeline by stage, contacts in sequence, and every card waiting on you with one-click Approve buttons. The board is a starting point on purpose: ask for any change (“make pipeline a chart”, “add my renewals”) and it’s yours. Say refresh my board any time.

If your AI supports scheduled tasks, the CRM can come to you. Copy either of these into a new scheduled task:

Check my Green Trees CRM (morning_brief tool) and send me a short brief: lead with anything waiting on me (include the one-click approve links), then what changed since yesterday, then pipeline health. A few tight lines, not a report.

Pull my Green Trees pipeline (board_data) and give me the Friday view: forecast by stage, what moved this week, what stalled, and the three deals I should touch Monday morning.

Approve links in a board or brief act as you and expire in about three days — treat them like an approval email.

A system of record your AI operates

There is no app. Your AI seat (Claude, ChatGPT, Claude Code, Cursor) connects over MCP and holds the whole tool manifest — reading the workspace, filing records, building sequences, rendering your board. Records file instantly, each with a receipt (what changed, who asked, when). Anything send-adjacent queues for a person: approval links arrive by email or Slack and can never be clicked by the AI. Autonomy — sequence steps firing on time, replies stopping runs, briefings on schedule — runs in Green Trees itself, so it works while no chat is open.

Talk to the workspace, not about it

Start requests with GT, and your AI knows the sentence is workspace work: “GT, log the call with Dana — she wants the proposal Friday.” Good sessions start with a brief (workspace_snapshot) and honor your standing instructions (get_preferences). When you state a durable rule — “never email a prospect on Fridays” — your AI saves it with update_preferences, and every seat honors it from then on.

The record, by asking

Companies, people, deals, notes and activities are created, updated, merged and reported on in sentences. Matching is deliberately loose — “Acme” finds Acme Industrial LLC — and records dedupe on file, never overwriting what you have. Need a field that doesn’t exist? Name it and it exists, ready to filter and report on. Bulk work goes through bulk_add_records: up to 100 records in one call, receipted. How the data model molds to you.

Living lists, sourced in your seat

A segment is a definition, not a snapshot: “prospects scored 70+ we haven’t touched in 30 days” stays true as the book changes, and suppression lists are honored everywhere sends happen. Sourcing and enrichment run through your AI’s own web and data tools — it researches, you approve the list, and the results file in bulk with sources noted.

Answers, not dashboards

Nothing is pre-built on a Monday. weekly_report computes the week live; whats_changed returns everything since a timestamp (the digest’s source); list_deals rolls the pipeline up by any cut you ask for. If you want it visual, ask for your board — the same numbers, rendered in the Green Trees system.

What your AI is told when it connects

On connect, the server hands your AI its operating doctrine: ground yourself before acting (preferences, then search before answering from memory), never claim something sent when it only queued, show outreach copy before queueing it, confirm bulk or irreversible actions, close working sessions with a receipt summary, and offer the morning ritual once — never nag. It also carries the board rendering contract and the standing-instructions habit. The instructions are versioned with the product, so every seat behaves the same way.

Generous for a person, starvation for a loop

Every connection has fixed hourly ceilings, tiered by plan: Starter 120 calls / 30 writes, Pro 300 / 100, Team 600 / 200, Enterprise 1,200 / 400. Bulk filing counts as one write, so real work fits easily — the ceilings exist to starve a runaway loop or a prompt-injected write flood, not to meter you. Reads are cheap and unlimited within plan.

Isolated by construction

Every query runs scoped to your workspace at the database index level — there is no cross-tenant code path. Connections are OAuth 2.1 with PKCE, revocable instantly; sign-in is an email one-time code, so there are no passwords. Every write is receipted, approvals are human-only, and reply-stop is transactional. The full posture lives on the Security page.

Where the workspace reaches you

When no chat is open, waiting approvals and briefings reach you on the channel you chose with configure_notifications: approval email from Green Trees, or a Slack channel — posts arrive as Green Trees 🌲 with one-click Approve and Dismiss buttons. Both carry the same signed, short-lived links. SMS and voice delivery are on the roadmap; when they land they’ll be one sentence to turn on, like everything else.