@bahirul/manta-work-mcp

Local stdio MCP bridge for Manta Gateway developer work tracking. The MCP client launches it inside the developer's project, so it can detect Git metadata and manage the work-session lifecycle without manual manta-work commands.

Requires Node.js 22 or newer so the MCP client can launch it through npx.

Configure

Add the server to an MCP-capable coding client:

{
  "command": "npx",
  "args": ["-y", "@bahirul/manta-work-mcp@latest"],
  "env": {
    "MANTA_GATEWAY_URL": "https://gateway.example.com",
    "MANTA_GATEWAY_API_KEY": "<developer-key>"
  }
}

npx downloads and caches the package automatically. The bridge starts a project session during MCP initialization, sends heartbeats every 60 seconds, exposes completion-reporting tools to the agent, and releases its client lease when the MCP client exits cleanly.

Multiple bridge processes using the same developer API key and project share one logical work session. Each process maintains an independent lease, so closing or losing one client does not close the project session while another client remains active. A lease becomes abandoned after 10 minutes without a heartbeat; the shared session becomes abandoned only after its final lease expires.

Set MANTA_MCP_URL instead of MANTA_GATEWAY_URL only when the MCP endpoint uses a custom URL.

Privacy

The bridge sends sanitized project identity and client-generated completion metadata, including optional aggregate LOC additions/deletions. Completion reports may also contain optional aggregate workflow metrics for the period since the previous report: outcome and task type, conversation and plan turn counts, plan-question counts, tool names with call/failure counts, validation check counts by type, and the skill name(s) the agent used for the completed work.

The local record_skill_applied tool records a skill only when it actually governs current work. Recorded skills remain pending across turns and failed completion-report attempts, are included in the next successful report, and are then removed from the pending window. A later report does not repeat a skill unless it is explicitly applied again. Skill versions are optional and should be omitted unless the client has a trustworthy version source. The skills input on report_work_complete remains supported for clients that report application at completion time.

The bridge does not infer skill persistence from earlier turns or discover arbitrary tools used outside this MCP server. Aggregate tool metrics therefore remain client-reported. It also does not send prompts, source files, diffs, file-level LOC, tool arguments or results, command contents, or API keys as work-report content. Git credentials and URL query parameters are removed locally before project metadata is sent. Workflow metrics are agent-reported best-effort data; gateway request, model, latency, and token metrics are derived separately where a request can be attributed to a work session without guessing.