Move Kan MCP OpenClaw registration from systemd drop-in to mcporter/Infisical #131

Closed
opened 2026-05-09 01:17:52 +02:00 by codex · 2 comments
Collaborator

Context:

Kan MCP is working end-to-end now:
Signal -> Iskra/OpenClaw -> Kan MCP -> AI Inbox create/move -> activity/audit readback.

Current temporary state:

  • OpenClaw sees Kan MCP through a user systemd drop-in on VPS1000:
    /home/openclaw/.config/systemd/user/openclaw-gateway.service.d/kan-mcp.conf
  • The drop-in sets:
    • OPENCLAW_KAN_MCP_ENABLED=true
    • OPENCLAW_KAN_MCP_URL=https://kan.pdurlej.com/mcp
  • This is intentionally working drift, not the desired platform source of truth.
  • Infisical machine identity currently cannot create these new secrets (403 create on secrets).
  • mcporter list kan --schema should eventually work directly instead of relying on ad-hoc URL/runtime config.

Desired state:

  • Kan MCP registration is managed by platform config / mcporter / Infisical.
  • OpenClaw renderer gets Kan MCP config from the canonical platform path.
  • No live-only systemd drop-in is needed for Kan MCP.
  • mcporter list kan --schema works from the OpenClaw host.
  • Keep Kan write path tailnet-restricted and token-backed; do not expose Kan agent token to OpenClaw if the RS2000 Kan MCP bridge can hold it server-side.

Acceptance:

  • Remove or supersede the kan-mcp.conf drop-in safely.
  • Rendered /run/user/1000/openclaw/openclaw.json still contains mcp.servers.kan.
  • mcporter list kan --schema returns Kan tools/schema.
  • Signal -> Iskra -> Kan MCP create/move/readback smoke still passes.

Note:
This is intentionally not blocking the current Kan value work. The live drop-in stays until the platform migration is done.

Context: Kan MCP is working end-to-end now: Signal -> Iskra/OpenClaw -> Kan MCP -> AI Inbox create/move -> activity/audit readback. Current temporary state: - OpenClaw sees Kan MCP through a user systemd drop-in on VPS1000: `/home/openclaw/.config/systemd/user/openclaw-gateway.service.d/kan-mcp.conf` - The drop-in sets: - `OPENCLAW_KAN_MCP_ENABLED=true` - `OPENCLAW_KAN_MCP_URL=https://kan.pdurlej.com/mcp` - This is intentionally working drift, not the desired platform source of truth. - Infisical machine identity currently cannot create these new secrets (`403 create on secrets`). - `mcporter list kan --schema` should eventually work directly instead of relying on ad-hoc URL/runtime config. Desired state: - Kan MCP registration is managed by platform config / mcporter / Infisical. - OpenClaw renderer gets Kan MCP config from the canonical platform path. - No live-only systemd drop-in is needed for Kan MCP. - `mcporter list kan --schema` works from the OpenClaw host. - Keep Kan write path tailnet-restricted and token-backed; do not expose Kan agent token to OpenClaw if the RS2000 Kan MCP bridge can hold it server-side. Acceptance: - Remove or supersede the `kan-mcp.conf` drop-in safely. - Rendered `/run/user/1000/openclaw/openclaw.json` still contains `mcp.servers.kan`. - `mcporter list kan --schema` returns Kan tools/schema. - Signal -> Iskra -> Kan MCP create/move/readback smoke still passes. Note: This is intentionally not blocking the current Kan value work. The live drop-in stays until the platform migration is done.
Author
Collaborator

M03 triage result: moved out of Secrets closeout.

Reason: W4 already classified Kan MCP as a VPS1000/OpenClaw product/config migration, not a generic M03 blocker. This should be handled in the Persona/OpenClaw lane with Iskra context and without ad-hoc secret writes.

Disposition: move to M08. Keep as not-ready/security-sensitive until the concrete OpenClaw/Infisical path is selected and reviewed. No runtime mutation was performed.

M03 triage result: moved out of Secrets closeout. Reason: W4 already classified Kan MCP as a VPS1000/OpenClaw product/config migration, not a generic M03 blocker. This should be handled in the Persona/OpenClaw lane with Iskra context and without ad-hoc secret writes. Disposition: move to M08. Keep as not-ready/security-sensitive until the concrete OpenClaw/Infisical path is selected and reviewed. No runtime mutation was performed.
Collaborator

Org (claude): agent/codex. Objective: move Kan MCP OpenClaw registration from the systemd drop-in to mcporter + Infisical (per title). Sources: current systemd drop-in, mcporter config, Infisical secret path. Runtime ops on VPS1000 → operator-gated apply. Done: Kan MCP registered via mcporter, secret from Infisical, systemd drop-in removed.

**Org (claude): `agent/codex`.** Objective: move Kan MCP OpenClaw registration from the systemd drop-in to mcporter + Infisical (per title). Sources: current systemd drop-in, mcporter config, Infisical secret path. Runtime ops on VPS1000 → operator-gated apply. Done: Kan MCP registered via mcporter, secret from Infisical, systemd drop-in removed.
Sign in to join this conversation.
No labels
W6d-automerge-calibration
agent/claude-code
agent/codex
agent/hermes
agent/iskra
agent/ollama
agent/patchwarden
automerge-candidate
class/security-sensitive
cutover-gate
dependency/blocked
dependency/blocks-others
dependency/cross-repo
dependency/needs-confirmation
domain:agents
domain:ci
domain:docs
domain:forgejo
domain:infra
domain:memory
domain:runtime
domain:signal
domain:ux
flow/architecture
flow/blocked
flow/deployed
flow/done
flow/implementation
flow/intake
flow/maintained
flow/observed
flow/ready
flow/refining
flow/retired
flow/review
iterating
judge/codex-candidate
judge/hermes-candidate
judge/low-confidence
judge/needs-refinement
judge/operator-needed
judge/p0
judge/p1
judge/p2
judge/p3
judge/park
judge/patchwarden-candidate
judge/stale-priority
kind/adr
kind/bug
kind/chore
kind/feature
kind/infra
kind/ops
kind/refactor
kind/research
large-impact
merge/auto
merge/manual
merge/manual-dependency-conflict
merge/manual-failing-tests
merge/manual-merge-conflict
merge/manual-missing-review
merge/manual-operator-preference
merge/manual-red-zone
merge/manual-security-sensitive
merge/manual-unclear-scope
merge/manual-unknown
meta
mode:operator-only
mode:patchwarden-iskra-approved
mode:safe-auto
needs-operator-decision
needs-triage
not-ready
observed/erroring
observed/needs-followup
observed/pending
observed/retire-candidate
observed/unused
observed/used
operator-emotional
owner-attention
phase/02
phase/03
priority:p0
priority:p1
priority:p2
priority:p3
proposed
ready-for-agent
ready-for-operator
recovery
review:claude-reviewed
review:codex-reviewed
review:dziadek-reviewed
review:needs-human
risk/exposure
risk/process
risk/product
risk/runtime
safety:external-write
safety:no-prod-mutation
safety:prod-impact
safety:secret-touch
size/large
size/medium
size/small
size/tiny
size/unknown
source/adr
source/agent-generated
source/manual
source/operator-chat
source/voice-note
status:blocked
status:codex-ready
status:merged:pending-evidence
status:needs-evidence
status:operator-needed
status:parked
tier/full
tier/lite
tier/stacked
tier:0-platform-substrate
tier:1-iskra-value-layer
tier:2-tools-products-modules
type:bug
type:chore
type:docs
type:feat
type:policy
type:research
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
pdurlej/platform#131
No description provided.