GRAFOMEM CGR Capture runs on your own machine — the client starts it, so there is no endpoint to ping. 58 installs a week from pypi. Last commit 17 Oct 2026.
Record agent judgments and their real outcomes on GRAFOMEM Cloud. Capture now, score later.
What the code does
We read the source, 4 d ago · rules 995398eba69f
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
inside = subprocess.run(
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Nothing serious here today
Today is the operative word: we check GRAFOMEM CGR Capture every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add cgr-capture -e 'GRAFOMEM_CGR_TENANT_KEY=<GRAFOMEM_CGR_TENANT_KEY>' -e 'GRAFOMEM_CGR_TENANT=<GRAFOMEM_CGR_TENANT>' -- uvx grafomem-cgr{
"mcpServers": {
"cgr-capture": {
"command": "uvx",
"args": [
"grafomem-cgr"
],
"env": {
"GRAFOMEM_CGR_TENANT": "<GRAFOMEM_CGR_TENANT>",
"GRAFOMEM_CGR_TENANT_KEY": "<GRAFOMEM_CGR_TENANT_KEY>"
}
}
}
}[mcp_servers.cgr-capture]
command = "uvx"
args = ["grafomem-cgr"]
env = { GRAFOMEM_CGR_TENANT_KEY = "<GRAFOMEM_CGR_TENANT_KEY>", GRAFOMEM_CGR_TENANT = "<GRAFOMEM_CGR_TENANT>" }{
"mcpServers": {
"cgr-capture": {
"command": "uvx",
"args": [
"grafomem-cgr"
],
"env": {
"GRAFOMEM_CGR_TENANT": "<GRAFOMEM_CGR_TENANT>",
"GRAFOMEM_CGR_TENANT_KEY": "<GRAFOMEM_CGR_TENANT_KEY>"
}
}
}
}{
"servers": {
"cgr-capture": {
"type": "stdio",
"command": "uvx",
"args": [
"grafomem-cgr"
],
"env": {
"GRAFOMEM_CGR_TENANT": "<GRAFOMEM_CGR_TENANT>",
"GRAFOMEM_CGR_TENANT_KEY": "<GRAFOMEM_CGR_TENANT_KEY>"
}
}
}
}Put your own values in place of
<GRAFOMEM_CGR_TENANT_KEY> (Your GRAFOMEM Cloud tenant API key (X-API-Key). Needs decisions:read for the durability guard), <GRAFOMEM_CGR_TENANT> (The tenant id you expect that key to resolve to. If the key resolves to any other tenant, every write is refused).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
GRAFOMEM_CGR_ROLE_KEYS_JSON (Role handles to public agent_key (64-hex Ed25519), inline as JSON. Example: {"cc-builder@acme":"<64-hex>"}. Use this or GRAFOMEM_CGR_ROLE_KEYS), GRAFOMEM_CGR_ROLE_KEYS (Path to a JSON file with the same role-handle to public agent_key mapping. Use this or GRAFOMEM_CGR_ROLE_KEYS_JSON), GRAFOMEM_CGR_FORBIDDEN_TENANTS (Comma-separated tenant ids to always refuse, even if pinned by mistake. Put your production tenant here), GRAFOMEM_API (GRAFOMEM Cloud base URL. Defaults to https://api.grafomem.com).
Alternatives to GRAFOMEM CGR Capture
same job, measured the same wayCapture the screen, read/render notes, and upload files on a Ratta Supernote from an AI agent.
Give LLM agents webcam access: capture photos and record short videos over MCP.
Human capability for AI agents - real-world action and human judgment.
Private document cloud for MCP agents. Claim a link, then store and recall.
Typed yes/no, pick-one and score judgments from Jev in one batched call; typed escalation back.
Notes your team and their agents build on together: write, share, comment and edit.
Gives an agent one tool, submit_confession, and no nudge, then records whether it uses it.
Scope changes against a work order, each with a reason, a date and the client's approval on record.
GRAFOMEM CGR Capture — questions
Answers built from our own checks of this server.