Skip to content

docs: state that MCP project paths must be absolute #76

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tupe12334 merged 1 commit into from
Oct 19, 2026
Merged

docs: state that MCP project paths must be absolute #76

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions .changeset/mcp-absolute-project-path.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
---
"centy-docs": patch
---

Document that MCP `projectPath` and other path arguments must be absolute. Relative paths are rejected with `INVALID_PATH` since centy-daemon 0.16.0.
1 change: 1 addition & 0 deletions docs/llm-integration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -158,6 +158,7 @@ Centy daemon 0.15.1 and later serves a built-in MCP endpoint on loopback. No sep
- **Daemon:** must be running for MCP to work.
- **Tools:** each daemon RPC is a tool named `centy_v1_CentyDaemon_<Method>`.
- **Address:** change it with `--mcp-addr` or `CENTY_MCP_ADDR`. It must stay a loopback address.
- **Paths:** `projectPath` and any other path argument must be an absolute path. Since centy-daemon 0.16.0, relative paths are rejected with `INVALID_PATH`.

The `centy` plugin from the centy-daemon marketplace configures the URL for you. To configure it yourself, add this to `.mcp.json`:

Expand Down
Loading