Drop a skill, share it over MCP
Every copy of a skill is a fork.
Skills reach your agent in all kinds of ways. You clone a repo, run npx skills add, install a plugin, or copy a folder out of a teammate's project. However it gets there, it lands as files on disk, and from then on it's yours. When the author fixes a step next week, your copy doesn't know. Neither does your agent.
Every copy of a skill is a fork
That's a nuisance for a skill only you use. For one your whole team depends on, nobody can say which version anyone is running.
It's also backwards. Most skills worth sharing explain how to use something: an API, a platform, an internal service. The people who build that thing know best how it should be used, and its tools often already live on an MCP server. But the skill ships separately, so the tools move forward and the instructions get left behind.
Skills over MCP lets them ship together. The skill lives on a server, next to the tools it describes, and every agent reads that one copy. Fix it once and everyone has the fix. There are two ways to get there: drop a skill and get a URL, or add skills to the MCP server you already have.
The no-code way
We wanted the shortest path from "I have a skill" to "my team has it," so we built a page for it. Drop a skill folder, a .zip or a SKILL.md on the page, or paste a GitHub repo, public or private, and you get back a hosted MCP server. No server code, no deploy.
A dropped server is public and expires after seven days, even if the skills came from a private repo, so treat it like a public gist. To keep it, save the one-time claim link the page gives you and sign in to FastMCP Gateway. A claimed server stays up for free, can be made private, and keeps its URL when you upload a new version.
How it works
Connect once, get the tools and the skills
The Skills extension, SEP-2640, comes from MCP's Skills Over MCP Working Group and adds one thing to the protocol: a way to ask a server what skills it has. A client calls skills/list and gets back each skill's frontmatter and a manifest of its files:
{
"uri": "skill://release-notes/SKILL.md",
"frontmatter": {
"name": "release-notes",
"description": "Draft release notes from merged PRs."
},
"resources": [
{
"uri": "skill://release-notes/SKILL.md",
"digest": "sha256:9f2c...",
"size": 2314
},
{
"uri": "skill://release-notes/template.md",
"digest": "sha256:41ab...",
"size": 806
}
]
}Everything else is ordinary MCP. Each file is a skill:// resource the client reads when it needs it, so the agent sees names and descriptions up front and only loads a skill when it uses one, same as on disk. The digests let the client confirm it got exactly what the server has.
The agent only loads a skill when it uses one
Client support is early. VS Code reads skills straight off an MCP server as of 1.146, in preview behind a setting, and most other clients don't yet. So every dropped server also comes with list_skills and read_skill tools. Any agent that can call a tool can load your skills today.
One MCP URL for every agent on your team
Or add them to your own server
Every dropped server is a FastMCP server, so if you build your own, you can add a folder of skills to it right next to your tools:
from pathlib import Path
from fastmcp import FastMCP
from fastmcp.server.transforms import ResourcesAsTools
from fastmcp.skills.provider import SkillsDirectoryProvider
mcp = FastMCP("Pipelines")
@mcp.tool
def check_freshness(table: str) -> str:
"""Return when a table was last updated."""
return f"{table}: updated 5 minutes ago"
mcp.add_provider(SkillsDirectoryProvider(Path("skills")))
mcp.add_transform(ResourcesAsTools(mcp))Every subfolder with a SKILL.md becomes a skill, with the same authorization as your tools. ResourcesAsTools is the fallback for clients that can't read skills yet. It adds list_resources and read_resource tools, which reach the same skill:// files that a dropped server's list_skills and read_skill tools do. When a tool changes, update its skill in the same commit, and every agent gets both on your next deploy.
One live copy also means a bad edit reaches every agent at once, and nobody can pin last week's version. So put skill changes through the same review as the tools they describe. The digests show exactly which files changed, and a team that needs a frozen copy can still sync one to disk. The skills over MCP post shows how, along with defining skills in code.
Try it
Pick a skill and drop it on gofastmcp.com/skill-drop. Connect your agent, claim the server, and share the URL with your team.
The people who build the tools can ship the skill for using them. And because it lives on the server, there's only ever one copy.
Free hat. One day only.
To celebrate Skill Drop, the $KILL$ TO PAY THE BILL$ beanie is on us. Add both codes at checkout and the hat and the shipping are free.
Use both codes at checkout
Nov 17 onlyEnds midnight PTUS shipping only
