forgejo_admin/pal-e-mcp
1
0
Fork 0
Code Issues 4 Pull requests Projects Releases Packages Wiki Activity Actions

Rename pal-e-docs-mcp repo to pal-e-mcp + update SDK imports #50

New issue
Closed
opened 2026-03-27 04:54:12 +00:00 by forgejo_admin · 2 comments
forgejo_admin commented 2026-03-27 04:54:12 +00:00
Owner
Copy link

Type

Feature

Lineage

Part of repo rename initiative. Depends on pal-e-docs-sdk → pal-e-sdk rename completing first (import paths change).

Repo

forgejo_admin/pal-e-docs-mcp → forgejo_admin/pal-e-mcp

User Story

As the platform
I want the MCP server repo named pal-e-mcp instead of pal-e-docs-mcp
So that the naming is consistent with the project naming convention

Context

The MCP server provides 36+ tools for AI agents to interact with the pal-e-docs knowledge platform. The repo name should be pal-e-mcp. The MCP server KEY in settings.json stays pal-e-docs because that's the project name — this means zero changes to hook tool matchers (mcp__pal-e-docs__* prefix stays).

The main code change is updating SDK import paths from pal_e_docs_sdk to pal_e_sdk (after the SDK rename completes).

CRITICAL: ~/.mcp.json has hardcoded paths (/home/ldraney/pal-e-docs-mcp and module pal_e_docs_mcp). This must be updated atomically with the directory rename or ALL agent sessions lose MCP tools.

File Targets

Forgejo API rename:

  • PATCH /api/v1/repos/forgejo_admin/pal-e-docs-mcp with {"name": "pal-e-mcp"}

Files to modify in THIS repo:

  • pyproject.toml — update ALL fields: package name, script entry point, wheel path, uv source, SDK dependency name (pal_e_docs_sdk → pal_e_sdk)
  • All from pal_e_docs_sdk import statements → from pal_e_sdk import
  • src/pal_e_docs_mcp/ → src/pal_e_mcp/ — rename package directory (if applicable)
  • .woodpecker.yaml (or .yml) — verify image paths
  • tests/ — update import paths

CRITICAL file outside this repo (must update atomically):

  • ~/.mcp.json — update command path from /home/ldraney/pal-e-docs-mcp to /home/ldraney/pal-e-mcp, update module name pal_e_docs_mcp → pal_e_mcp

Files that do NOT exist (confirmed by review):

  • CLAUDE.md — does not exist in this repo, do not create

Files the agent should NOT touch:

  • settings.json MCP server key — stays pal-e-docs (project name)
  • Hook tool matchers — mcp__pal-e-docs__* prefix stays
  • Agent disallowedTools lists — tool prefix stays

Acceptance Criteria

  • Forgejo repo accessible at forgejo_admin/pal-e-mcp
  • MCP server starts and all 36+ tools are available
  • Tool prefix remains mcp__pal-e-docs__* (unchanged)
  • SDK imports use new pal_e_sdk package name
  • ~/.mcp.json points to new path and module
  • CI pipeline works on renamed repo

Test Expectations

  • MCP server starts without import errors
  • pytest passes (if tests exist)
  • Claude Code session can use mcp__pal-e-docs__get_note after restart
  • Run command: source .venv/bin/activate && python -c "import pal_e_mcp; print('OK')"

Constraints

  • MCP server key in settings.json MUST stay pal-e-docs
  • SDK rename must complete first (import paths depend on it)
  • ~/.mcp.json update must be atomic with directory rename — if either is done without the other, all sessions lose MCP tools
  • MCP process cache means session restart is needed after this change

Checklist

  • Repo renamed on Forgejo
  • Package renamed
  • SDK imports updated
  • ~/.mcp.json updated
  • MCP server starts successfully
  • No unrelated changes

Related

  • forgejo_admin/pal-e-docs-sdk#38 — must complete first
  • phase-pal-e-docs-repo-renames — deferred phase this replaces
### Type Feature ### Lineage Part of repo rename initiative. Depends on pal-e-docs-sdk → pal-e-sdk rename completing first (import paths change). ### Repo `forgejo_admin/pal-e-docs-mcp` → `forgejo_admin/pal-e-mcp` ### User Story As the platform I want the MCP server repo named pal-e-mcp instead of pal-e-docs-mcp So that the naming is consistent with the project naming convention ### Context The MCP server provides 36+ tools for AI agents to interact with the pal-e-docs knowledge platform. The repo name should be pal-e-mcp. The MCP server KEY in settings.json stays `pal-e-docs` because that's the project name — this means zero changes to hook tool matchers (`mcp__pal-e-docs__*` prefix stays). The main code change is updating SDK import paths from `pal_e_docs_sdk` to `pal_e_sdk` (after the SDK rename completes). CRITICAL: `~/.mcp.json` has hardcoded paths (`/home/ldraney/pal-e-docs-mcp` and module `pal_e_docs_mcp`). This must be updated atomically with the directory rename or ALL agent sessions lose MCP tools. ### File Targets Forgejo API rename: - `PATCH /api/v1/repos/forgejo_admin/pal-e-docs-mcp` with `{"name": "pal-e-mcp"}` Files to modify in THIS repo: - `pyproject.toml` — update ALL fields: package name, script entry point, wheel path, uv source, SDK dependency name (`pal_e_docs_sdk` → `pal_e_sdk`) - All `from pal_e_docs_sdk import` statements → `from pal_e_sdk import` - `src/pal_e_docs_mcp/` → `src/pal_e_mcp/` — rename package directory (if applicable) - `.woodpecker.yaml` (or `.yml`) — verify image paths - `tests/` — update import paths CRITICAL file outside this repo (must update atomically): - `~/.mcp.json` — update `command` path from `/home/ldraney/pal-e-docs-mcp` to `/home/ldraney/pal-e-mcp`, update module name `pal_e_docs_mcp` → `pal_e_mcp` Files that do NOT exist (confirmed by review): - `CLAUDE.md` — does not exist in this repo, do not create Files the agent should NOT touch: - `settings.json` MCP server key — stays `pal-e-docs` (project name) - Hook tool matchers — `mcp__pal-e-docs__*` prefix stays - Agent `disallowedTools` lists — tool prefix stays ### Acceptance Criteria - [ ] Forgejo repo accessible at `forgejo_admin/pal-e-mcp` - [ ] MCP server starts and all 36+ tools are available - [ ] Tool prefix remains `mcp__pal-e-docs__*` (unchanged) - [ ] SDK imports use new `pal_e_sdk` package name - [ ] `~/.mcp.json` points to new path and module - [ ] CI pipeline works on renamed repo ### Test Expectations - [ ] MCP server starts without import errors - [ ] `pytest` passes (if tests exist) - [ ] Claude Code session can use `mcp__pal-e-docs__get_note` after restart - Run command: `source .venv/bin/activate && python -c "import pal_e_mcp; print('OK')"` ### Constraints - MCP server key in settings.json MUST stay `pal-e-docs` - SDK rename must complete first (import paths depend on it) - `~/.mcp.json` update must be atomic with directory rename — if either is done without the other, all sessions lose MCP tools - MCP process cache means session restart is needed after this change ### Checklist - [ ] Repo renamed on Forgejo - [ ] Package renamed - [ ] SDK imports updated - [ ] `~/.mcp.json` updated - [ ] MCP server starts successfully - [ ] No unrelated changes ### Related - `forgejo_admin/pal-e-docs-sdk#38` — must complete first - `phase-pal-e-docs-repo-renames` — deferred phase this replaces
forgejo_admin commented 2026-03-27 05:00:36 +00:00
Author
Owner
Copy link

Scope Review: NEEDS_REFINEMENT

Review note: review-441-2026-03-26

Well-structured issue with complete template and traceability. Three gaps found:

  • CLAUDE.md listed in file targets but does not exist in this repo -- remove from targets or create first
  • ~/.mcp.json missing from file targets -- contains hardcoded path /home/ldraney/pal-e-docs-mcp and module pal_e_docs_mcp. MCP server breaks immediately on directory rename if this isn't updated in the same session. Clarify ownership (this ticket vs #442)
  • pyproject.toml scope understated -- file targets only mention SDK dependency, but package name (line 6), script entry point (line 18), wheel path (line 28), and uv source (line 42) all need renaming too

Additionally: dependency on SDK rename (pal-e-docs-sdk#38, board item #440) is in backlog. This ticket cannot move to next_up until that dependency progresses.

## Scope Review: NEEDS_REFINEMENT Review note: `review-441-2026-03-26` Well-structured issue with complete template and traceability. Three gaps found: - **CLAUDE.md listed in file targets but does not exist** in this repo -- remove from targets or create first - **~/.mcp.json missing from file targets** -- contains hardcoded path `/home/ldraney/pal-e-docs-mcp` and module `pal_e_docs_mcp`. MCP server breaks immediately on directory rename if this isn't updated in the same session. Clarify ownership (this ticket vs #442) - **pyproject.toml scope understated** -- file targets only mention SDK dependency, but package name (line 6), script entry point (line 18), wheel path (line 28), and uv source (line 42) all need renaming too Additionally: dependency on SDK rename (pal-e-docs-sdk#38, board item #440) is in backlog. This ticket cannot move to next_up until that dependency progresses.
forgejo_admin commented 2026-03-27 05:14:30 +00:00
Author
Owner
Copy link

Scope Review: READY

Review note: review-441-2026-03-26 (updated)

Re-review after refinements. All three issues from the initial review are resolved:

  1. CLAUDE.md -- now correctly listed under "Files that do NOT exist" with "do not create" instruction
  2. ~/.mcp.json -- added as CRITICAL target with atomic update requirement, added to Context, Acceptance Criteria, Constraints, and Checklist
  3. pyproject.toml -- scope expanded to all 5 fields (package name, script entry point, wheel path, uv source, SDK dep)

Two minor nits noted (README.md and uv.lock not in file targets) but these are standard rename artifacts, not blocking.

Dependency note: Board item #440 (SDK rename, pal-e-docs-sdk#38) is still in backlog. This ticket cannot move to next_up until that dependency completes.

## Scope Review: READY Review note: `review-441-2026-03-26` (updated) Re-review after refinements. All three issues from the initial review are resolved: 1. **CLAUDE.md** -- now correctly listed under "Files that do NOT exist" with "do not create" instruction 2. **~/.mcp.json** -- added as CRITICAL target with atomic update requirement, added to Context, Acceptance Criteria, Constraints, and Checklist 3. **pyproject.toml** -- scope expanded to all 5 fields (package name, script entry point, wheel path, uv source, SDK dep) Two minor nits noted (README.md and uv.lock not in file targets) but these are standard rename artifacts, not blocking. **Dependency note:** Board item #440 (SDK rename, pal-e-docs-sdk#38) is still in backlog. This ticket cannot move to next_up until that dependency completes.
forgejo_admin 2026-03-27 06:03:00 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
No results found.
Labels
Clear labels   
domain:backend

   
domain:devops

   
domain:frontend

   
status:approved

QA passed, awaiting merge approval

  
status:in-progress

Dev agent is actively working

  
status:needs-fix

QA found issues, back to dev

  
status:qa

PR submitted, awaiting QA review

  
type:bug

Bug fix

  
type:devops

Infrastructure/CI/config work

  
type:feature

New functionality

No labels
domain:backend
domain:devops
domain:frontend
status:approved
status:in-progress
status:needs-fix
status:qa
type:bug
type:devops
type:feature
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
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
forgejo_admin/pal-e-mcp#50
No description provided.