Integration

Papertrail integration

Papertrail (SolarWinds) is hosted log management. Search the account's log events with Papertrail search syntax by system, group and time window; list, register, update and remove systems (log senders) and move them in and out of groups; create, update and delete groups and saved searches; read log destinations, the account's log data usage, the list of archive files and the account's members. Log lines carry whatever the senders write, which can include personal data and secrets. Not exposed: inviting, updating and removing members, downloading archive files, and creating log destinations (the API does not offer it). Authentication is an API token from the Papertrail user profile, sent in the X-Papertrail-Token header.

Connect Papertrail How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Papertrail

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.

Search, 6 operations

create_saved_searchCreate saved searchPOSTSaves a search query under a name, on a group (All Systems or the first group when group_id is left out). Returns the saved search.
delete_saved_searchDelete saved searchDELETEDeletes a saved search, given its id from list_saved_searches. Answers a message such as Search deleted.
get_saved_searchGet saved searchGETReturns one saved search with its query and the group it runs on.
list_saved_searchesList saved searchesGETLists every saved search of the account with its query and the group it runs on.
search_eventsSearch eventsGETSearches log events with Papertrail search syntax, optionally in one system or group and an id or time window. Up to limit events (1000 by default). Log lines can hold personal data or secrets.
update_saved_searchUpdate saved searchPUTChanges a saved search's name, query and group. Send both name and query (the reference marks them required). Returns the saved search.

Group, 5 operations

create_groupCreate groupPOSTCreates a group of systems, holding the systems whose names match system_wildcard and those listed in system_ids. Returns the group with its systems.
delete_groupDelete groupDELETEDeletes a group, given its id from list_groups. Answers a message such as Group deleted.
get_groupGet groupGETReturns one group with the systems it contains (static members and wildcard matches).
list_groupsList groupsGETLists every group of the account with the systems it contains (static members and wildcard matches).
update_groupUpdate groupPUTChanges a group's name or system wildcard; fields left out keep their value. Members are added and removed with add_system_to_group and remove_system_from_group.

System, 5 operations

get_systemGet systemGETReturns one system (log sender) with its name, IP address, hostname, last event time and the syslog host and port it logs to.
list_systemsList systemsGETLists every system (log sender) of the account with its id, name, IP address, hostname, last event time and the syslog host and port it logs to. Use it to find systems that stopped sending.
register_systemRegister systemPOSTRegisters a log sender: with destination_id or destination_port plus hostname for a log destination, or with ip_address for the standard syslog port logs.papertrailapp.com:514. Returns the system.
remove_systemRemove systemDELETEDeletes a system (log sender) from the account.
update_systemUpdate systemPUTChanges a system's name, IP address, hostname, description or auto-delete setting; fields left out keep their value. The log destination cannot be changed. Returns the system.

Destination, 2 operations

get_log_destinationGet log destinationGETReturns one log destination with its syslog host, port, description and filter.
list_log_destinationsList log destinationsGETLists the account's log destinations, each with the syslog host and port senders log to and its filter.

Account, 1 operation

get_account_usageGet account usageGETReturns the log data the account has transferred since the start of the billing period, in bytes and as a percentage of the plan, with the plan and hard limits.

Archive, 1 operation

list_archivesList archivesGETLists the account's log archive files, one per period (usually a day), with the time span, file name such as 2016-12-27.tsv.gz and size in bytes. Downloading them is not offered here.

Join, 1 operation

add_system_to_groupAdd system to groupPOSTAdds a system to a group, so the group's searches and alerts cover it.

Leave, 1 operation

remove_system_from_groupRemove system from groupPOSTRemoves a system from a group.

User, 1 operation

list_usersList usersGETLists the members of the Papertrail account with their user id and email address (personal data).

Use Papertrail from Claude Code, Cursor or Codex

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

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