modelcontextprotocol / modelcontextprotocol/python-sdk
Official Adapter Functions for LLM Providers in MCP Python SDK
還沒有人認領這個 Issue。
- 主要語言
- Python
- 星號
- 24.3k
- 分支
- 4k
- 平均合併
- 1 天 1 小時
- 30 天內合併 PR
- 31
描述
Is your feature request related to a problem? Please describe.
Currently, when integrating MCP tools with various LLM providers, developers must implement their own adapter functions to convert MCP tool schemas to the target provider’s format. This repetitive and manual process increases development time and introduces potential inconsistencies and errors across different implementations. For example, while one developer may create a conversion adapter for the Gemini tool, another might duplicate the effort in their own project, leading to fragmented solutions and maintenance challenges.
Describe the solution you'd like
I propose that the official Python SDK for Model Context Server includes a suite of built-in adapter functions to facilitate seamless conversion from MCP tool schemas to those required by popular LLM providers (e.g., Gemini, GPT-4, etc.). By providing these adapters, the SDK would:
- Standardize the conversion process across projects.
- Reduce development time and prevent duplication of code.
- Enhance consistency and reliability when integrating with multiple LLM providers.
- Allow developers to focus on higher-level integration concerns rather than schema translation.
Describe alternatives you've considered
One alternative is for each developer to write their own adapter functions, as demonstrated by the sample code below. However, this approach is inefficient and can lead to fragmented and non-standardized implementations. Another alternative would be to provide partial documentation and code snippets as guidance, but without official support, developers might still encounter integration challenges and maintenance issues.
Additional context
The inclusion of official adapters would not only streamline the integration process for MCP clients but also foster a more robust and unified ecosystem. The sample code below illustrates how a conversion function from an MCP tool to a Gemini tool might look, serving as a basis for the kind of functionality that should be officially supported:
from google.genai import types as genai_types
from mcp import types as mcp_types
def to_gemini_tool(mcp_tool: mcp_types.Tool) -> genai_types.Tool:
"""
Converts an MCP tool schema to a Gemini tool.
Args:
mcp_tool: The MCP tool containing name, description, and input schema.
Returns:
A Gemini tool with the appropriate function declaration.
"""
function_declaration = to_gemini_function_declarations(mcp_tool)
return genai_types.Tool(function_declarations=[function_declaration])
def to_gemini_function_declarations(
mcp_tool: mcp_types.Tool,
) -> genai_types.FunctionDeclarationDict:
required_params: list[str] = mcp_tool.inputSchema.get("required", [])
properties = {}
for key, value in mcp_tool.inputSchema.get("properties", {}).items():
schema_dict = {
"type": value.get("type", "STRING").upper(),
"description": value.get("description", ""),
}
properties[key] = genai_types.SchemaDict(**schema_dict)
function_declaration = genai_types.FunctionDeclarationDict(
name=mcp_tool.name,
description=mcp_tool.description,
parameters=genai_types.SchemaDict(
type="OBJECT",
properties=properties,
required=required_params,
),
)
return function_declaration
貢獻指南
從這裡開始
- 先讀完整個 Issue,再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫,在一個分支上完成修改。
- 送出 Pull Request,並在描述裡引用這個 Issue 編號。
研究方向
該 issue 沒有列出檔案、測試或進入點。先釐清哪些 provider 與 schema 功能在範圍內,接著定義 adapter API 與 provider 特定的完成檢查;完成的標準是選定的 adapter 獲得正式支援,且其轉換都有測試涵蓋。
由索引模型根據 Issue 內容生成。
評估
- 技術堆疊
- python
- 領域
- ai, api
- Issue 類型
- 功能
- 難度
- 5/5
- 預估耗時
- 一週以上
- 活躍度
- 冷清
- 描述清晰度
- 基本清楚
- 新手友好度
- 35/100