Livespace CRM MCP Server

Install

Pick your client. Read the repository before you give any tool access to your data.

About

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.

Tools

6 read · 3 write · 2 delete

Secrets

None asked for

Install scripts

Not scanned yet

Runs as

Node.js package

Tools (11)

Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].

• analyzeAnalyze CRMread-only

  Run one named aggregation per call. "pipeline_summary" counts open deals per process and stage and takes an optional processId scope; "stage_conversion" needs processId and estimates stage-to-stage conversion inside it; "activity_summary" needs dateFrom and dateTo (YYYY-MM-DD) and counts feed entries by type and by author, and tasks by type and completion; "forecast_vs_realization" needs the same period, weighs open deals due in it against the deals won and lost in it, and takes an optional processId scope. Take process ids from crm_metadata; never guess them. Notes: Livespace has no aggregati…

• create_recordsCreate CRM Records

  Create persons, companies, deals or tasks - at most 10 items per call across all four arrays. dryRun: true previews without writing or asking for approval. On clients with form elicitation, a non-dry-run call requests human approval; confirm: true cannot bypass it. Other clients can preview, but execution with confirm: true is refused by default. Only an operator-enabled unsafe compatibility mode permits execution without signed human approval; see server instructions. Notes: a person carrying e-mails is checked against the CRM by exact address (case-insensitive) and against the earlier items …

• crm_metadataCRM Metadataread-only

  Read CRM dictionaries: processes (with stages and their checkbox steps), users and teams, contact/deal groups, sources, task types and statuses, products, and the current user. ALWAYS take ids from here instead of guessing. Notes: deal stage changes happen by completing steps, not by setting a stage directly; stages, steps and statuses are listed in their CRM order; sources have no ids (names only); currentUser.id is null when it cannot be resolved - then match currentUser.email in the users section. Custom-field datasets are not available yet. Results are cached server-side for a few minutes …

• get_activityGet CRM Activityread-only

  Read history from one source per call. "record" returns the wall of a single person, company or deal and needs record: {kind, id}; "crm" returns the CRM-wide feed and needs dateFrom and dateTo (YYYY-MM-DD); "tasks" returns tasks and takes completed plus an optional date range. Take ids from search_crm or crm_metadata; never guess them. Notes: typeName narrows the CRM feed page you get back by exact entry type - it thins the page after fetching, it does not search; wall and feed text arrives flattened to plain text and cut at 500 characters (textTruncated says so); count is what the source held…

• get_recordsGet CRM Recordsread-only

  Read persons, companies, deals or tasks by id - one kind per call, up to 25 ids at a time. Take the ids from search_crm or crm_metadata; never guess them. Every id answers for itself: status "ok" carries the record under the key of its kind, "not_found" means the record does not exist OR the API key's user cannot see it (Livespace does not distinguish the two), and "error" carries a {code, message, hint}. Duplicate ids are collapsed before fetching. detail omits fields outside the selected level. An empty or null returned field means this response supplies no value; it does not establish an em…

• healthServer Healthread-only

  Check that this MCP server is up. Pass checkLivespace: true to also verify the Livespace API connection (one lightweight call).

• log_activitiesLog CRM Activities

  Log notes on a person, company or deal and phone calls on a person - at most 15 items per call across both arrays. dryRun: true previews without writing or asking for approval. On clients with form elicitation, a non-dry-run call requests human approval; confirm: true cannot bypass it. Other clients can preview, but execution with confirm: true is refused by default. Only an operator-enabled unsafe compatibility mode permits execution without signed human approval; see server instructions. Notes are PUBLIC - Livespace ignores every visibility parameter, so anyone who can see the record can rea…

• move_deals_to_stageMove Deals To Stagecan change or delete data

  Move deals to a pipeline stage - at most 10 deals per call, all to the same stage. Livespace has no "set stage" call: a deal stands where its furthest checked process step stands, so this tool checks and unchecks steps, which means a forward move marks intermediate steps as completed and a backward move un-marks them - the checkboxes stop being evidence of work done. dryRun: true previews without writing or asking for approval. On clients with form elicitation, a non-dry-run call requests human approval; confirm: true cannot bypass it. Other clients can preview, but execution with confirm: tru…

• notify_userNotify a CRM User

  Send ONE in-app Livespace notification to one CRM user - a short message and a link, shown in that user's notification bell. dryRun: true previews without writing or asking for approval. On clients with form elicitation, a non-dry-run call requests human approval; confirm: true cannot bypass it. Other clients can preview, but execution with confirm: true is refused by default. Only an operator-enabled unsafe compatibility mode permits execution without signed human approval; see server instructions. The human may edit the notification message in the approval form. Livespace exposes no read-bac…

• search_crmSearch CRMread-only

  Find persons, companies and deals. Two modes, exactly one per call: "phrase" runs the CRM's own word-prefix search and returns light hits (id, name, description, url) - use it when you have a name or a fragment of one; "filters" lists records and returns full ones - use it for "all open deals in process X". An empty filters object lists everything of that kind. Feed the returned ids into get_records or get_activity; never guess ids. Notes: sorting is done by this server over one window of at most 200 rows, so sortBy cannot be combined with cursor and sortWindowTruncated tells you the window wa…

• update_recordsUpdate CRM Recordscan change or delete data

  Update persons, companies, deals or tasks by id - at most 10 items per call across all four arrays. Edits merge upstream, so a field you do not send is left alone, and an item that names no field at all is refused. dryRun: true previews without writing or asking for approval. On clients with form elicitation, a non-dry-run call requests human approval; confirm: true cannot bypass it. Other clients can preview, but execution with confirm: true is refused by default. Only an operator-enabled unsafe compatibility mode permits execution without signed human approval; see server instructions. Every…

Signals

Stars

0

Forks

0

Open issues

0

Last commit

Oct 5, 2026 (25 days ago)

Last release

Oct 5, 2026 (25 days ago)

From GitHub (fetched Oct 24, 2026).

Details

Registry name

io.github.proAutomator/livespace-crm-mcp

Version

0.1.2

Auth

API key

Packages

npm livespace-crm-mcp

License

MIT

Repository

github.com/proAutomator/livespace-crm-mcp

Website

github.com/proAutomator/livespace-crm-mcp#readme

First seen

Oct 24, 2026

Last checked

Oct 24, 2026

Source

Official MCP Registrygithub-graphql