Getting started

MCP server

Let an AI tool use Siftzo directly. Give it one URL; it registers itself and sends you to a login page, so no API key is copied or stored in a config file.

Connect

The server is a remote MCP server over Streamable HTTP. The URL is the same for every client:

Server URL
https://app.siftzo.com/mcp
claude mcp add --transport http siftzo https://app.siftzo.com/mcp

Run it once, then type /mcp in Claude Code and choose siftzo to log in.

The first time, the client opens a Siftzo page in your browser. Log in, choose the organization it may use and press Allow. You need an account first: create one for free, which includes 1,000 credits a month.

Tools

  • search: Search the web and get the results: title, URL and snippet for each. DuckDuckGo (default) answers in a second or two with the real URL of every result. Use google only when Google's own ranking matters: it is slower, and only its top one or two results have their real URL (the rest are google.com/goto links). site: works but makes DuckDuckGo slower. Costs 10 credits per successful search. Use scrape to read a result.
  • scrape: Fetch a public web page and return its content as Markdown (default) or raw HTML. Proxies, browser rendering and retries are handled. Costs credits only when the request succeeds. Use this to read a page; use extract when you need specific fields.
  • extract: Fetch a page and turn it into JSON that matches a JSON Schema, a plain-language prompt, or both. Billed as the fetch plus the language model usage.
  • data: Return a page as a record with fixed fields. source=product gives name, price and availability, article gives title, author and text, metadata gives title, description and Open Graph. Cheaper than extract for these common cases.
  • get_usage: Credits used and left this month for the connected organization, and its concurrency limit.
  • list_feeds: The scheduled feeds of the connected organization, with schedule, status and last run.
  • run_feed: Start a run of a feed immediately, outside its schedule. This spends credits like a scheduled run does.

Each call runs as the organization you connected and is billed like the matching API call; see rate limits and credits. Only successful requests cost credits. Responses are cut at 60,000 characters, so ask for fields with extract on large pages.

Let a coding agent set it up

Paste this into Claude Code, Cursor or any agent. It reads llms.txt, which lists every doc page, and picks MCP or the REST API.

Prompt
Set up Siftzo (web scraping, search and extraction API) for this project.

1. Read https://www.siftzo.com/llms.txt and follow the links there for details.
2. Prefer the MCP server at https://app.siftzo.com/mcp if this tool supports remote MCP; it logs in with OAuth.
3. Otherwise use the REST API at https://api.siftzo.com with an API key in the X-API-Key header. I will create the key in the dashboard; read it from the SIFTZO_API_KEY environment variable.
4. Scrape https://example.com as a first test and show me the result.

Access and revoking

  • The connection is tied to you and one organization. If you leave the organization, it stops working.
  • Access tokens last one hour and refresh tokens 30 days. A refresh token can be used once; reusing one ends the connection.
  • An app never sees your password or your API keys. Disconnect it any time under AI connections in the dashboard.
  • Pages an AI reads can contain text that tries to give it instructions. Treat what a tool returns as data, and keep tools that can act on your behalf behind confirmation.

For client authors

The server follows the MCP authorization spec: OAuth 2.1 with PKCE (S256), public clients and dynamic client registration (RFC 7591). Start at the protected resource metadata (RFC 9728), which points to the authorization server metadata (RFC 8414).

Discovery
POST https://app.siftzo.com/mcp                          → 401, WWW-Authenticate: Bearer resource_metadata="…"
GET  https://app.siftzo.com/.well-known/oauth-protected-resource/mcp
GET  https://app.siftzo.com/.well-known/oauth-authorization-server
POST https://app.siftzo.com/oauth/register     (redirect_uris)
GET  https://app.siftzo.com/oauth/authorize    (code_challenge, S256)
POST https://app.siftzo.com/oauth/token        (authorization_code, refresh_token)

Prefer plain HTTP? The REST API does the same with an API key, and the quickstart shows the first request.