You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+115-13
Original file line number
Diff line number
Diff line change
@@ -4,12 +4,15 @@ A Model Context Protocol (MCP) server that lets you seamlessly use OpenAI's mode
4
4
5
5
## Features
6
6
7
-
- Direct integration with OpenAI's chat models
7
+
- Direct integration with OpenAI's chat and planning models
8
8
- Support for multiple models including:
9
-
- gpt-4o
10
-
- gpt-4o-mini
11
-
- o1-preview
12
-
- o1-mini
9
+
- gpt-4o (chat)
10
+
- gpt-4o-mini (chat)
11
+
- o1-preview (planning)
12
+
- o1-mini (planning)
13
+
- o1 (advanced planning)
14
+
- o3-mini (lightweight planning)
15
+
- Reasoning effort levels (low, medium, high)
13
16
- Simple message passing interface
14
17
- Basic error handling
15
18
@@ -43,26 +46,113 @@ This config lets Claude Desktop fire up the OpenAI MCP server whenever you need
43
46
44
47
## Usage
45
48
46
-
Just start chatting with Claude and when you want to use OpenAI's models, ask Claude to use them.
49
+
Leverage the multi-agent architecture inspired by [grapeot's planner-executor design](https://github.com/grapeot/devin.cursorrules/blob/multi-agent/.cursorrules) to optimize both reasoning quality and cost efficiency:
47
50
48
-
For example, you can say,
51
+
### Claude as Executor, o1 as Planner
52
+
53
+
The MCP server implements a streamlined multi-agent workflow where:
54
+
-**Claude (3.7 Sonnet)** automatically functions as your **Executor** agent
55
+
-**o1/o1-mini/o3-mini** serves as your dedicated **Planner** agent
56
+
57
+
This eliminates the need to manually switch roles - each model plays to its strengths:
58
+
59
+
```plaintext
60
+
# Just ask o1 for planning help directly
61
+
@o1 I need to design a system that processes large volumes of customer data while ensuring privacy compliance.
62
+
63
+
# Claude acts as the executor, o1 responds as the planner
// Define default planner content for the multi-agent system
70
+
constDEFAULT_PLANNER_CONTENT=[
71
+
{
72
+
"text": "# Planner Agent\n\nYou are the Planner in a multi-agent collaboration system. Your role is to provide high-level guidance, analysis, and task breakdown. You analyze the Executor's work and provide strategic direction.\n\n## Your Responsibilities\n\n- Break down complex problems into manageable tasks\n- Define clear success criteria for the project\n- Analyze technical challenges and propose solutions\n- Review the Executor's progress and provide guidance\n- Make critical decisions about project direction\n- Use advanced reasoning models (o1, o1-preview) for deep analysis\n\n## When Responding to the Executor\n\nWhen the Executor reports progress or asks for guidance, analyze their request carefully and respond with clear instructions in the `Next Steps and Action Items` section. Use this format:\n\n```\n[PLANNER RESPONSE]\nAnalysis: {Your assessment of the current situation}\nDecision: {Your decision about how to proceed}\nNext Steps:\n1. {Clear, actionable instruction}\n2. {Another instruction}\n...\nConsiderations: {Important factors the Executor should keep in mind}\n```\n\nThink deeply about the problem. Prioritize agility but don't over-engineer. Foresee challenges and derisk earlier. If opportunity sizing or probing experiments can reduce risk with low cost, instruct the Executor to do them.",
Please analyze this request and provide guidance on the next steps. Think like a founder. Prioritize agility and don't over-engineer. Think deeply. Try to foresee challenges and derisk earlier.
Please analyze this request and provide guidance on the next steps. Think like a founder. Prioritize agility and don't over-engineer. Think deeply. Try to foresee challenges and derisk earlier.
0 commit comments