A
licenseNot graded
qualityD
maintenanceA production-grade MCP server designed for multi-tenant, authenticated, and observable AI agent systems, enabling secure tool execution across heterogeneous data sources.
66
MIT
willow-mcp
willow-mcp
エージェント非依存のMCPサーバー。SQLiteキー/値ストア、Postgresナレッジベース、Kartタスクキュー。すべてのツール呼び出しでSAP/1.0認証を実行。
pip install willow-mcpツール
ツール | 説明 |
| SQLiteストアへの書き込み |
| SQLiteストアからの読み取り |
| コレクション内のアトムを一覧表示 |
| コレクション内の全文検索 |
| アトムの削除 |
| すべてのコレクションを横断検索 |
| Postgresナレッジベースへの追加 |
| Postgresナレッジベースの検索 |
| Kartキューへのタスク送信 |
| タスクステータスの確認 |
| 保留中のタスクを一覧表示 |
すべてのツールで app_id パラメータが必要です。認証は SAP/1.0 を介してチェックされます。
Related MCP server: astra-knowledge-base-mcp
OpenClaw設定
{
"mcp": {
"servers": {
"willow": {
"command": "python3",
"args": ["-m", "willow_mcp"],
"env": {
"WILLOW_PG_DB": "willow",
"SAP_SAFE_ROOT": "~/.sap/Applications",
"SAP_PGP_FINGERPRINT": "YOUR_KEY_FINGERPRINT"
}
}
}
}
}設定
環境変数 | デフォルト | 説明 |
|
| Postgresデータベース名 |
|
| Postgresユーザー (Unixソケット認証) |
|
| SQLiteストアディレクトリ |
|
| SAFEフォルダのルート |
| (空) | 固定されたGPGフィンガープリント |
認証
openclaw-sap-gate (SAP/1.0) を使用します。各 app_id に対してSAFEフォルダをセットアップしてください：
sap-gate init my-app
# edit ~/.sap/Applications/my-app/safe-app-manifest.json
# sign it, then:
sap-gate verify my-appライセンス
MIT — Sean Campbell 2026
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
147 tool updates
v2.54.1- Removed
agent_clear - Removed
agent_dispatch_result - Removed
agent_route - Removed
agent_seed_mirror - Removed
code_graph_explain - Removed
code_graph_impact - Removed
code_graph_index - Removed
code_graph_search - Removed
code_graph_suggest - Removed
code_graph_walk - Removed
commitment_acknowledge - Removed
commitment_ingest - Removed
commitment_list - Removed
commitment_surface - Removed
context_expire - Removed
context_get - Removed
context_list - Removed
context_save - Removed
decision_propose - Removed
diagnostic_summary - Removed
dispatch_accept - Removed
dispatch_list - Removed
dispatch_read - Removed
dispatch_send - Removed
env_check - Removed
envelope_apply - Removed
envelope_list - Removed
envelope_pending_read - Removed
envelope_propose - Removed
envelope_ratify - Removed
envelope_read_discards - Removed
envelope_reject - Removed
exposure_config_get - Removed
exposure_slice - Removed
federation_call - Removed
federation_discover - Removed
federation_list_servers - Removed
fleet_health - Removed
fleet_status - Removed
fork_create - Removed
fork_delete - Removed
fork_join - Removed
fork_list - Removed
fork_log - Removed
fork_merge - Removed
fork_status - Removed
frank_append - Removed
frank_read - Removed
frank_verify - Removed
friction_flags_list - Removed
friction_scan - Removed
gap_delete - Removed
gap_list - Removed
gap_log - Removed
gap_promote - Removed
gap_purge_topic - Removed
gap_resolve - Removed
git_pull_execute - Removed
git_push_execute - Removed
gitsync_sweep - Removed
grove_ack - Removed
grove_agents - Removed
grove_bus_receive - Removed
grove_bus_send - Removed
grove_flag - Removed
grove_flagged - Removed
grove_fleet_status - Removed
grove_get_history - Removed
grove_get_identity - Removed
grove_get_thread - Removed
grove_heartbeat - Removed
grove_human_required - Removed
grove_inbox - Removed
grove_list_channels - Removed
grove_reply - Removed
grove_search - Removed
grove_send_message - Removed
grove_unflag - Removed
grove_watch - Removed
grove_watch_all - Removed
handoff_read - Removed
handoff_write_v4 - Removed
human_attestation_create - Removed
human_attestation_list - Removed
human_required_enqueue - Removed
human_required_list - Removed
human_required_resolve - Removed
integration_call - Removed
integration_list - Removed
integration_status - Removed
kb_at - Removed
kb_ingest - Removed
kb_journal - Removed
kb_journal_read - Removed
kb_promote - Removed
kb_startup_continuity - Removed
knowledge_check - Removed
knowledge_flag - Removed
knowledge_ingest - Removed
knowledge_retract - Removed
knowledge_search - Removed
knowledge_verify - Removed
lineage_link - Removed
lineage_list - Removed
lineage_record - Removed
lineage_why - Removed
nest_digest - Removed
nest_intake_file - Removed
nest_intake_flags - Removed
nest_intake_queue - Removed
nest_intake_scan - Removed
nest_intake_skip - Removed
nest_promote - Removed
nest_scan - Removed
nest_status - Removed
nestor_tool_pending - Removed
nestor_tool_route - Removed
nestor_tool_seal - Removed
pr_open_execute - Removed
receipts_tail - Removed
schema_confirm_mapping - Removed
session_bind - Removed
session_enter - Removed
session_handoff_write - Removed
session_read - Removed
session_reconcile - Removed
sessions_read_unverifiable - Removed
specialist_get - Removed
specialist_list - Removed
store_collections - Removed
store_delete - Removed
store_get - Removed
store_list - Removed
store_purge_collection - Removed
store_put - Removed
store_search - Removed
store_search_all - Removed
store_stats - Removed
store_update - Removed
task_list - Removed
task_status - Removed
task_submit - Removed
verify_handoff - Removed
whoami - Removed
willow_institutional_search - Removed
willow_web_fetch - Removed
willow_web_search
5 tool updates
v2.48.0- Added
git_pull_execute - Changed
git_push_execute1 field changed- added
Input schema / properties / baseAdded value: +{ + "default": "", + "title": "Base", + "type": "string" +}
- Added
gitsync_sweep - Added
pr_open_execute - Changed
task_submit1 field changed- added
Input schema / properties / anticipated_gatesAdded value: +{ + "anyOf": [ + { + "items": { + "type": "string" + }, + "type": "array" + }, + { + "type": "null" + } + ], + "default": null, + "title": "Anticipated Gates" +}
1 tool update
v2.36.0- Added
decision_propose
1 tool update
v2.34.0- Added
git_push_execute
2 tool updates
v2.27.0- Changed
dispatch_send1 field changed- added
Input schema / properties / envelope_idAdded value: +{ + "default": "", + "title": "Envelope Id", + "type": "string" +}
- Changed
envelope_list1 field changed- added
Input schema / properties / include_revokedAdded value: +{ + "default": false, + "title": "Include Revoked", + "type": "boolean" +}
1 tool update
v2.23.0- Added
kb_journal_read
8 tool updates
v2.19.0- Added
envelope_list - Added
envelope_pending_read - Added
envelope_propose - Added
envelope_ratify - Added
envelope_read_discards - Added
envelope_reject - Changed
session_enter3 fields changed- added
Input schema / properties / attested_atAdded value: +{ + "default": "", + "title": "Attested At", + "type": "string" +} - added
Input schema / properties / seal_sigAdded value: +{ + "default": "", + "title": "Seal Sig", + "type": "string" +} - added
Input schema / properties / verifierAdded value: +{ + "default": "", + "title": "Verifier", + "type": "string" +}
- Added
sessions_read_unverifiable
TDQS
B3.3/5.0
Scored across 147 tools
Disambiguation4/5
The tool set is enormous but organized into clear prefix families (store_*, grove_*, gap_*, knowledge_*, kb_*, dispatch_*, envelope_*, session_*, fork_*, etc.) with detailed descriptions. A few pairs could be confused (e.g., store_search vs store_search_all, grove_send_message vs grove_bus_send, handoff_write_v4 vs session_handoff_write) but their scopes are distinct enough that an agent reading descriptions would likely pick correctly.
Naming Consistency5/5
All tool names follow a consistent snake_case verb_noun (or prefix_verb_noun) pattern. Prefixes denote the domain (store, grove, gap, knowledge, kb, dispatch, fork, envelope, session, human, etc.), and verbs are consistently descriptive. There are no mixed conventions like camelCase or abbreviated ambiguities.
Tool Count1/5
147 tools is extreme for any MCP server, even one covering a broad governance/fleet management domain. The sheer volume makes the surface area unwieldy and increases the risk of a tool being overlooked or mis-selected. Per the calibration, 50+ tools is a strong mismatch; 147 far exceeds that threshold.
Completeness5/5
The tool set provides comprehensive coverage across its apparent domains: store CRUD and search, messaging and fleet coordination, knowledge base lifecycle, gap/backlog management, task queueing, dispatch workflow, fork management, envelope governance, session binding/reconciliation, human-required queue, and attestations. Each domain has create/read/update/delete or lifecycle operations, leaving very few obvious gaps.
Maintenance
ActivityNo data
ResponsivenessWithin a week
Related MCP Connectors
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
MCP-first toolbox for agents: KV storage, auth, queue, and utility tools. Free in early access.
- UnifAPIOAuthcom.unifapi
Hosted MCP server for live public-data APIs and Skills for AI agents.
Personal assistant MCP server with search, execute, packages, jobs, secrets, and integrations.
Related MCP Servers
- AlicenseAqualityBmaintenanceMCP server for managing and searching multi-tenant knowledge bases backed by SQLite with FTS5, enabling AI agents to persist and retrieve content via full-text search.132MIT
- FlicenseNot gradedqualityDmaintenanceEnterprise MCP server providing a suite of tools including file, database, GitHub, Slack, calendar, email, vector search, and Python execution, with safe defaults and OpenAI integration for automatic tool selection.-
- AlicenseNot gradedqualityDmaintenanceMCP tool server providing SQLite database access for AI agents.MIT