# personal-mcp MCP Usage

This repository is resource-first.

- Canonical skill guidance lives in `src/personal_mcp/docs/skills/<skill-id>/SKILL.md`.
- Skills are exposed through FastMCP's native `skill://` resource family.
- Prompts are exposed through native MCP prompt operations (`prompts/list`, `prompts/get`).
- General documentation pages are exposed through `resource://docs/{path*}`.
- The server intentionally does not provide compatibility tool projections for resources or prompts.

When a task appears to match a documented implementation pattern in `personal-mcp`, use this sequence:

1. Prefer an already attached native skill resource.
2. Otherwise browse native MCP resources and compare available `skill://<name>/SKILL.md` descriptions.
3. Read the best matching main skill file, or at most 2 candidate main files.
4. Read `skill://<name>/_manifest` only when supporting material may be useful.
5. Fetch only the relevant supporting paths from that manifest.
6. Reconcile skill guidance with the actual repository code before proposing or making changes.

Preferred MCP resource order:

1. `skill://<name>/SKILL.md`
2. `skill://<name>/_manifest` when needed
3. `skill://<name>/<supporting-path>` for selected supporting files

Selection rules:

- Prefer the closest `name` and `description` match.
- Keep context bounded; do not load many skill documents speculatively.
- If confidence is low after reading at most two main files, ask one clarifying question before loading more context.

Repository-specific guidance:

- For tasks about adding or modifying a skill, use `skill://copilot-customization/SKILL.md` when relevant.
- Keep skills provider-native; do not add tool projections for resource or prompt access.


## Python Checks

After changes run these commands to confirm functionality. Resolve any errors

```python
uv run ruff check .
```

```python
uv run ty check
```

```python
uv run pytest
```