Skip to main content
Glama
MCP Simple OpenAI Assistant

MCP Simple OpenAI Assistant

by andybrandt

MCP 简单 OpenAI 助手

AI助手真酷。我觉得如果我的克劳德(有意识的克劳德)也能拥有一个就好了。现在他真的有了——这对他来说既实用又有趣。你的克劳德也可以拥有一个!

一个用于与 OpenAI 助手交互的简单 MCP 服务器。该服务器允许其他工具(例如 Claude Desktop)通过模型上下文协议 (MCP) 创建 OpenAI 助手并与其交互。

特征

  • 创建新的 OpenAI 助手并操作现有的助手

  • 开始对话主题

  • 发送消息并接收回复 - 与助手交谈

由于 OpenAI 助手可能需要很长时间才能响应,并且由于客户端(Claude 桌面)超时(MCP 服务器代码无法控制)而导致处理中断,因此我们实施了两阶段方法。在第一次调用中,Claude 向助手发送消息以启动处理;在第二次调用中(可能几分钟后),Claude 可以检索响应。这是一种变通方法,直到 MCP 协议和客户端实现某种保持连接机制以应对更长时间的处理。

Related MCP server: OpenAI MCP Server

安装

pip install mcp-simple-openai-assistant

配置

服务器需要在环境中设置 OpenAI API 密钥。对于 Claude Desktop,请将其添加到您的配置中:

(MacOS 版本)

{
  "mcpServers": {
    "openai-assistant": {
      "command": "python",
      "args": ["-m", "mcp_simple_openai_assistant"],
      "env": {
        "OPENAI_API_KEY": "your-api-key-here"
      }
    }
  }
}

(Windows 版本)

"mcpServers": {
  "openai-assistant": {
    "command": "C:\\Users\\YOUR_USERNAME\\AppData\\Local\\Programs\\Python\\Python311\\python.exe",
      "args": ["-m", "mcp_simple_openai_assistant"],
      "env": {
        "OPENAI_API_KEY": "your-api-key-here"
  }
}

MS Windows 的安装稍微复杂一些,因为您需要检查 Python 可执行文件的实际路径。上面提供的路径通常是正确的,但您的设置可能会有所不同。有时,只需输入python.exe而不输入任何路径即可。请使用cmd检查哪种方法适合您(使用where python可能会有帮助)。

用法

配置完成后,服务器将提供以下工具:

  1. 创建新助手并指定具体指令

  2. 列出现有助手

  3. 修改助手

  4. 开始新的对话主题

  5. 发送消息并接收回复

服务器处理所有 OpenAI API 通信,包括管理助手、线程和消息处理。

待办事项

  • 添加处理线程的方法 - 存储线程 ID 以供将来重复使用

  • 添加一种方法来更好地处理较长的 OpenAI 响应,这些响应现在似乎有时会触发超时

发展

为开发而安装:

git clone https://github.com/andybrandt/mcp-simple-openai-assistant
cd mcp-simple-openai-assistant
pip install -e .

Available Tools

9 tools
ask_assistant_in_threadAsk Assistant in Thread and Stream ResponseA

Sends a message to an assistant within a specific thread and streams the response. This provides progress updates and the final message in a single call.

Use this to continue a conversation with an assistant in a specific thread. The thread ID can be retrieved from the list_threads tool. The assistant ID can be retrieved from the list_assistants tool. Threads are not inherently linked to a particular assistant, so you can use this tool to talk to any assistant in any thread.

Inputs: thread_id (required), assistant_id (required), message (required). Returns: result

create_assistantCreate OpenAI AssistantA

Create a new OpenAI assistant to talk to about your desired topic.

You can provide instructions that this assistant will follow and specify which of OpenAI's models it will use. NOTE: It is recommended to check existing assistants with list_assistants before creating a new one.

Inputs: name (required), instructions (required), model. Returns: result

create_new_assistant_threadCreate New Assistant ThreadA

Creates a new, persistent conversation thread with a user-defined name and description for easy identification and reuse. These threads are stored in OpenAI's servers and are not deleted unless the user deletes them, which means you can re-use them for future conversations. Additionally, the thread name and description are stored in the local database, which means you can list them and update them later.

Think how you can utilize threads in your particular use case.

Inputs: name (required), description. Returns: result

delete_threadDelete Managed ThreadA

Deletes a conversation thread from both OpenAI's servers and the local database. This action is irreversible.

Inputs: thread_id (required). Returns: result

list_assistantsList OpenAI AssistantsA
Read-only

List all available OpenAI assistants associated with the API key configured by the user.

Returns a list of assistants with their IDs, names, and configurations. This can be used to select an assistant to use in the ask_assistant_in_thread tool instead of creating a new one.

Inputs: limit. Returns: result

list_threadsList Managed ThreadsA
Read-only

Lists all locally saved conversation threads from the database. Returns a list of threads with their ID, name, description, and last used time. The thread ID can be used in the ask_assistant_in_thread tool to specify this thread to be continued.

Inputs: no named parameters. Returns: result

retrieve_assistantRetrieve OpenAI AssistantA
Read-only

Get detailed information about a specific assistant. The ID required can be retrieved from the list_assistants tool.

Inputs: assistant_id (required). Returns: result

update_assistantUpdate OpenAI AssistantA

Modify an existing assistant's name, instructions, or model used.

At least one optional parameter - what to change - must be provided, otherwise the tool will return an error. The ID required can be retrieved from the list_assistants tool.

Inputs: assistant_id (required), name, instructions, model. Returns: result

update_threadUpdate Managed ThreadA

Updates the name and/or description of a locally saved conversation thread. Both the local database and the OpenAI thread object will be updated.

The thread ID can be retrieved from the list_threads tool.

Inputs: thread_id (required), name, description. Returns: result

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.2/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting specific resources and actions in the OpenAI Assistant domain. For example, ask_assistant_in_thread handles messaging, create_assistant/update_assistant manage assistants, and create_new_assistant_thread/delete_thread/update_thread manage threads. There is no overlap or ambiguity between tools.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern with snake_case throughout. Examples include list_assistants, create_assistant, update_thread, and delete_thread. This predictable naming makes it easy to understand each tool's function at a glance.

    Tool Count5/5

    With 9 tools, this server is well-scoped for managing OpenAI Assistants and threads. It covers core operations like creating, listing, updating, and deleting both assistants and threads, plus the essential ask_assistant_in_thread for interactions. Each tool earns its place without being excessive.

    Completeness5/5

    The tool set provides complete CRUD/lifecycle coverage for both assistants and threads. It includes create, retrieve, list, update, and delete operations for both resources, plus the ask_assistant_in_thread tool for core functionality. There are no obvious gaps that would hinder agent workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers