Integration

New Sloth integration

New Sloth monitors public webpages (news, blogs, press releases, jobs, products) and turns their updates into structured data feeds. List the monitored sources with their feed URLs, start monitoring a new webpage (articles are auto-detected with AI), and delete a source. Each source's feed URL serves the extracted items as XML/RSS, or JSON when the extension is changed to .json; the feed itself is read at that URL, not through this API. API access needs a plan that includes it, and new sources count toward the plan's source allowance. Authentication is HTTP Basic: the API key as username and the API secret as password, both from the account profile.

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in New Sloth.Built from the 3 New Sloth tools below, on the connection you add once.

What you can do with New Sloth

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.

  • create_sourceCreate sourcePOSTStarts monitoring a public webpage: New Sloth auto-detects its articles with AI and returns the new source with its feedRssUrl (checked is 0 until the first check). Saved only within the plan's source allowance.
  • delete_sourceDelete sourceDELETEDeletes a source from the account, identified by its feedRssUrl. Deleted sources cannot be restored.
  • list_sourcesList sourcesGETLists every monitored source of the account with its title, webpage URL, structured feed URL (feedRssUrl), status flags and timestamps, plus the total count.

Use New Sloth from Claude Code, Cursor or Codex

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

  1. Create your workspace

    Sign up free. Nothing to install.

  2. Connect New Sloth once

    Add your New Sloth connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.

  3. 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.

New Sloth integration FAQ

What can you do with the New Sloth integration?

LiveContext exposes 3 operations on New Sloth, covering source.

Popular integrations

Browse the whole catalog