Livespace MCP integration for AI agents.
Connect AI agents to Livespace through 26 structured actions, including get company, create company, and delete company. Review authentication, inputs, workf…
- ACTION CONTRACTS
- 26
- AUTHENTICATION
- API key
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Livespace integration exposes
The Livespace Agent App exposes 26 provider-backed actions for productivity and marketing work. Its current contract lets an authorized agent get a livespace company by id, create a livespace company, and delete a livespace company. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses API key. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Livespace account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Livespace capabilities.
Showing 12 of 26 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
get_companyREADGet a Livespace company by ID.
INPUTS: id
create_companyWRITECreate a Livespace company.
INPUTS: company
delete_companyHIGH IMPACTDelete a Livespace company.
INPUTS: id
create_dealWRITECreate a Livespace deal.
INPUTS: deal
create_personWRITECreate a Livespace person.
INPUTS: contact
create_taskWRITECreate a Livespace todo.
INPUTS: todo
delete_dealHIGH IMPACTDelete a Livespace deal.
INPUTS: id
delete_personHIGH IMPACTDelete a Livespace person.
INPUTS: id
delete_taskHIGH IMPACTDelete a Livespace todo.
INPUTS: id
get_current_userREADGet information about the current Livespace API user.
get_dealREADGet a Livespace deal by ID.
INPUTS: id
get_personREADGet a Livespace person by ID.
INPUTS: id
INPUT CONTRACTS
Know what the action needs before it runs.
get_company
idREQUIRED- Livespace object ID.
create_company
companyREQUIRED- Raw Livespace company payload accepted by Contact/addCompany or Contact/editCompany.
delete_company
idREQUIRED- Livespace object ID.
create_deal
dealREQUIRED- Raw Livespace deal payload accepted by Deal/addDeal or Deal/editDeal.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Get Company
Get a Livespace company by ID. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
get_companyControl Create Company
Create a Livespace company. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
create_companyVerify with Create Company
Create a Livespace company. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
create_companySAFETY BOUNDARY
Operate Livespace with explicit limits
- Authorize Livespace with API key and grant only the provider access required by the selected actions.
- 12 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `delete_company`, `delete_deal`, and `delete_person` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Livespace rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Livespace task completed successfully.
CONNECTION MODEL
API key
Livespace API key sent with every API request. Find it in Account settings > API: https://support.livespace.io/en/articles/3572069-api-documentation-and-information.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 14
- WRITE SIGNALS
- 8
- HIGH IMPACT
- 4
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Livespace.