Skip to main content
Glama
README.md
# mcpme

A personal MCP server that exposes your CV so any MCP-compatible agent can answer questions about you.

![Demo](assets/demo.gif)

## Install

```bash
# Create a local virtual environment and install dependencies
uv venv
uv sync

# Or install globally as a tool
uv tool install .
```

## Usage

By default the bundled `cv.md` is used. Point to your own CV with an env var:

```bash
MCPME_CV_PATH=/path/to/your-cv.md mcpme
```

## Connect to Claude Code

To connect the server to a specific project, create a local settings file:

```bash
cat > .mcp.json << 'EOF'
{
  "mcpServers": {
    "mcpme": {
      "command": "mcpme",
      "env": {
        "MCPME_CV_PATH": "/path/to/your-cv.md"
      }
    }
  }
}
EOF
```

Or add it to your global `~/.claude/settings.json` to make it available everywhere.

## What it exposes

| Type | Name | Description |
|------|------|-------------|
| Tool | `read_cv` | Returns the full CV text |
| Resource | `cv://resume` | CV as an MCP resource |
| Prompt | `about_me` | Primed prompt for CV Q&A |

TDQS

A4.1/5.0

Scored across 1 tool

Disambiguation5/5

With only a single tool, there is no possibility of ambiguity or overlapping functionality. The tool's purpose is clearly distinct by default.

Naming Consistency5/5

The single tool name 'read_cv' uses a clear snake_case verb-object structure that is consistent and intuitive for its function.

Tool Count2/5

Having only one tool falls well below the typical 3-15 range and feels thin for a server purporting to represent a person's overall background and skills.

Completeness2/5

The domain of a personal assistant server would reasonably include additional capabilities like listing skills, providing contact details, or describing projects. Providing only a CV leaves significant gaps.

Maintenance

ActivityMaintained
ResponsivenessResponsive