Agmt Verbatim

MCP · CLI · local files

Connect Agmt Verbatim to an agent.

The remote MCP server uses Streamable HTTP at https://verbatim.agmt.legal/mcp. A local stdio option is included in the JavaScript package for agents that can launch local MCP servers.

Use it when the user asks to parse a Word agreement or redline. The remote server cannot read a file directly from the user's disk. It accepts document bytes, a URL or an encrypted upload handle; the local stdio tool can read a path when called.

Text, changes and comments are verified against the source on every call. The parser makes no LLM calls. Tool annotations describe real behavior: parse and source tools update quota and deduplication metadata, upload creation creates a session, and discard deletes an upload.

Remote server

Claude Code

Add the remote server with the documented CLI command:

claude mcp add --transport http agmt-verbatim https://verbatim.agmt.legal/mcp

Cursor

For a remote connection, add the server URL to .cursor/mcp.json:

{
  "mcpServers": {
    "agmt-verbatim": {
      "url": "https://verbatim.agmt.legal/mcp"
    }
  }
}

Claude Desktop

Add the remote MCP server URL in Settings → Connectors → Add custom connector:

https://verbatim.agmt.legal/mcp

Remote authentication and availability depend on the service configuration. Keyless access is available for a limited daily trial; the remote setup does not require a key to try it.

Local stdio server

Claude Code

The package's stdio server proxies remote tools and adds agmt_verbatim_parse_file(path). It reads a local file only when that tool is called, then sends its bytes to the API.

claude mcp add --transport stdio agmt-verbatim -- npx -y @agmt/verbatim mcp

Cursor

For local stdio, use this configuration in .cursor/mcp.json:

{
  "mcpServers": {
    "agmt-verbatim": {
      "command": "npx",
      "args": ["-y", "@agmt/verbatim", "mcp"]
    }
  }
}

Claude Desktop

Some Claude Desktop configurations support stdio MCP servers. If using one, the configuration entry is:

{
  "mcpServers": {
    "agmt-verbatim": {
      "command": "npx",
      "args": ["-y", "@agmt/verbatim", "mcp"]
    }
  }
}

Use the remote connector flow above when configuring a remote server in Claude Desktop.

VS Code and other local stdio hosts

The build specification includes VS Code in the local-agent flow and documents the command npx -y @agmt/verbatim mcp. Configure that command using the host's own stdio MCP settings. This page does not prescribe a client-specific configuration file format that has not been established.

Available tools

Tool behavior

  • agmt_verbatim_parse parses a source and returns the requested view, summary and quota metadata.
  • agmt_verbatim_list_changes, agmt_verbatim_list_comments, agmt_verbatim_define and agmt_verbatim_check_references parse a source and return the selected ledger or result.
  • agmt_verbatim_create_upload creates an encrypted browser-upload session; agmt_verbatim_discard deletes it.
  • The local stdio server additionally exposes agmt_verbatim_parse_file(path).

Parse and source tools record quota and keyed deduplication metadata. They are therefore not read-only or idempotent from the service's perspective. The server annotates each tool separately for its actual behavior.

Quota and key handling

When a key is useful

  • Without a key: 10 documents per day per IP hash, up to 5 MiB and 100 page-equivalents per document.
  • With a free key: 50 documents per day, up to 25 MiB and 300 page-equivalents per document.
  • When the keyless daily quota is exhausted, the API returns a 429 instruction telling the agent to ask the user for a key. Get one at Agmt Verbatim API keys.

Page-equivalents are ceil(words ÷ 500). The same document parsed again with the same key within 24 hours does not count toward quota. A separate request burst limit applies.

Remote files

Choose an input the server can access

  1. Send file_base64 when the agent can read the attachment (the documented remote flow uses files up to 4 MB).
  2. Pass a URL for a file hosted elsewhere; the service fetches that URL.
  3. For a file available only on the user's device, create an upload session and give the user its link. The browser encrypts the file before upload; the agent then parses the returned handle.

For browser uploads, encrypted data is accessible for 15 minutes. Physical deletion is asynchronous, and this deployment has no verified physical-deletion deadline. The 15-minute access period is not a physical-deletion promise.

The application design processes document bytes in Worker memory and omits them from application logs and databases; local canary CI exercises that boundary. Production configuration, deletion monitoring and operational controls have not yet been verified. Account, usage and keyed deduplication metadata are separate from document plaintext.

Further reading