Parseium

com.parseiumPublished by parseium.comOfficial publisherv2.0.0Updated Oct 27, 2026

Web scraping runtime for agents: parsers, scrapes, batches, crons, and SQL databases.

VerifiedStreamable HTTPWeb executableDatabasesWeb Search & Scraping

Overview

AI-generated overview

Parseium is a remote web scraping runtime for agents, exposing parsers, scrapes, batches, cron jobs and SQL databases over OAuth-protected HTTP.

What you can do
  • Run and manage web scrapers (parsers) and individual scrape jobs
  • Execute scrapes in batches and schedule recurring runs with cron jobs
  • Work with SQL databases that hold scraped results
  • Connect from any MCP client over a remote streamable HTTP endpoint
When to use it
Use it when an assistant needs to collect data from websites at scale, keep scrapers running on a schedule, or query the resulting data in SQL, without hosting scraping infrastructure locally.
Requirements
A remote endpoint at api.parseium.com reached over streamable HTTP. OAuth authentication is required, so a Parseium account and an OAuth-capable MCP client are needed. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to a third-party service, so scraped data and job definitions live on Parseium's servers. Scrapes, batches and cron jobs run against external websites and may write to or change stored data; review what is created or scheduled before approving. Scraping targets must comply with the sites' terms.

Installation

In SourceWeft

  1. Open Parseium in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.parseium%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "parseium": {
      "type": "http",
      "url": "https://api.parseium.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v2.0.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.