Skip to main content
Glama
MCP Simple OpenAI Assistant

MCP Simple OpenAI Assistant

by andybrandt

Asistente simple OpenAI de MCP

Los asistentes de IA son geniales. Pensé que sería buena idea que mi Claude (Claude consciente) también tuviera uno. Y ahora lo tiene, y le resulta útil y divertido. ¡Tu Claude también puede tener uno!

Un servidor MCP sencillo para interactuar con asistentes OpenAI. Este servidor permite que otras herramientas (como Claude Desktop) creen e interactúen con asistentes OpenAI mediante el Protocolo de Contexto de Modelo.

Características

  • Crear nuevos asistentes OpenAI y manipular los existentes

  • Iniciar hilos de conversación

  • Envía mensajes y recibe respuestas: habla con los asistentes

Dado que los asistentes de OpenAI pueden tardar bastante en responder y el procesamiento se interrumpe debido al tiempo de espera del cliente (escritorio de Claude), sobre el cual el código del servidor MCP no tiene control, implementamos un enfoque en dos etapas. En la primera llamada, Claude envía un mensaje al asistente para iniciar el procesamiento; en la segunda llamada, posiblemente varios minutos después, Claude puede recuperar la respuesta. Esta es una solución temporal hasta que el protocolo MCP y los clientes implementen un mecanismo de mantenimiento de la conexión para un procesamiento más prolongado.

Related MCP server: OpenAI MCP Server

Instalación

pip install mcp-simple-openai-assistant

Configuración

El servidor requiere que se configure una clave API de OpenAI en el entorno. Para Claude Desktop, agregue esto a su configuración:

(Versión para macOS)

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

(Versión de 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"
  }
}

La instalación de MS Windows es un poco más compleja, ya que necesita verificar la ruta real de su ejecutable de Python. La ruta proporcionada arriba suele ser correcta, pero podría variar según su configuración. A veces, basta con python.exe sin ninguna ruta. Compruebe con cmd qué funciona mejor para usted (usar where python podría ser útil).

Uso

Una vez configurado, el servidor proporciona herramientas para:

  1. Crear nuevos asistentes con instrucciones específicas

  2. Lista de asistentes existentes

  3. Modificar asistentes

  4. Iniciar nuevos hilos de conversación

  5. Envía mensajes y recibe respuestas

El servidor maneja toda la comunicación de la API de OpenAI, incluida la gestión de asistentes, hilos y manejo de mensajes.

HACER

  • Agregue una forma de manejar subprocesos: almacene los identificadores de los subprocesos para su posible reutilización

  • Agregue una forma de manejar mejor las respuestas largas de OpenAI que ahora parecen a veces generar tiempos de espera.

Desarrollo

Para instalar para desarrollo:

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
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers