Capable
run.capablev2.7.2Updated Oct 1, 2026
MCP-native CRM: your assistant proposes updates, you approve them field by field.
Overview
AI-generated overview
A remote MCP-native CRM where the assistant proposes record updates that you approve field by field.
- What it does
- Capable is a hosted CRM exposed as a remote MCP endpoint. It lets an assistant work with customer relationship records and propose changes to them, with each proposed field change presented for your approval before it is applied. The registry description frames the assistant as proposing updates rather than writing them directly.
- When to use it
- Consider it when you want an assistant to help maintain CRM data but you still want a human in the loop on every change. It suits teams that prefer reviewing proposed edits field by field instead of letting an assistant write to the CRM unattended.
- Requirements
- A remote MCP endpoint at crm.capable.run over streamable HTTP; no packages, environment variables, or headers are declared. The manifest declares no authentication, so check with the provider what account or access is needed before connecting.
Before you install
The server is described as proposing updates for approval, but confirm how approvals work and whether any change can be applied without review. The manifest declares no authentication, so verify how access to your CRM data is controlled before connecting. No credentials are declared in the manifest.
Installation
In SourceWeft
- Open Capable in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"crm": {
"type": "http",
"url": "https://crm.capable.run/api/mcp"
}
}
}Tools
0Tool metadata has not been indexed yet.
Version history
1- v2.7.2LatestOct 1, 2026

