Connect skl over MCP - Skillsync Docs

skl mcp is an MCP server. Your client starts it when it needs it, so there's nothing to keep running.

skl plugin install sets this up for Claude Code, Codex and OpenCode. The steps below are for doing it by hand, or for another client.

Claude Code

claude mcp add --transport stdio skl -- skl mcp

Add --scope user for every project, or --scope project to share it through the repo's .mcp.json.

Codex

codex mcp add skl -- skl mcp

Or in ~/.codex/config.toml:

[mcp_servers.skl]
command = "skl"
args = ["mcp"]

OpenCode

In opencode.json:

{
  "mcp": {
    "skl": {
      "type": "local",
      "command": ["skl", "mcp"]
    }
  }
}

Cursor, Claude Desktop and others

{
  "mcpServers": {
    "skl": {
      "command": "skl",
      "args": ["mcp"]
    }
  }
}

Cursor reads .cursor/mcp.json in a project or ~/.cursor/mcp.json. Claude Desktop reads claude_desktop_config.json. Restart the client after you change it.

Tools

These need no account.

Tool	What it does
`list_sessions`	List recent sessions on this machine.
`search_sessions`	Find sessions that contain some text.
`read_session`	Read a session, or a range of its messages.
`auth_status`	Say whether you're signed in, and as whom.

These need you signed in.

Tool	What it does
`ask_sessions`	Answer a question from your sessions, with the ones it cites. Same as `skl search`.
`list_workspaces`	List your workspaces.
`list_synced_sessions`	List your synced sessions, or the ones shared into a workspace.
`read_synced_session`	Read a synced session.
`list_skills`	List skills you can install.
`get_skill`	Read a skill before installing it.
`install_skill`	Install a skill.
`upload_skill`	Publish a local skill.

ask_sessions needs what skl search needs, and isn't on Windows yet. skl mcp --no-ask leaves it out.

No tool syncs a session. That stays with skl sync, run by you.

If it doesn't connect

The client says spawn skl ENOENT. Give it the full path from which skl.
The Skillsync tools fail. Run skl whoami, then skl login.