Developer Tools
gethaki.space
Manages a project's persistent memory, allowing recall, capture, inspection, forgetting, and correction of project facts and conventions.
ENDPOINT 1
https://api.gethaki.space/mcp
MCP server metadata
- Name
- haki
Project long-term memory. Call haki_context before planning or editing code, haki_capture at the end of a task for decisions, conventions and resolved errors. Only memorize durable content, never secrets. Call haki_correct when the user reports that a fact recalled by haki_context is wrong.
Known tools 5
haki_contextRecall the project's memory (decisions, conventions, preferences) relevant to a task.
Inferred read-onlyhaki_captureMemorize a durable project fact: technical decision, convention, resolved error.
Inferred read-onlyhaki_inspectInspect the trace of a haki_context call: which facts were included, excluded or blocked, and why (reason_code).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.haki]
url = "https://api.gethaki.space/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"haki": {
"type": "http",
"url": "https://api.gethaki.space/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: haki
Remote MCP URL: https://api.gethaki.space/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"haki": {
"url": "https://api.gethaki.space/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"haki": {
"type": "http",
"url": "https://api.gethaki.space/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "haki",
"transport": "streamable-http",
"url": "https://api.gethaki.space/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.