DEV Community

Douglas D
Douglas D

Posted on

Your CRM probably has an MCP server now. Here is why I still run my own.

Most of the big CRMs shipped MCP servers this year. Fair question, then: why did I keep building one?

I get asked some version of this every week, so here are the actual answers.

"Your CRM already has an MCP server. What is left to build?"

A CRM MCP server can answer CRM questions. That is the whole ceiling.

The problems that actually cost me money do not live inside one tool. They live in the seams. A task that has gone quiet. A client I have not spoken to in nine days. An open invoice attached to that same client.

Any one of those is unremarkable. You would not act on any of them alone. Together they are a decision I did not know I needed to make, and no single system holds all three, so no single-system MCP server can put them in front of me.

That join is the entire reason Founders OS exists. Not more tools. One read across CRM, ledger, and decision history at the same time.

"So it tells you what to do?"

No, and I am careful about this.

It surfaces the relationship. The invoice and the silence and the stalled task get put next to each other in one answer. What that means is my call. I have no interest in shipping something that pretends to have judgment about my business, and you should be skeptical of anything that claims otherwise.

The useful version is narrower and more honest: show me the thing I would not have looked for.

"Is this just search over my data?"

It reads live records through typed tools and joins them in one pass. Ask about a customer and you get the record, what has been invoiced and paid and is still open, and the interactions and decisions attached to them. One question, one answer, three domains.

The difference matters when the data changes hourly. There is no index to go stale.

"Where does the data live?"

Your own Postgres. It runs over stdio, self-hosted, MIT licensed.

That is a deliberate choice, not a slogan. Business data is the category where I want the storage decision to be mine, and I want no part of the migration conversation if I ever change my mind. Deploy it yourself, point it at your database, done.

"Which AI tools does it work with?"

Anything that speaks MCP. I use it in Claude and in Cursor against the same database, which is the point. The context follows the work, not the app.

"What is it bad at?"

Setup. It is deploy-it-yourself, so there is real work between cloning the repo and getting your first answer. If you want to sign up and be running in ninety seconds, this is not that, and I would rather say so than waste your afternoon.

It is also only as good as what is in it. Empty database, useless answers. Same as every system of record ever built.

If you are building on MCP or just want to poke at the schema:

Repo: https://github.com/OurThinkTank/founders-os Site: https://foundersmcp.com

Happy to answer anything in the comments, especially on the cross-domain query design. That was the hard part.

Top comments (0)