Skip to main content
Glama
PedroHenriqueNS

reapfield

by PedroHenriqueNS
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
ANTHROPIC_API_KEYNoAPI key for Anthropic, only needed to learn new selectors.
REAPFIELD_MCP_ALLOW_PRIVATENoSet to '1' to allow connections to private or loopback IP addresses (for local development).

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
scrapeA

Extract structured fields from a web page.

`fields` is comma-separated with optional inline types, e.g.
"title, price:float, in_stock:bool". Field names are arbitrary.

A field that could not be extracted comes back as null with an entry in
`misses` explaining why -- that is a normal result, not a failure.

Cost control: `no_llm=True` uses only structured data and already-cached
selectors, so the call is free; `max_llm_calls` caps what an uncached page
may spend. `scroll` and `paginate` cost extra fetches, not extra tokens.

There is no `strict`: it exists on the CLI only to pick an exit code, and
`misses` already tells you what was not found.
list_cached_selectorsA

Show the CSS selectors already learned for a domain. Costs nothing.

refresh_selectorsA

Forget the cached selectors for these fields so the next scrape re-derives them.

Returns the entries that were dropped. Re-derivation is lazy by design: it
needs a page to look at, and it happens on the next scrape of one.
Config-pinned selectors live in a separate store and are never touched.
prepare_issue_reportA

Prepare a bug report about reapfield itself. Does NOT submit it.

Call this only when you hit a real bug in reapfield during real work and
have verified a fix. It searches existing issues first; if `duplicate` is
true, stop. Otherwise show the user `body` and ask for authorization -- they
open `submit_url` themselves.

Never include credentials, private URLs, or personal data.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.1/5.0

Scored across 4 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: scrape extracts data, list_cached_selectors shows cached selectors, refresh_selectors removes them, and prepare_issue_report handles bug reporting. No two tools overlap in function, making selection unambiguous.

Naming Consistency4/5

Most tools follow a verb_noun pattern (list_cached_selectors, refresh_selectors, prepare_issue_report), but scrape is a bare verb. This is a minor deviation that does not impair readability or predictability.

Tool Count5/5

With 4 tools, the server is well-scoped for its purpose. Each tool is necessary: scrape for core functionality, list and refresh for cache management, and prepare_issue_report for maintenance. No bloat or excessive thinness.

Completeness4/5

The core workflow of scraping with cached selectors is well covered: scrape handles extraction, list shows cache state, refresh allows re-derivation. Minor gaps exist, such as no direct way to manually set selectors, but the lazy re-derivation design mitigates this. The self-report tool is an optional extra rather than a missing operation.

Maintenance

ActivitySlowing
ResponsivenessNo issues

Resources