Remove someone’s access
Choose who can use or edit the app. Remove their access, including access through a group, when they no longer need it.
Owners and organization admins retain access.
Create an internal app with your coding agent, then give your team access.
Your agent handles setup and publishing.
Renewal pricing calculator
40$12015%12 monthsRefert is optimized for Claude Code. Publish an internal app in one step from your agent with the CLI or the MCP server. Refert handles access, versions, and a kill switch. Refert is in private beta.
CLI
refert publish ./my-toolMCP
{
"mcpServers": {
"refert": {
"command": "cmd",
"args": [
"/c",
"npx",
"-y",
"@refert/mcp"
]
}
}
}A shared link still requires sign-in.
You keep control after publishing.
A team using Refert to publish internal tools built by coding agents.
Paste it into your coding agent. Your agent handles the setup and asks you to approve the connection. Then describe the app you want.
Read the agent instructionsGo to https://app.refert.app/agent-guide.md and fetch the .md, then follow it to set up Refert and deploy my first tool.
You describe the app you need in your coding agent. The agent writes the code, sets up Refert, and publishes the app. You approve the connection in your browser.
Use Claude Code, Cursor, Codex, Windsurf, Aider, or another coding agent that can read the Refert agent guide and run its setup instructions. You keep using the agent you already work with.
You choose which people or groups in your organization can use it. The owner and organization admins also have access. People sign in before opening the app. Copying a link does not grant access.
Each signed-in person has separate saved data. Giving someone access to your app does not automatically give them your stored dataset.
Ask your agent to change the app and publish it again. Refert keeps the earlier versions. Restoring a previous version keeps your saved data intact.
Remove their individual access to each app and any group access that lets them use it. Organization admins retain access through their role; an organization owner can change that role. The current build does not automatically handle employee offboarding.
The app owner or an organization admin can disable it in Refert. New runs are rejected while it is disabled. You can enable it again when you are ready.
Refert currently focuses on internal apps shared within an organization. Public apps and fully managed infrastructure are part of the longer-term direction. They are not available in the current build.
The current build supports agent-published internal apps, sign-in, sharing, saved data, version history, activity records, and disabling apps for local, trusted use. Managed cloud hosting, isolated execution, and automatic scaling are still planned.