mcp-tools-reference

A reference guide to the seven tools provided by Remarc’s MCP server, a standard way for an agent to communicate with external tools.

In plain words
What is it for?
Use it to list sessions or comments, retrieve a comment, change one or many statuses, rename a session, or create a paired session.
Why use it?
It explains which tool to use for sessions, comments, statuses, screenshots, and web-element feedback without guessing the tool names or filters.

Agent

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add agents/metedata/remarc/mcp-tools-reference
Clone the repo
git clone --depth 1 https://github.com/metedata/Remarc
Per session 22 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.
When invoked 516 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00022 $0.00516
Opus 5 $0.00011 $0.00258
Sonnet 5 $0.00004 $0.00103
Haiku 4.5 $0.00002 $0.00052

Measured 2d ago against content hash 064495c2f248, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

mcp-tools-reference scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

docs-site/src/content/docs/agents/mcp-tools-reference.md · 40 lines

How it starts

The opening of the file, as written. The whole thing — 40 lines — stays where its author put it; the contents beside it link to each section on GitHub.

The Remarc MCP (Model Context Protocol) server exposes seven tools. Every connected agent gets the same set regardless of how it was installed; setup paths are in the agent overview.

Tools

Each tool and what it does:

Tool What it does
remarc_list_sessions Lists active sessions, marks the active one, and shows open, in-progress, and resolved counts.
remarc_list_comments Lists comments, optionally filtered by session_id, status, or type. Types: comment, screenshot, quickNote, critMode, webElement.
remarc_get_comment Returns one comment by full UUID or the 5-character short ID shown on the card. Includes the image path for screenshot comments and the CSS selector, component name, and file path for web element comments.
remarc_set_status Sets one comment's status. resolved requires a summary of what was done, which appears on the card in Remarc.
remarc_bulk_set_status Sets the status of many comments at once, with a shared summary or per-comment summaries.
remarc_rename_session Renames a session.
remarc_create_session Creates a session paired to the current agent conversation and makes it active.

Statuses

Agents use these exact status strings:

Status Meaning
open Not yet accepted by the agent.
handedOff You handed the comment to the agent to address.
inProgress The agent is actively working this comment.
resolved Done, with a resolution summary.

These map to the Open, Handed Off, In-Progress, and Resolved dots on comment cards; see statuses and history.

Deliberate limits

No tool deletes or closes sessions. Session cleanup happens in the app (or through your integration's conversation-cleared setting), so an agent can never destroy a container of your feedback.

Agents should not edit comments.json directly. The MCP tools are the only safe write path; hand-editing the data file risks losing comments to concurrent writes.

Read the full file on GitHub · 40 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 40 lines · 22 tokens per session scan A 064495c2f248

Subscribe to this mod's changes

mcp-tools-reference is an agent published in the GitHub repository metedata/Remarc (66 stars, last pushed 11d ago), licensed MIT. It adds 22 tokens to every session and 516 once invoked, about $0.0001 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.