Skip to content
Docs: MCP server

In your repos

MCP server

Let agents browse the library, add skills to a repo and propose edits from inside a session.

On this page

Skillify has an MCP server at https://skillify.yogan.dev/mcp (streamable HTTP). Agents authenticate with your personal token and act as you, with one limit: they can propose changes to skills but never approve them.

Connect

Create a token in Settings → API tokens. A read token can browse; adding skills to repos and proposing changes needs a write token. Then add the server to your agent:

Terminalshell
claude mcp add --transport http skillify https://skillify.yogan.dev/mcp --header "Authorization: Bearer $SKILLIFY_TOKEN"

Add --scope project to write it to the repo’s .mcp.json instead (the token stays in your environment).

~/.codex/config.tomltoml
[mcp_servers.skillify]
url = "https://skillify.yogan.dev/mcp"
bearer_token_env_var = "SKILLIFY_TOKEN"
.cursor/mcp.jsonjson
{
  "mcpServers": {
    "skillify": {
      "url": "https://skillify.yogan.dev/mcp",
      "headers": { "Authorization": "Bearer ${env:SKILLIFY_TOKEN}" }
    }
  }
}

Tools

Tools
ToolTokenWhat it does
list_skillsReadSearches the library: names, descriptions, versions, repo counts and recent uses.
get_skillReadA skill’s latest files and the repos that use it. Read it before proposing a change.
list_reposReadRegistered repos with skill counts, usage and when each last reported.
get_repoReadA repo’s skills with version, pin, overlay and drift, plus its AGENTS.md notes.
lint_skillReadChecks a skill’s files without saving and returns the findings.
list_proposalsReadOpen proposals, or decided ones.
get_install_commandReadA one-hour install command for a repo.
add_skill_to_repoWriteAssigns a skill to a repo, optionally pinned and with an overlay.
remove_skill_from_repoWriteStops installing a skill in a repo; the next sync removes it.
set_repo_overlayWriteSets or clears a repo’s notes for one skill.
propose_skill_changeWriteOpens a proposal with new file contents. A person reviews it.

Good prompts

  • “Which skills does acme/payments-api have, and is it behind?”
  • “Add the review skill to this repo and tell it we use pnpm, not npm.”
  • “The tdd skill keeps telling me to use Jest. Propose a change that says to use the repo’s test runner.”

After an agent changes a repo's skills, run node .skillify/cli.mjs sync to write them.

The REST API

The same operations are under https://skillify.yogan.dev/api/v1 with Authorization: Bearer sk_…: /skills, /repos, /repos/<owner>/<name>/bundle, /proposals and /me. The CLI uses it.