Sign and register statements on a Forestrie log MCP Server

What this does

Sign and register statements on a Forestrie log exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

FORESTRIE_BASE_URL
FORESTRIE_ROOT_LOG_ID
FORESTRIE_GRANT
FORESTRIE_AUTHORITY_GRANT
FORESTRIE_COORDINATOR_URL
FORESTRIE_KNOWN_SEALER_KEY
MCP_REGISTER_HOME
MCP_REGISTER_KEY_FILE
MCP_REGISTER_AUTHORITY_KEY_FILE
MCP_REGISTER_PAYER_KEY_FILE
MCP_REGISTER_PAY_MAX_PER_CALL
MCP_REGISTER_PAY_MAX_PER_DAY
MCP_REGISTER_PAY_NETWORK
MCP_REGISTER_PAY_ASSET
MCP_REGISTER_PAY_TO
MCP_REGISTER_PAY_ALLOW_MAINNET

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install Sign and register statements on a Forestrie log?

Run the Claude Code command in the install section to add Sign and register statements on a Forestrie log to Claude Code, or copy the ready-made config for your client from the install section on this page. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with Sign and register statements on a Forestrie log?

This page carries setup and config for Claude Code, Claude Desktop, Cursor and VS Code. Any other MCP client that accepts a standard server config can connect to Sign and register statements on a Forestrie log as well.

Does Sign and register statements on a Forestrie log need an API key?

Yes. Before it can run, set these environment variables: FORESTRIE_BASE_URL, FORESTRIE_ROOT_LOG_ID, FORESTRIE_GRANT, FORESTRIE_AUTHORITY_GRANT, FORESTRIE_COORDINATOR_URL, FORESTRIE_KNOWN_SEALER_KEY, MCP_REGISTER_HOME, MCP_REGISTER_KEY_FILE, MCP_REGISTER_AUTHORITY_KEY_FILE, MCP_REGISTER_PAYER_KEY_FILE, MCP_REGISTER_PAY_MAX_PER_CALL, MCP_REGISTER_PAY_MAX_PER_DAY, MCP_REGISTER_PAY_NETWORK, MCP_REGISTER_PAY_ASSET, MCP_REGISTER_PAY_TO, MCP_REGISTER_PAY_ALLOW_MAINNET. They go in the env block of your MCP config.