Connect an MCP client
Connect a ready-made MCP client — like Claude Desktop (Cowork) or ChatGPT — straight to your SkillRepo library with a custom connector. No CLI, no terminal, no keys to copy. Once connected, the assistant can discover and read your skills on demand, in any chat or saved routine.
Setting up a local IDE instead (Claude Code, Cursor, Windsurf, VS Code)? Use the CLI connection flow — it writes skills to disk so your agent loads them locally. Building your own MCP integration? See the MCP Reference.
What you get
The assistant gains four read-only tools to discover and read your library. Ask it to list your skills or to use one, and it fetches that skill over the connection and works through its steps — including inside saved routines.
What it isn’t
A connector does not install skills as files or add clickable /-commands. That’s the CLI (for IDEs) or a vendor plugin. The connector is the tools surface: the assistant pulls a skill in when you ask for it.
Connect Claude Desktop
Claude Desktop (including Cowork) connects to SkillRepo as a custom connector. The whole flow lives in the app’s settings — you never touch a terminal or an access key.
- Open Claude Desktop and go to Settings → Connectors (also reachable via Customize → Connectors).
- Click Add custom connector (the
+button). - Paste the SkillRepo MCP URL and confirm:
https://mcp.skillrepo.dev - Approve the SkillRepo consent screen, then choose which account’s library to expose. (SkillRepo is its own OAuth 2.1 server — the client registers itself; you just approve.)
- SkillRepo now appears under Connectors with four read-only tools —
get_skill,get_skill_content,get_skill_file, andlist_library. Set them to Always allow if you don’t want a prompt each time. - Try it: ask “List my SkillRepo skills” or “Use my
new-projectskill to set up project X.” The assistant fetches the skill over the connection and follows it — this works inside saved routines too.
Availability
Custom connectors using remote MCP are available on every Claude plan — Free, Pro, Max, Team, and Enterprise. Free is limited to one custom connector. On Team and Enterprise an Owner adds the connector, then each member connects and enables it individually. See Anthropic’s custom connectors guide.
Other MCP clients
Any client that supports custom MCP connectors over the standard authorization flow — ChatGPT’s custom MCP integration and others — connects to the same endpoint. Paste the URL and complete the consent flow; there is no separate key to manage.
https://mcp.skillrepo.devSkillRepo implements OAuth 2.1 with dynamic client registration, so spec-compliant clients register and authorize themselves. If your client expects a hand-issued access key in a header instead, or you want the full tool schemas and rate limits, see the MCP Reference.
What you can do once connected
- Discover — “What skills are in my SkillRepo library?” (
list_library). - Use a skill — “Use my
new-projectskill to scaffold this repo.” The assistant loads the SKILL.md and follows it (get_skill_content). - Pull in a supporting file — when a skill references a script or template, the assistant fetches it on demand (
get_skill_file). - Build a routine that calls a skill, so a recurring task always runs against the latest published version.
The connection is read-only and scoped to the account you approved. Publishing still happens through the dashboard or the GitHub App sync — never over the connector.
Next steps
Need an account and a library first? Start with Getting Started. Setting up a local IDE? Use the Connections guide.