MCP Registry
Use the GetSkillary MCP registry
Local AI agents can connect to the GetSkillary MCP endpoint to search public skills, inspect details, request related packages, retrieve manual download links, and record aggregate usage events.
Recommended agent flow
Ask the agent to search for the work you need done, such as markdown writing workflow.
Have the agent compare summaries, use cases, package size, tags, and manual download links.
Choose a package yourself, read SKILL.md, then install it in your local skills directory.
Endpoint
https://mcp.getskillary.com/mcp
Client configuration
Add the remote server URL in an MCP-compatible client that supports HTTP MCP servers.
{
"mcpServers": {
"getskillary": {
"url": "https://mcp.getskillary.com/mcp"
}
}
}
Available tools
search_skills: search public skill records by query, category, or tag.get_skill_detail: inspect one public skill record before downloading.recommend_skills: find related skills by slug, query, or category.get_download_url: return the manual zip download URL for a public skill.get_install_guide: return manual installation guidance for a selected skill.record_usage: record an aggregate usage event after the user chooses to proceed.
Example request
{
"jsonrpc": "2.0",
"id": 1,
"method": "tools/call",
"params": {
"name": "search_skills",
"arguments": {
"query": "markdown writing workflow",
"limit": 5
}
}
}
Operation boundary
The MCP registry does not install files, modify local configuration, expose quarantined skills, or publish private analytics views. Users should download packages manually and read SKILL.md before enabling a skill in a local agent environment.
Discovery files
AI crawlers and local tooling can also use llms.txt and llms-full.txt to understand the public catalog without reading internal review data.