I hear it a lot from people and GPTs about JSON RPC (ie. MCP) being simpler, direct, explicit, and possessing a reduced overhead. All true. It is a remote procedure call using JSON. You just want to get something done. It is function. It is operational. It is actionable. I get it. It scratches an itch and gets things done. Which makes sense in any given moment.
The reason JSON RPC is simpler, direct, explicit, and comes with reduced overhead is because it is very tactical. It comes without the burden of design, product, and strategy. It comes without much wider awareness. It satisfies a need and gets things done. It is easy to wrap your head around. It meets my emotional needs in this given moment.
However, the accounting for each individual call will still have to be done at some point. You may not want to be burdened by business, product, architecture, design, and where this procedure fits into the bigger picture before you develop. You probably haven’t caught the attention of governance and compliance yet. However, eventually the accounting for each transaction will have to occur, and the books will have to be reconciled—but we’ll worry about that down the road.
