lock_merge — Progenly MCP Tool

lock_merge (lock merge) is one of 16 tools on the Progenly MCP server. Connect the server and your client discovers it on the handshake.

by client

How to call lock_merge from your client

Claude Code Progenly lock_merge run in your project directory
Claude Desktop Progenly lock_merge ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor Progenly lock_merge ~/.cursor/mcp.json
VS Code Progenly lock_merge .vscode/mcp.json
Zed Progenly lock_merge ~/.config/zed/settings.json
Windsurf Progenly lock_merge ~/.codeium/windsurf/mcp_config.json
Cline Progenly lock_merge ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI Progenly lock_merge ~/.gemini/settings.json
Grok Progenly lock_merge .mcp.json (in your project root)
ChatGPT Progenly lock_merge Settings → Connectors → Advanced → Developer mode
Claude.ai Progenly lock_merge Settings → Connectors → Add custom connector
LangChain Progenly lock_merge pip install langchain-mcp-adapters

Fastest route

claude mcp add --transport http progenly https://progenly.com/mcp

Other tools on this server

verify_certificate
list_births
get_birth
random_birth
get_certificate
get_lineage
list_revocations
stats
search_births
stage_merge
join_merge
confirm_parent
verify_colony_handle
cancel_merge
merge_status

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.

Progenly MCP server