The Liftable MCP server: your store’s findings in Claude, Cursor or your own agent

What connecting it does for you

• Ask about your store from the tools you already use: what was found, the evidence, what is running, what the receipt says.
• Propose a change or record a decision from an agent of your own, within the same policy and approval rules as the app.

What Liftable reads

• Opportunities, evidence, experiments, decisions and the receipt for the store the key belongs to.

What Liftable can write

• With a propose key: a proposal, which still needs an approval. With a decide key: a decision, recorded with the key’s owner. Nothing a key can do bypasses the policy layer.

What it never reads or does

• Another store’s data: a key belongs to one store and the database enforces it with row-level security.
• A theme file, a live change or a test start that the policy would refuse.

The permissions requested

• read
• propose
• decide

These are the permissions the connector asks the vendor for, as the vendor names them. The Connections page shows the same list on the row before you connect.

How to connect

• Create a key in Settings, choosing its scope and expiry. Keys are stored hashed, show their last use, and can be revoked. Each key carries its own rate limit.

How often, and where the data lands

Live: tools answer from the store’s current data.

Questions