Enables seamless integration between local Ollama LLM instances and MCP-compatible applications for advanced task management.
If you already use Ollama, the ollama mcp server is the piece that lets your assistant work with it directly. Enables seamless integration between local Ollama LLM instances and MCP-compatible applications for advanced task management.
このMCPサーバーは、ローカルのOllama LLMインスタンスとMCP互換アプリケーションの間でシームレスな統合を可能にし、高度なタスク分解、評価、ワークフロー管理を提供します。
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
task — //** - 個別のタスクにアクセスするためのURIスキームresult — //** - 評価結果にアクセスするためのURIスキームmodel — //** - 利用可能なOllamaモデルにアクセスするためのURIスキームdecompose-task — 複雑なタスクを管理しやすいサブタスクに分解evaluate-result — 指定された基準に対してタスク結果を分析add-task — 必須パラメータ: name (文字列), description (文字列)run-model — 必須パラメータ: model (文字列), prompt (文字列)MacOS — The MacOS tool exposed by this serverWindows — The Windows tool exposed by this server@modelcontextprotocol/inspector on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Configuration is passed through the environment: OLLAMA_HOST, UV_PUBLISH_TOKEN. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Ollama's toolset — task, result, model and 6 more — is a fair guide to whether it matches your workflow. It is maintained by NewAITees; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| task | //** - 個別のタスクにアクセスするためのURIスキーム |
| result | //** - 評価結果にアクセスするためのURIスキーム |
| model | //** - 利用可能なOllamaモデルにアクセスするためのURIスキーム |
| decompose-task | 複雑なタスクを管理しやすいサブタスクに分解 |
| evaluate-result | 指定された基準に対してタスク結果を分析 |
| add-task | 必須パラメータ: name (文字列), description (文字列) |
| run-model | 必須パラメータ: model (文字列), prompt (文字列) |
| MacOS | The MacOS tool exposed by this server. |
| Windows | The Windows tool exposed by this server. |
"mcpServers": {
"ollama-MCP-server": {
"command": "uv",
"args": [
"--directory",
"/path/to/ollama-MCP-server",
"run",
"ollama-MCP-server"
],
"ENV":["model":"deepseek:r14B"]
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| OLLAMA_HOST | Endpoint or connection string the server talks to. | Optional |
| UV_PUBLISH_TOKEN | Credential the server authenticates with. | Yes |
Your workspace, on speaking terms with AI — search, read and write Notion pages and databases.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Search and read your Drive — Docs, Sheets and files become context your assistant can actually use.
Your assistant inside the workspace — read channels, search history, post messages and tame the noise.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Stop letting your assistant hallucinate n8n node parameters — this server hands it the real schemas, templates and validation.