Skip to main content
Glama

Server Details

Impri MCP server — human-in-the-loop approval inbox for AI agents

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
Repository
sekera-radim/impri
GitHub Stars
6
Server Listing
Impri
ChatGPT
–
Claude
–

TDQS

A4.2/5.0

Scored across 8 tools

Disambiguation4/5

Most tools target distinct operations in the approval/watcher lifecycle. The only real overlap is impri_create_watcher vs impri_create_watcher_from_preset, but descriptions clearly frame one as raw-config and the other as the preset-driven path, and the docs explicitly steer agents to prefer presets.

Naming Consistency4/5

Tools share a consistent impri_ prefix and mostly follow a verb_noun pattern (push_action, await_decision, create_watcher, list_watchers, report_result). impri_inbox_status is a noun-style name, a minor deviation, but overall the set is predictable.

Tool Count5/5

Eight tools is well-scoped for an approval-inbox plus watcher-monitoring server. Each tool maps to a necessary step (discover presets, create, list, submit, await, report, check inbox depth) without redundancy.

Completeness3/5

The push→await→report loop and watcher creation/discovery are covered, but the watcher lifecycle has notable gaps: no update/pause/delete/resume for watchers, and no way to list individual actions (only a brief pending summary via inbox_status). Agents can work around these but the surface feels partial.

Available Tools

8 tools
impri_await_decisionAwait human decisionA
Read-onlyIdempotent
Inspect

Poll until the human approves, rejects, or the timeout elapses.

Checks GET /actions/:id every 5 seconds and returns as soon as the action leaves the pending state.

Decision meanings: "approved" — proceed with the action; any reviewer edits are included in preview/payload "rejected" — abort; respect the decision and do not proceed "expired" — the approval window closed; create a new action if the task is still relevant

On timeout the action stays pending in the inbox. Call impri_inbox_status to check queue depth and consider pausing further submissions.

Typical usage:

  1. impri_push_action → get action_id

  2. impri_await_decision(action_id) → wait for human decision

  3. If approved: execute the action, then impri_report_result(action_id, "executed")

Inputs: action_id (required), timeout_s. Returns: diff, status, payload, preview, +4 more

impri_create_watcherCreate watcherAInspect

Create a watcher that monitors external sources (RSS feeds, Reddit, URL diffs) and delivers matching items to the approval inbox or a webhook.

The watcher runs on the schedule you specify, deduplicates items by URL/content-hash, and delivers only new matches. The first run establishes a baseline and does not generate alerts.

Example — watch an RSS feed for AI-related news: spec: { name: "AI launches radar", kind: "rss", config: { url: "https://openai.com/news/rss.xml" }, keywords: ["launch", "gpt-", "voice"], keywords_none: ["funding", "benchmark"], min_score: 1, schedule: { every: "8h", jitter: "4h" } }

Returns { watcher_id, name, kind, status, next_run_at }.

Inputs: spec (required). Returns: kind, name, status, watcher_id, +1 more

impri_create_watcher_from_presetCreate watcher from presetAInspect

Create a watcher from a preset template by supplying the preset id and param values.

Presets handle all watcher config construction — URL building, keyword setup, SSRF validation — so you only provide the param values listed by impri_list_watcher_presets.

The schedule defaults to the preset's recommended interval but can be overridden. The name defaults to "{preset title}: {primary param value}" if omitted.

Returns { watcher_id, name, kind, status, next_run_at }.

Examples:

Watch the HN front page (no params needed): preset_id: "hn-front-page" params: {}

Watch a subreddit for new posts: preset_id: "reddit-subreddit" params: { subreddit: "MachineLearning" }

Watch a GitHub repo for new releases, check every 2 hours: preset_id: "github-releases" params: { owner: "fastify", repo: "fastify" } schedule: { every: "2h" }

Watch HN for keyword with a custom min_points threshold: preset_id: "hn-keyword" params: { keyword: "rust programming", min_points: "25" }

Inputs: params (required), preset_id (required), name, schedule. Returns: kind, name, status, watcher_id, +1 more

impri_inbox_statusCheck inbox statusA
Read-onlyIdempotent
Inspect

Check how many actions are waiting for human decisions.

Returns the pending count and a brief list of pending action titles. Call this before starting a large batch of tasks — if the inbox is backed up, pause and let the operator catch up to avoid actions expiring before they are reviewed.

Inputs: no named parameters. Returns: pending_count

impri_list_watcher_presetsList watcher presetsA
Read-onlyIdempotent
Inspect

List all available watcher presets with their parameters.

Presets are pre-configured watcher templates for common sources (Hacker News, Reddit, GitHub, npm, YouTube, arXiv, etc.). Each preset has an id, a human-readable title, required and optional params, and a default schedule.

Call this first to discover which preset fits your monitoring goal, then use impri_create_watcher_from_preset to create the watcher by supplying only the preset_id and param values. No deep knowledge of watcher config schemas is needed.

Example output: Community: - hn-front-page: "Hacker News Front Page" (rss) — no params required - reddit-keyword: "Reddit – Keyword Search" (reddit_search) — params: query, [subreddit]

Inputs: no named parameters. Returns: presets

impri_list_watchersList watchersA
Read-onlyIdempotent
Inspect

List all configured watchers, optionally filtered by status.

Returns the watcher count and a summary line per watcher (id, name, kind, status). Use this to audit what is being monitored, check for degraded watchers, or find a watcher_id for further operations.

Inputs: status. Returns: count, watchers

impri_push_actionPush action for approvalAInspect

Submit an action to the Impri human-approval inbox.

The action appears in the operator's web and mobile inbox as a card with a title, formatted preview, and optional tap-to-edit fields. The operator approves or rejects with one tap; you poll for the decision with impri_await_decision.

Returns { action_id, status: "pending", inbox_url }. Save action_id — you need it for all follow-up calls.

Example — send a draft Reddit reply for review: kind: "reddit.comment" title: "Reply: Why is resume advice so conflicting?" preview: { format: "markdown", body: "The advice conflicts because different advisors optimise for different audiences..." } target_url: "https://reddit.com/r/cscareerquestions/comments/..." editable: ["preview.body"] // lets the reviewer tweak wording before approving

Inputs: kind (required), title (required), preview (required), payload, +4 more. Returns: status, action_id, inbox_url

impri_report_resultReport execution resultAInspect

Report whether you successfully executed an approved action.

Closes the audit loop — the operator sees 'executed' or 'execute_failed' in the inbox alongside the original action and decision. Always call this after attempting an approved action, even on failure.

Statuses: "executed" — action was carried out successfully "execute_failed" — execution attempt failed (include the error in detail)

Inputs: status (required), action_id (required), detail. Returns: detail, status, action_id, updated_at

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server that provides human-in-the-loop approval for risky AI agent actions, with durable state and audit logs.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      This MCP server gives AI agents unrestricted read, search, and draft access to a locally archived set of IMAP mailboxes, while every write at the mail provider (send, move, archive, mark, Trash) becomes an inspectable approval request that a human clears in a web UI first. It also issues scoped, expiring API keys and logs each approved action's outcome.
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      An MCP server that enables AI agents to pause and request human approval or information via Slack, Telegram, or macOS dialogs before proceeding with actions.
      2
      15
      Apache 2.0
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.