Integration

Trust integration

Trust (usetrust.io) collects customer testimonials and shows them on websites through widgets. List your workspaces (registered websites), widgets and campaigns, create, read, update and delete testimonials and contacts, upload a testimonial video and attach a testimonial to a widget or remove it. The three image and small-video upload routes are not exposed (the vendor documents their answer only as a URL, with no response format), and webhooks are configured in the Trust account, not through this API. Authentication is HTTP Basic: any text as the username and the API key generated in your Trust account as the password.

Connect Trust How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Trust.Built from the 17 Trust tools below, on the connection you add once.

What you can do with Trust

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.

Contact, 6 operations

create_contactCreate contactPOSTCreate a contact in a workspace (workspaceId from list_workspaces) with name, email, phone and image URL. Returns the created contact with its id.
delete_contactDelete contactDELETEDelete a contact by its id. Irreversible.
find_contacts_by_emailFind contacts by emailGETLook up contacts by email address. The vendor calls the answer a list but documents it as one contact object (contactId, names, email, phone, imageUrl).
get_contactGet contactGETGet one contact by its id (from list_contacts or find_contacts_by_email).
list_contactsList contactsGETList all contacts of one workspace (pass a workspaceId from list_workspaces), with id, name, email, phone and image URL.
update_contactUpdate contactPUTUpdate a contact. The docs do not say whether fields left out are kept or cleared: read it with get_contact first and send back every field you want to keep.

Testimonial, 5 operations

create_testimonialCreate testimonialPOSTCreate a testimonial in a workspace (workspaceId from list_workspaces). For an uploaded video, pass videoToken and videoUrl from upload_testimonial_video together. Set published true only when it should show in widgets.
delete_testimonialDelete testimonialDELETEDelete a testimonial by its id. Irreversible.
get_testimonialGet testimonialGETGet one testimonial by its id (from list_testimonials), including its video URL and social media profiles.
list_testimonialsList testimonialsGETList all testimonials of one workspace (workspaceId from list_workspaces): text, giver, stars, consent, published flag and video.
update_testimonialUpdate testimonialPUTUpdate a testimonial. The docs do not say whether fields left out are kept or cleared: read it with get_testimonial first and send back every field you want to keep.

Testimonial widget, 2 operations

assign_testimonial_to_widgetAssign testimonial to widgetPUTAssign a testimonial (id from list_testimonials) to a widget (widgetId from list_widgets) so the widget can show it.
remove_testimonial_from_widgetRemove testimonial from widgetPUTRemove a testimonial (id from list_testimonials) from a widget (widgetId from list_widgets). The testimonial itself is kept.

Campaign, 1 operation

list_campaignsList campaignsGETList the campaigns of one workspace. Trust documents this answer only as a list of all campaigns, without its fields, so it is passed through unfiltered in result (one result per campaign when the answer is a list).

Testimonial video, 1 operation

upload_testimonial_videoUpload testimonial videoPOSTUpload a video file for a testimonial. Returns token and videoUrl: pass both to create_testimonial (videoToken, videoUrl). The file goes as multipart field file.

Widget, 1 operation

list_widgetsList widgetsGETList the testimonial widgets (onpage or popup) of all registered websites, with their widgetId for assign_testimonial_to_widget. Empty when the testimonial tool is not activated.

Workspace, 1 operation

list_workspacesList workspacesGETList the websites (workspaces) registered in your Trust account with their workspaceId, which the testimonial, contact, campaign and upload tools take. Call this first.

Use Trust from Claude Code, Cursor or Codex

Connect Trust in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Trust 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 Trust

Create your workspace
Sign up free. Nothing to install.
Connect Trust once
Add your Trust 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.