Twins for Postgres and REST: declared-subset Postgres, spec-defined REST, migration proof.
MCPpedia last refreshed this data
com.cmdrvl/twinning is an MCP server that twins for Postgres and REST: declared-subset Postgres, spec-defined REST, migration proof. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 62/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"twins": {
"args": [
"--workdir",
"/absolute/path/to/project"
],
"command": "/absolute/path/to/twinning-mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Twins for Postgres and REST: declared-subset Postgres, spec-defined REST, migration proof.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked @cmdrvl/twinning-mcp against OSV.dev.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in data
Token-efficient database MCP server for PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, SQLite
Manage Supabase projects — databases, auth, storage, and edge functions
A cross-platform desktop application for managing AI Agents and MCP Servers. 一款用于管理AI智能体与MCP服务器的跨平台桌面应用程序。
Extract data from any website with thousands of scrapers, crawlers, and automations on Apify Store ⚡
MCP Security Weekly
Get CVE alerts and security updates for com.cmdrvl/twinning and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Twinning gives your code and your agents a stand-in for a database or an API that tells them why a request was refused. Point it at a Postgres schema or an OpenAPI spec and it serves a local twin. Your client connects with its normal driver, a write that breaks a constraint comes back with the real SQLSTATE and a reason, and a report records what happened. Use it to rehearse extraction code and pipelines before they touch a real database, to check a migration by replaying queries against old and new snapshots, and to test API clients against a spec-defined contract. Anything outside the declared contract is refused with a reason instead of guessed.
Paste this prompt into your coding agent (Claude Code, Cursor, Codex, or any agent that can run shell commands) to install the twinning MCP server on your machine. It downloads the prebuilt release, verifies its checksum, and configures your MCP client. It works on macOS and Linux. The Windows archive does not include the MCP server yet.
Set up the twinning MCP server on this machine. Work through the steps in order,
run each command yourself, and tell me what you did and what you saw. Do not use
sudo, and do not change any MCP server entry other than "twins".
1. Detect my OS and CPU. Supported targets are aarch64-apple-darwin,
x86_64-apple-darwin, x86_64-unknown-linux-gnu and aarch64-unknown-linux-gnu.
If this is Windows, stop and tell me the MCP server is not available there yet.
2. Find the latest release tag of https://github.com/cmdrvl/twinning (for example
by following the redirect from https://github.com/cmdrvl/twinning/releases/latest).
The archive is named twinning-<tag>-<target>.tar.gz and the checksums file is
named SHA256SUMS, both under https://github.com/cmdrvl/twinning/releases/download/<tag>/.
3. Create a new, empty directory ~/.local/share/twinning/<tag> and download the
archive and SHA256SUMS into it with curl -fL (not a browser). Verify the archive
against its line in SHA256SUMS (shasum -a 256 -c, or sha256sum -c on Linux).
If the checksum does not match, stop and tell me. Do not extract it.
4. Extract the archive into that directory. It must contain two executables,
twinning and twinning-mcp. Remember their absolute paths.
5. Run "<dir>/twinning-mcp doctor". It must print "health: ok (healthy (READY))".
If macOS refuses to run the binaries, run
"xattr -d com.apple.quarantine <dir>/twinning <dir>/twinning-mcp" and retry.
6. Ask me which project directory twins should work in (default: the current
directory) and which MCP client I use. Then configure it:
- Claude Desktop: "<dir>/twinning-mcp --workdir <project> setup --client claude-desktop"
- Cursor: "<dir>/twinning-mcp --workdir <project> setup --client cursor"
- Claude Code: "claude mcp add twins -- <dir>/twinning-mcp --workdir <project>"
- Anything else: run "<dir>/twinning-mcp --workdir <project> setup --client claude-desktop --print"
and add that "twins" entry to my client's MCP configuration by hand.
Tell me if I need to restart or reload the client.
7. Check it works without the client: write a file schema.sql in the project
directory containing
CREATE TABLE deals (deal_id TEXT PRIMARY KEY, deal_name TEXT NOT NULL);
then start the server with "<dir>/twinning-mcp --workdir <project>" and, over
MCP stdio, call twin_doctor, then twin_start with kind "postgres" and
schema_path "schema.sql", then twin_stop with the returned twin_id. Report the
result of each call. Stop the server when done.
If any step fails, stop and show me the exact command and its full output.
Twinning is built by CMD+RVL. If you work with filings or structured finance data and want a sourced answer, you can chat with Cairn, our research assistant, over text at textcairn.com.
Twinning is not a general database. The MCP ma