Skill-to-MCP
Converts AI Skills (following Claude Skills format) into MCP server resources, enabling LLM applications to discover, access, and utilize self-contained skill directories through the Model Context Protocol. Provides tools to list available skills, retrieve skill details and content, and read supporting files with security protections.
README
Skill-to-MCP
Convert AI Skills (following Claude Skills format) into MCP server resources, making them accessible through the Model Context Protocol.
Part of BioContextAI - A community-driven initiative connecting agentic AI with biomedical resources through standardized MCP servers. While this package is domain-agnostic and can be used for any skill collection, it was developed to support the biomedical research community.
Overview
This MCP server exposes Claude Skills as resources that can be accessed by LLM applications through the Model Context Protocol. Skills are self-contained directories containing a SKILL.md file with YAML frontmatter, along with supporting files like scripts, references, and examples.
Features
- Automatic skill discovery: Recursively finds all 
SKILL.mdfiles in theskills/directory - Frontmatter parsing: Extracts skill metadata (name, description) from YAML frontmatter
 - Three core tools:
get_available_skills: Lists all available skills with descriptionsget_skill_details: Returns SKILL.md content and file listing for a specific skillget_skill_related_file: Reads any file within a skill directory (with directory traversal protection)
 - Security: Path validation prevents access outside skill directories
 
Getting Started
Please refer to the documentation for comprehensive guides, or jump to:
- Configuration - Set up your skills directory
 - Usage - Learn about the three core tools
 - Creating Skills - Build your own skills
 - Installation - Multiple installation options
 
Quick Links
- Documentation: skill-to-mcp.readthedocs.io
 - BioContextAI Registry: biocontext.ai/registry
 - API Reference: API documentation
 - Source Code: GitHub
 - Issue Tracker: GitHub Issues
 
Configuration
The MCP server requires a skills directory to be specified. This allows you to:
- Install the package separately from your skills
 - Edit skills without modifying the package
 - Use different skill collections for different projects
 
Set the skills directory using either:
- Command-line option: 
--skills-dir /path/to/skills - Environment variable: 
SKILLS_DIR=/path/to/skills 
Example Configuration for MCP Clients
{
  "mcpServers": {
    "skill-to-mcp": {
      "command": "uvx",
      "args": ["skill_to_mcp", "--skills-dir", "/path/to/your/skills"],
      "env": {
        "UV_PYTHON": "3.12"
      }
    }
  }
}
Or using environment variables:
{
  "mcpServers": {
    "skill-to-mcp": {
      "command": "uvx",
      "args": ["skill_to_mcp"],
      "env": {
        "UV_PYTHON": "3.12",
        "SKILLS_DIR": "/path/to/your/skills"
      }
    }
  }
}
Usage
Once configured in your MCP client, the server provides three tools:
get_available_skills
Returns a list of all available skills with metadata:
[
  {
    "name": "single-cell-rna-qc",
    "description": "Performs quality control on single-cell RNA-seq data...",
    "path": "/path/to/skills/single-cell-rna-qc"
  }
]
get_skill_details
Returns the full SKILL.md content and list of files for a specific skill:
{
  "skill_content": "---\nname: single-cell-rna-qc\n...",
  "files": ["SKILL.md", "scripts/qc_analysis.py", "references/guidelines.md"]
}
The return_type parameter controls what data is returned:
"content": Returns only the SKILL.md content as text"file_path": Returns only the absolute path to SKILL.md"both"(default): Returns both content and file path in a dict
get_skill_related_file
Reads a specific file within a skill directory:
get_skill_related_file(
    skill_name="single-cell-rna-qc",
    relative_path="scripts/qc_analysis.py",
    return_type="content"  # "content", "file_path", or "both" (default)
)
Example Configurations
Claude Desktop Configuration
Add to your claude_desktop_config.json:
{
  "mcpServers": {
    "biomedical-skills": {
      "command": "uvx",
      "args": [
        "skill_to_mcp",
        "--skills-dir",
        "/Users/yourname/biomedical-skills"
      ],
      "env": {
        "UV_PYTHON": "3.12"
      }
    }
  }
}
Multiple Skill Collections
You can run multiple instances with different skill directories:
{
  "mcpServers": {
    "biomedical-skills": {
      "command": "uvx",
      "args": ["skill_to_mcp", "--skills-dir", "/path/to/biomedical-skills"]
    },
    "data-science-skills": {
      "command": "uvx",
      "args": ["skill_to_mcp", "--skills-dir", "/path/to/data-science-skills"]
    }
  }
}
Creating Skills
Skills should be placed in your configured skills directory. Each skill must:
- Have its own subdirectory
 - Contain a 
SKILL.mdfile with YAML frontmatter - Follow the frontmatter format:
 
---
name: my-skill-name
description: Brief description of what this skill does and when to use it
---
# Skill Content
Instructions and documentation go here...
Skill Naming Requirements
- Use lowercase letters, numbers, and hyphens only
 - Maximum 64 characters
 - No XML tags or reserved words
 
See the included example skills/single-cell-rna-qc/SKILL.md for a complete reference.
Example Skills Directory Structure
my-skills/
├── skill-1/
│   ├── SKILL.md
│   ├── scripts/
│   └── references/
├── skill-2/
│   ├── SKILL.md
│   └── data/
└── skill-3/
    └── SKILL.md
Installation
You need to have Python 3.11 or newer installed on your system. If you don't have Python installed, we recommend installing uv.
There are several alternative options to install skill-to-mcp:
- Use 
uvxto run it immediately (requires SKILLS_DIR environment variable): 
SKILLS_DIR=/path/to/skills uvx skill_to_mcp
Or with the command-line option:
uvx skill_to_mcp --skills-dir /path/to/skills
- Include it in various MCP clients that support the 
mcp.jsonstandard: 
{
  "mcpServers": {
    "skill-to-mcp": {
      "command": "uvx",
      "args": ["skill_to_mcp", "--skills-dir", "/path/to/your/skills"],
      "env": {
        "UV_PYTHON": "3.12"
      }
    }
  }
}
- Install it through 
pip: 
pip install --user skill_to_mcp
- Install the latest development version:
 
pip install git+https://github.com/biocontext-ai/skill-to-mcp.git@main
Deployment Options
Local Development
For development and testing:
# Using uvx (recommended)
SKILLS_DIR=/path/to/skills uvx skill_to_mcp
# Using pip
pip install skill_to_mcp
skill_to_mcp --skills-dir /path/to/skills
Production Deployment
For production environments with HTTP transport:
export MCP_ENVIRONMENT=PRODUCTION
export SKILLS_DIR=/path/to/skills
export MCP_TRANSPORT=http
export MCP_PORT=8000
skill_to_mcp
Docker Deployment
Create a Dockerfile:
FROM python:3.12-slim
WORKDIR /app
RUN pip install skill_to_mcp
COPY skills /app/skills
ENV SKILLS_DIR=/app/skills
ENV MCP_TRANSPORT=http
ENV MCP_PORT=8000
CMD ["skill_to_mcp"]
Build and run:
docker build -t skill-to-mcp .
docker run -p 8000:8000 skill-to-mcp
About BioContextAI
BioContextAI is a community effort to connect agentic artificial intelligence with biomedical resources using the Model Context Protocol. The Registry is a community-driven catalog of MCP servers for biomedical research, enabling researchers and developers to discover, access, and contribute specialized tools and databases.
Key Principles:
- FAIR4RS Compliant: Findable, Accessible, Interoperable, Reusable for Research Software
 - Community-Driven: Open-source and collaborative development
 - Standardized: Built on the Model Context Protocol specification
 
Contributing
Contributions are welcome! See CONTRIBUTING.md for guidelines on:
- Development setup
 - Code style requirements
 - Testing procedures
 - Pull request process
 
To contribute skills to the biomedical community, consider adding them to the BioContextAI Registry.
Contact
If you found a bug, please use the issue tracker.
For questions about BioContextAI or the registry, visit biocontext.ai.
Citation
If you use this software in your research, please cite the BioContextAI paper:
@misc{kuehlCommunitybasedBiomedicalContext2025,
  title = {Community-Based Biomedical Context to Unlock Agentic Systems},
  author = {Kuehl, Malte and Schaub, Darius P. and Carli, Francesco and Heumos, Lukas and {Fern{\'a}ndez-Zapata}, Camila and Kaiser, Nico and Schaul, Jonathan and Panzer, Ulf and Bonn, Stefan and Lobentanzer, Sebastian and {Saez-Rodriguez}, Julio and Puelles, Victor G.},
  year = {2025},
  month = jul,
  pages = {2025.07.21.665729},
  publisher = {bioRxiv},
  doi = {10.1101/2025.07.21.665729},
  url = {https://biocontext.ai}
}
Acknowledgments
- Example Skill: The included 
single-cell-rna-qcskill is adapted from Anthropic's Life Sciences repository - Anthropic: For developing Claude Skills and the Model Context Protocol
 - scverse®: The scverse community (scverse.org) for best practices in single-cell analysis
 - BioContextAI Community: For fostering open-source biomedical AI infrastructure
 
License
This project is licensed under the Apache License 2.0 - see the LICENSE file for details.
Note: While this software is open-source, individual skills may have their own licenses. Users are responsible for compliance with the licenses of any skills they use or distribute.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.