# NousResearch/hermes-agent · Fix stdio MCP servers working directory behavior

## Open now

- Nothing open on GitHub.

These issues and pull requests address a bug where stdio MCP servers start in the Hermes process directory rather than the session's working directory. The changes aim to correct the default working directory used when spawning stdio servers.

## TL;DR

- 3 member(s): 0 open issue(s), 1 closed issue(s), 0 open PR(s), 1 merged PR(s), 1 PR(s) closed without merging.
- A fix was merged to main in PR #114849. Verify it addresses your case.
- **Recommended:** read PR #114849 (and any competing PRs below) before filing. Confirm the merged change covers your symptom.

## Maintainer resolution verdict

- Internal-tracker verdict over this cluster's issue members: `resolved` · deciding PR(s): `pr-114849`. This is distinct from the fix status above. Weigh it yourself.

## How this cluster was grouped

- Link evidence (`STRUCTURAL_SPANNING`): every member is connected by structural evidence: shared changed files, or a closing/superseded reference.
- Pairwise link density `0.67`: the share of member pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36. `1.00` means every pair is linked.

## Closed / duplicate issues

- #113888: stdio MCP servers spawn in the Hermes process directory instead of the session working directory

## Prior & competing PRs

- **#114849: fix(mcp): stdio servers start in the session working directory, not the Hermes launch dir (#113888, salvage #113890)**. merged to main · fix tier `verified`
  - maintainer direction: category `merged`
  - files: `acp_adapter/server.py`, `tests/acp_adapter/test_server.py`, `tests/tools/test_mcp_tool.py`, `tools/mcp_tool_transport.py`, `website/docs/user-guide/features/mcp.md`
- **#113890: fix(mcp): stdio servers default to the session working directory**. closed without merge
  - maintainer direction: category `merged_via`; implication `superseded`; refs `787b6ebd3a7d`, `#114849`, `#113888`, `#113890`

## Fix status

- Merged to main in PR #114849 (cited above). No release data is tracked. Verify downstream.
- Fix last verified (merged) `2026-09-18`.
