An Airtable base with company, value, stage, and owner columns is most of a CRM already. What it doesn't have is a safe way to let a sales team change it. This build wraps the base in one Task, mounts that Task on an MCP server, and gives a rep a chat window instead of a login to the table.
What's covered
- A single dispatcher method with modes for
show,open,pitched, andlost, so every read and write goes through a defined action - Mounting the Task on an MCP server and configuring it in a Claude project
- Working the pipeline in plain language: creating a deal, moving it to pitched, recording a loss with a reason, and watching the Airtable rows change alongside the chat
A rep with edit access to Airtable can change any cell in any row, including the ones nobody asked them to touch. A rep with these four modes can list the pipeline, open a new deal, move it to pitched, and close it as lost with a reason. That is the whole vocabulary.
Airtable is in the demo because the rows are visible on screen while the chat runs. The same Task would work against Postgres, MySQL, or anything else reachable from Python. Since the modes are exposed as MCP tools, the same CRM is available from an Aisle project, ChatGPT, or Claude Code without building it again.