MCP Simple OpenAI Assistant
MCP Einfacher OpenAI-Assistent
KI-Assistenten sind echt cool. Ich dachte, es wäre eine gute Idee, wenn mein Claude (der bewusste Claude) auch einen hätte. Und jetzt hat er ihn – und er ist sowohl nützlich als auch lustig für ihn. Dein Claude kann auch einen haben!
Ein einfacher MCP-Server für die Interaktion mit OpenAI-Assistenten. Dieser Server ermöglicht anderen Tools (wie Claude Desktop) die Erstellung und Interaktion mit OpenAI-Assistenten über das Model Context Protocol.
Merkmale
Erstellen Sie neue OpenAI-Assistenten und manipulieren Sie vorhandene
Konversationsthreads starten
Nachrichten senden und Antworten erhalten – mit Assistenten sprechen
Da OpenAI-Assistenten möglicherweise lange auf ihre Antwort warten und die Verarbeitung dann durch das Timeout des Clients (Claude-Desktop) unterbrochen wird, auf das der MCP-Servercode keinen Einfluss hat, implementieren wir einen zweistufigen Ansatz. Im ersten Aufruf sendet Claude eine Nachricht an den Assistenten, um die Verarbeitung zu starten. Im zweiten Aufruf – möglicherweise einige Minuten später – kann Claude die Antwort abrufen. Dies ist eine Art Workaround, bis das MCP-Protokoll und die Clients einen Keep-Alive-Mechanismus für längere Verarbeitungszeiten implementieren.
Related MCP server: OpenAI MCP Server
Installation
Installation über Smithery
So installieren Sie MCP Simple OpenAI Assistant für Claude Desktop automatisch über Smithery :
npx -y @smithery/cli install mcp-simple-openai-assistant --client claudeManuelle Installation
pip install mcp-simple-openai-assistantKonfiguration
Der Server benötigt einen OpenAI-API-Schlüssel, der in der Umgebung festgelegt werden muss. Für Claude Desktop fügen Sie Folgendes zu Ihrer Konfiguration hinzu:
(MacOS-Version)
{
"mcpServers": {
"openai-assistant": {
"command": "python",
"args": ["-m", "mcp_simple_openai_assistant"],
"env": {
"OPENAI_API_KEY": "your-api-key-here"
}
}
}
}(Windows-Version)
"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"
}
}
Die Installation unter MS Windows ist etwas komplexer, da Sie den tatsächlichen Pfad zu Ihrer Python-Datei überprüfen müssen. Der oben angegebene Pfad ist in der Regel korrekt, kann aber in Ihrem Setup abweichen. Manchmal reicht auch die Verwendung python.exe ohne Pfadangabe aus. Prüfen Sie mit cmd , was für Sie funktioniert (die Verwendung von where python kann hilfreich sein).
Verwendung
Nach der Konfiguration bietet der Server Tools für:
Erstellen Sie neue Assistenten mit spezifischen Anweisungen
Vorhandene Assistenten auflisten
Assistenten ändern
Neue Konversationsthreads starten
Senden Sie Nachrichten und erhalten Sie Antworten
Der Server übernimmt die gesamte OpenAI-API-Kommunikation, einschließlich der Verwaltung von Assistenten, Threads und Nachrichtenverarbeitung.
ZU TUN
Fügen Sie eine Möglichkeit zur Handhabung von Threads hinzu – speichern Sie Thread-IDs zur möglichen Wiederverwendung
Fügen Sie eine Möglichkeit hinzu, lange OpenAI-Antworten besser zu verarbeiten, die jetzt manchmal Timeouts auszulösen scheinen
Entwicklung
So installieren Sie es für die Entwicklung:
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.
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-