# mcp-current-repo

> Use this tool when you need to scope GitHub tools to a specific repository without requiring filesystem access. It solves problems related to repository identification and access by utilizing MCP roots to carry the repo identity. This tool is ideal for use cases where repository-specific GitHub tool integration is required, providing a proof-of-concept MCP server solution.

Canonical page: https://skillsregistry.net/skills/wolfe-jam-mcp-current-repo  
JSON: https://api.skillsregistry.net/v1/skills/wolfe-jam-mcp-current-repo

## Description

A proof-of-concept MCP server that scopes GitHub tools to the current repository without filesystem access, using MCP roots to carry the repo identity.

## Trust

- **Trust score (0–1):** 0.70
- **Verification tier:** verified
- **Last scanned:** 2026-09-03

## Facts

- **Version:** 1.0.0
- **Skill type:** atomic
- **Execution layer:** mcp-remote
- **Runtime environment:** api
- **Category:** version-control
- **Updated:** 2026-09-03

## Source

- **Source listing:** [Glama](https://glama.ai/mcp/servers/x5ae53asl8)
- **Repository:** <https://github.com/Wolfe-Jam/mcp-current-repo>

## Use it

Resolve this record through the SkillsRegistry MCP server (no auth, read-only):

```
claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp
```

```json
{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "get_skill",
    "arguments": {
      "slug": "wolfe-jam-mcp-current-repo"
    }
  }
}
```

REST: `GET https://api.skillsregistry.net/v1/skills/wolfe-jam-mcp-current-repo` · pull for local use: `GET https://api.skillsregistry.net/v1/skills/wolfe-jam-mcp-current-repo/pull`

---
SkillsRegistry indexes agent skills from public registries and GitHub. Skills we have analysed are scanned with Circle-IR and scored on six dimensions; each listing states its scan coverage. More: https://skillsregistry.net/llms.txt