Inspired by mcp-openai-gemini-llama-example.
This is an agent based on the MCP protocol that can directly operate a SQLite database using natural language, and the LLM service is compatible with OpenAI format.
What this agent do:
sequenceDiagram
participant User
participant Main
participant MCP_Client
participant MCP_Server
participant LLM
Note right of MCP_Client: Initialization & Tool Registration
Main->>MCP_Client: Create Client Instance
MCP_Client->>MCP_Server: get_available_tools()
MCP_Server-->>MCP_Client: Return Tool List
MCP_Client->>LLM: Register Tools via Function Calling
loop Interactive Session
User->>Main: Enter Prompt
Main->>LLM: Send Query
Note right of LLM: LLM autonomously decides tool usage
alt LLM Decides to Use Tool
LLM-->>Main: Request Tool Call
Main->>MCP_Client: Execute Tool Call
MCP_Client->>MCP_Server: Call Tool
MCP_Server-->>MCP_Client: Tool Response
MCP_Client-->>Main: Tool Result
Main->>LLM: Send Tool Result
LLM-->>Main: Final Response
else Direct Response
LLM-->>Main: Direct Response
end
Main-->>User: Display Response
end
This project is intended to explain: How does an LLM perceive external protocols through MCP?
Considering that MCP was proposed by Anthropic, I did not see any good examples of LLM interacting with MCP on the official MCP website. Here, I provide OpenAI's version, which theoretically can run this case as long as any OpenAI interface-compatible LLM model supports Function Calling.
The project actually has a high degree of overlap with the mcp-openai-gemini-llama-example , but due to issues like dependency conflicts and code conflicts in the original repository, it is quite messy. So I specifically created this repository to clarify the problems I mentioned in my motivation.
Please ensure that the model of the service provider you are using supports Function Calling. Note that whether Function Calling is supported is related to the provider and also to the model; some models support Function Calling, but the provider deploying that model may not necessarily support it.
How to check if the model & provider supports function calling?
For example:
openrouter.ai (Well this is a freaking display, as if it doesn't want to be seen.):
fireworks.ai:
Add .env to the project according to .env.template and fill in your OPENAI service provider information.
Please refer to the format of the service providers I have tested below:
✅ OpenRouter + qwen-turbo
OPENAI_API_KEY='sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
OPENAI_API_BASE='https://openrouter.ai/api/v1'
LLM_MODEL='qwen/qwen-turbo'
✅ OpenRouter + qwen-max
OPENAI_API_KEY='sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
OPENAI_API_BASE='https://openrouter.ai/api/v1'
LLM_MODEL='qwen/qwen-max'
OPENAI_API_KEY='sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
OPENAI_API_BASE='https://openrouter.ai/api/v1'
LLM_MODEL='openai/gpt-4o-mini'
❌ DeepSeek + deepseek-chat (🙁 Don't know the reason; the request didn't return an error, but it also didn't operate on the database.)
OPENAI_API_KEY='sk-xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx'
OPENAI_API_BASE='https://api.deepseek.com'
LLM_MODEL='deepseek-chat'
Enter your prompt (or 'quit' to exit): show tables
Response: It seems there are no user-created tables in the database yet. The `sqlite_master` table is a system table that contains metadata about the database, such as the schema of all tables, indexes, and other objects.
If you'd like to create a new table or perform any other operations, feel free to let me know! I can help you with creating tables, inserting data, or querying information. 😊
conda create -n tiny-oai-mcp-agent python=3.11
pip install -r requirements.txt
python agent.pyExample 1:
Enter your prompt (or 'quit' to exit): show tables
Response: Here are the tables available in the database:
1. **users**
2. **stock**
If you need more information about either of these tables or want to perform operations on them, just let me know!
Enter your prompt (or 'quit' to exit): create table students with 4 columuns for me, decide column detail by yourself
Response: The table **students** has been created successfully with the following columns:
1. **id**: INTEGER PRIMARY KEY
2. **name**: TEXT NOT NULL
3. **age**: INTEGER NOT NULL
4. **enrollment_date**: DATE NOT NULL
If you need to add data to this table or perform any further actions, feel free to ask!
Enter your prompt (or 'quit' to exit): show tables
Response: Now, in addition to the previous tables, the database also contains the newly created **students** table. Here’s the updated list:
1. **users**
2. **stock**
3. **students**
If you have any tasks in mind for these tables or need more information, just let me know!Example 2:
(mcp-example) Warren@L-MBP Tiny-OAI-MCP-Agent % python mcp_client.py
Enter your prompt (or 'quit' to exit): hi
Response: Hello! How can I assist you today?
Enter your prompt (or 'quit' to exit): show tables from my db
Response: Here are the tables in your database:
1. **users**
2. **stock**
3. **students**
If you need more information about any of these tables or want to perform any specific task, just let me know!
Enter your prompt (or 'quit' to exit): show metadata from users
Response: The "users" table has the following structure:
- **id**: INTEGER, Primary Key (optional, can be null)
- **name**: TEXT, Not Null
- **age**: INTEGER, Not Null
If you need to know anything else or want to perform any operations on this table, feel free to ask!
Enter your prompt (or 'quit' to exit): quit
Example 3:
(mcp-example) Warren@L-MBP Tiny-OAI-MCP-Agent % python mcp_client.py
Enter your prompt (or 'quit' to exit): show tabls
Response: It looks like we have a few tables in our database: `users`, `stock`, and `students`. Would you like to know more about any of them? We could check the structure or see what's inside! What would you like to explore first?
Enter your prompt (or 'quit' to exit): show metadata from users
Response: Sure thing! Here’s the metadata for the `users` table:
- **id**: This is the primary key (unique identifier) for each user and it can hold integer values.
- **name**: This field stores the user's name as text. It's a required field, so every entry must include a value here.
- **age**: This field holds the user's age as an integer. Like the name field, it is also required.
Would you like to dive deeper into this table? For example, we could look at some data within it or even add some new records. Let me know what sparks your interest!
Enter your prompt (or 'quit' to exit):