---
icon: lucide/workflow
---

# Using Personal MCP

Personal MCP gives clients access to skills, prompts, and general documentation. Use the smallest piece of content that matches the task instead of loading the whole library.

## Connect

The HTTP endpoint is `/mcp`. For a local server on port `8765`, connect to:

```text
http://127.0.0.1:8765/mcp
```

Clients that launch servers as subprocesses can use:

```bash
uv run mcp-stdio
```

## Use A Skill

Skills are MCP resources. A client should:

1. browse the available `skill://<name>/SKILL.md` resources
2. choose one by its name and description
3. read the main `SKILL.md`
4. read its `_manifest` only when extra reference material is needed
5. load only the relevant supporting files

The guidance should then be checked against the code and conventions in the current workspace.

## Use A Prompt

Prompts are reusable workflows with named arguments. Browse the server's prompts, select one by its description, and supply the requested values when invoking it.

In VS Code, MCP prompts appear as chat slash commands. Resources can be opened from **MCP: Browse Resources** and attached as context when the active chat surface supports it.

## Tool Fallbacks

Some clients can call tools but cannot browse MCP resources or prompts directly. For those clients, the server exposes four read-only tools:

- `list_resources`
- `read_resource`
- `list_prompts`
- `get_prompt`

They provide access to the same underlying content. Clients with native resource and prompt support should use those native features.

## Example Request

```text
Browse the available Personal MCP skills, choose the best match for this task,
read its main SKILL.md, and load supporting files only if they are needed.
Apply the guidance to this repository rather than treating it as generated output.
```

For the exact resource and prompt formats, see the [content contracts](./contracts/index.md).