A side-by-side look at the Clment and Contracts 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.
Contracts 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.
Clment is categorized under Legal and uses an install path we have not confirmed yet. Contracts belongs to Legal and uses a remote HTTP/SSE transport. Pick Clment for legal work and Contracts for legal.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. Clment has no confirmed install command yet — follow its own setup instructions.
Clment has no declared pricing — check the project's own site. Contracts has no declared pricing — check the project's own site. 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 contracts 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. Contracts has 42/100 (Fair) with 1 views, 0 installs and 0 GitHub stars.