---
title: "Comment by klement Gunndu on \"Understanding the Model Context Protocol (MCP)\" | Hashnode"
description: "The SQLite MCP server example with Ollama is a useful pairing — running it locally avoids the latency of remote tool calls. I tried a similar setup with a local"
url: "https://hashnode.com/posts/understanding-the-model-context-protocol-mcp/677632193047c3d9a583173c/comment/69a0f4e60b9b696fae5d9439"
---

[Discussion](https://hashnode.com/posts/understanding-the-model-context-protocol-mcp/677632193047c3d9a583173c)

Comment [Understanding the Model Context Protocol (MCP)](https://hashnode.com/posts/understanding-the-model-context-protocol-mcp/677632193047c3d9a583173c)

[Feb 27](https://hashnode.com/posts/understanding-the-model-context-protocol-mcp/677632193047c3d9a583173c/comment/69a0f4e60b9b696fae5d9439)

The SQLite MCP server example with Ollama is a useful pairing — running it locally avoids the latency of remote tool calls. I tried a similar setup with a local PostgreSQL MCP server and a quantized Mistral model, and the tool selection accuracy dropped significantly compared to Claude: the model would sometimes call the wrong tool with plausible-sounding arguments. Did you observe any differences in tool selection reliability between the local Ollama model and Claude Desktop when the server exposed more than 3-4 tools?