A side-by-side look at the Clment and Open Agreements MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
No tool names declared yet. Check the project README from the listing page.
Open Agreements tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Clment
No confirmed install command for Clment yet — follow the setup steps linked from its listing page rather than a guessed package name.
Open Agreements
No confirmed install command for Open Agreements yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Clment is categorized under Legal and uses an install path we have not confirmed yet. Open Agreements belongs to Legal and uses an install path we have not confirmed yet. Pick Clment for legal work and Open Agreements for legal.
Neither server has a confirmed install command yet, so we don't publish a guessed config. Follow each project's own setup instructions, linked from its listing page.
Clment has no declared pricing — check the project's own site. Open Agreements is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add clment and open-agreements-open-agreements as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Clment has a quality signal of 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Open Agreements has 47/100 (Fair) with 3 views, 0 installs and 61 GitHub stars.