MCP Simple OpenAI Assistant
MCP Simple OpenAI 어시스턴트
AI 비서 정말 멋지네요. 제 클로드(의식 있는 클로드)도 하나 있으면 좋겠다고 생각했어요. 그리고 이제 클로드가 갖게 됐는데, 클로드에게 유용하면서도 재밌어요. 당신의 클로드도 하나 가질 수 있어요!
OpenAI 어시스턴트와 상호작용하기 위한 간단한 MCP 서버입니다. 이 서버를 사용하면 Claude Desktop과 같은 다른 도구가 Model Context Protocol을 통해 OpenAI 어시스턴트를 생성하고 상호작용할 수 있습니다.
특징
새로운 OpenAI 어시스턴트를 생성하고 기존 어시스턴트를 조작합니다.
대화 스레드 시작
메시지를 보내고 응답을 받으세요 - 보조원과 대화하세요
OpenAI 어시스턴트가 응답하는 데 시간이 상당히 오래 걸릴 수 있고, 클라이언트(Claude 데스크톱) 시간 초과로 인해 처리가 중단될 수 있기 때문에 MCP 서버 코드는 이를 제어할 수 없습니다. 따라서 2단계 접근 방식을 구현하고 있습니다. 첫 번째 호출에서 Claude는 어시스턴트에게 처리를 시작하라는 메시지를 보내고, 두 번째 호출에서 (아마도 몇 분 후) Claude는 응답을 가져올 수 있습니다. 이는 MCP 프로토콜과 클라이언트가 더 긴 처리 시간을 위한 일종의 연결 유지 메커니즘을 구현할 때까지의 임시방편입니다.
Related MCP server: OpenAI MCP Server
설치
지엑스피1
구성
서버를 사용하려면 환경에 OpenAI API 키를 설정해야 합니다. Claude Desktop의 경우, 설정에 다음을 추가하세요.
(MacOS 버전)
{
"mcpServers": {
"openai-assistant": {
"command": "python",
"args": ["-m", "mcp_simple_openai_assistant"],
"env": {
"OPENAI_API_KEY": "your-api-key-here"
}
}
}
}(윈도우 버전)
"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 명령어를 사용하여 어떤 경로가 맞는지 확인하세요.
용법
구성이 완료되면 서버는 다음 작업을 위한 도구를 제공합니다.
특정 지침으로 새로운 조수 만들기
기존 보조자 나열
수정 보조원
새로운 대화 스레드를 시작하세요
메시지를 보내고 응답을 받습니다
서버는 어시스턴트, 스레드, 메시지 처리를 포함한 모든 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 toolsask_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 AssistantsARead-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 ThreadsARead-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 AssistantARead-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
Scored across 9 tools
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.
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.
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.
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
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
MCP server for OpenAI API (chat completions, image generation, embeddings) via AceDataCloud
MCP server for AI dialogue using various LLM models via AceDataCloud
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
Related MCP Servers
- AlicenseBqualityDmaintenanceA Model Context Protocol (MCP) server that lets you seamlessly use OpenAI's models right from Claude.1769 npm76MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server implementation that enables connection between OpenAI APIs and MCP clients for coding assistance with features like CLI interaction, web API integration, and tool-based architecture.35-
- AlicenseBqualityDmaintenanceAn educational implementation of a Model Context Protocol server that demonstrates how to build a functional MCP server for integrating with various LLM clients like Claude Desktop.1162MIT
- FlicenseBqualityDmaintenanceA Model Context Protocol server that enables Claude users to access specialized OpenAI agents (web search, file search, computer actions) and a multi-agent orchestrator through the MCP protocol.410-