Integration

Content Snare integration

Content Snare collects files, text and approvals from clients through structured requests. Create and manage clients and client companies, create requests from templates or from scratch (with pages and sections), list and update requests, submit or approve their fields, review individual field answers, run a request's integration actions, and list templates, folders, communication schedules and team members. Webhook management and creating, updating or deleting team members (account administration) are not exposed. Authentication is a personal access token (starts with cs_pat_) sent as a Bearer token in the Authorization header; each route also needs the token's matching scope.

Connect Content Snare How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Content Snare.Built from the 30 Content Snare tools below, on the connection you add once.

What you can do with Content Snare

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Client, 5 operations

create_clientCreate clientPOSTCreates a new client Required scopes: write_clients
delete_clientDelete clientDELETEDeletes a client with specific ID Required scopes: write_clients
get_clientGet clientGETReturns a client with specific ID Required scopes: read_clients
list_clientsList clientsGETReturns list of active clients Required scopes: read_clients
update_clientUpdate clientPUTUpdates a client; send only the fields to change, leave the others out to keep them. Scope: write_clients.

Request, 5 operations

create_requestCreate requestPOSTCreates a request (draft unless status=published). Pass client_id or client_assignments for existing clients. If build_status is building in the answer, poll get_request until ready or failed. Scope: write_requests.
delete_requestDelete requestDELETEDeletes a request with specific ID Required scopes: write_requests
get_requestGet requestGETReturns a request with specific ID. For asynchronous request creation, poll about every 10 seconds while `build_status` is `building`; stop on `ready` or `failed`.
list_requestsList requestsGETReturns list of requests Required scopes: read_requests
update_requestUpdate requestPUTUpdates a request; send only the fields to change, leave the others out to keep them. Use client_assignments to assign one or more clients by id. Scope: write_requests.

Approve all submitted field, 3 operations

approve_page_all_submitted_fieldsApprove page all submitted fieldsPUTApproves all submitted for review fields in page (sets status "approved" for all fields) Required scopes: review_requests
approve_request_all_submitted_fieldsApprove request all submitted fieldsPUTApproves all submitted for review fields in request (sets status "approved" for all fields) Required scopes: review_requests
approve_section_all_submitted_fieldsApprove section all submitted fieldsPUTApproves all submitted for review fields in section (sets status "approved" for all fields) Required scopes: review_requests

Submit all field, 3 operations

submit_page_all_fieldsSubmit page all fieldsPUTSubmits all fields in page for review (sets status "done" for all fields) Required scopes: review_requests
submit_request_all_fieldsSubmit request all fieldsPUTSubmits all fields in request for review (sets status "done" for all fields) Required scopes: review_requests
submit_section_all_fieldsSubmit section all fieldsPUTSubmits all fields in section for review (sets status "done" for all fields) Required scopes: review_requests

Page, 2 operations

create_pageCreate pagePOSTCreates a new page in request Required scopes: write_requests
get_pageGet pageGETReturns a page with specific ID Required scopes: read_requests

Team member, 2 operations

get_team_memberGet team memberGETReturns a team member with specific ID Required scopes: read_team_members
list_team_membersList team membersGETReturns list of team members Required scopes: read_team_members

Client company, 1 operation

list_client_companiesList client companiesGETReturns list of client companies Required scopes: read_clients

Communication template, 1 operation

list_communication_templatesList communication templatesGETReturns list of communications schedules Required scopes: read_requests

Folder, 1 operation

list_foldersList foldersGETReturns list of folders Required scopes: read_requests

Me, 1 operation

get_current_identityGet current identityGETReturns the authenticated team member's name and safe details about the credential used for this request, including its type, scopes, and expiry. Required scopes: -

Page template, 1 operation

list_page_templatesList page templatesGETReturns list of page templates Required scopes: read_templates

Request template, 1 operation

list_request_templatesList request templatesGETReturns list of request templates Required scopes: read_templates

Review, 1 operation

review_fieldReview fieldPUTSets the review status of one field: approved (approve), redo (reject, add rejection_comment), todo (revise) or done (submit for review, remove reject or approval). Scope: review_requests.

Run integration action, 1 operation

run_request_integration_actionsRun request integration actionsPUTRuns integration actions inside a request with specific ID Required scopes: review_requests

Section, 1 operation

create_sectionCreate sectionPOSTCreates a new section in page Required scopes: write_requests

Section template, 1 operation

list_section_templatesList section templatesGETReturns list of section templates Required scopes: read_templates

Use Content Snare from Claude Code, Cursor or Codex

Connect Content Snare in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Content Snare operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Content Snare

Create your workspace
Sign up free. Nothing to install.
Connect Content Snare once
Add your Content Snare connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.