Back to browse
GitHub Repository

Convert an mcp server to an skill that agents can use.

7 starsPython

MCP-skill – generate Python skills from MCP servers

by manojbajaj95·Mar 6, 2026·2 points·1 comment

AI Analysis

●●SolidBig BrainSolve My Problem

Compiles MCP tools to typed Python to skip model loop, but MCP agents are nascent—adoption depends on platform.

Strengths
  • Smart architecture: skips model round-trip per tool call by letting agents chain tools in Python code instead.
  • Type generation from JSON Schema + validation with ruff/mypy ensures generated code is safe and correct.
  • Programmatic Tool Calling alignment is forward-thinking; Claude's own docs endorse this pattern.
Weaknesses
  • Timing risk: MCP ecosystem is early; tool adoption depends on Claude/Anthropic platform growth and third-party MCP server availability.
  • Narrow scope: only generates Python; agent frameworks vary (LangChain, AutoGen, etc.), so reusability across frameworks unclear.
Target Audience

AI/agent developers using MCP servers who want to reduce token burn and latency in multi-tool workflows.

Similar To

Claude SDK · Anthropic Cookbooks (Programmatic Tool Calling)

Post Description

I've been experimenting with MCP-based agents for some of my daily workflows (checking assigned issues, gathering context, drafting plans, etc.).

With most agent frameworks, tool calls run in a loop like this:

agent → tool → agent → tool → agent → tool

Each step goes back through the model. For tools returning large payloads, this adds latency and burns tokens.

So I built a small tool that converts an MCP server into a Python skill.

It introspects the server and generates a typed Python class where each tool becomes an async method.

Example:

issue = await github.get_issue(issue_id) docs = await search.web_search(issue.title)

The agent can process results locally in code and only return the final output.

This also enables progressive disclosure. Tools can return large responses, but the agent can filter or aggregate data in code instead of sending everything back into the model context.

The generated skills include a `SKILL.md` file and can be reused later, so useful workflows can be saved and run again as scripts.

Still a work in progress, but already useful in my own setup.

Would love feedback from others experimenting with MCP or similar patterns.

Repo: https://github.com/manojbajaj95/mcp-skill

Similar Projects

Security●●Solid

Security Scanner for Agent Skills and MCP

Finally a security linter for MCP configs before you accidentally execute a prompt injection payload.

Solve My ProblemShip It
lirantal
701mo ago