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