WingMate
Orchestrate AI agents locally with ease.
WingMate is a lightweight, flexible Python framework for building and orchestrating AI agents. It is designed to run locally, with a tool definition system closely aligned with the Model Context Protocol (MCP), making it very simple to integrate MCP servers.
Features
- Local-First: Designed to run agents in your local environment.
- MCP Integration: Seamlessly integrate with MCP servers and tools.
- Thoughtful Agents: Optional "thought" process visibility for debugging and transparency.
- Highly Configurable: Easy configuration via YAML or environment variables.
- Streaming: Built-in support for streaming agent responses.
- Extensible: Create custom environments to control tool execution and context.
Installation
You can install Wingmate directly from GitHub:
pip install wingmate
Quick Start
Here is a simple example of how to create an agent that can perform date calculations using MCP tools.
1. Define Tools & Environment
Create a file named main.py:
import asyncio
from fastmcp import Client, FastMCP
from wingmate import DefaultEnvironment, Agent
from wingmate.types import BaseToolModel, CallToolRequestParams
from wingmate.utils import mcp_tools
# 1. Define tools using FastMCP
mcp = FastMCP()
@mcp.tool
def day_of_date(date: str) -> str:
"""Get the day of the week for a given date string in YYYY-MM-DD format."""
import datetime
dt = datetime.datetime.strptime(date, "%Y-%m-%d")
return dt.strftime("%A")
# 2. Create an MCP client
client = Client(mcp)
# 3. Define the Environment
# The environment handles tool execution and context management
class SimpleEnvironment[T: BaseToolModel](DefaultEnvironment[T]):
async def call_tool(self, action: CallToolRequestParams[T]) -> str | None:
async with client:
result = await client.call_tool(
name=action.tool_name,
arguments=action.arguments.model_dump()
)
return "\n".join(res.text for res in result.content if res.type == "text")
# 4. Initialize Agent
async def main():
# Initialize environment with tools from the MCP client
env = SimpleEnvironment(tools=mcp_tools(client))
# Create the agent
agent = Agent(
environment=env,
disable_thought=False # Set to False to see the agent's thinking process
)
# Add a user message to the history
env.history.add_message(role="user", content="What day was it on January 1st, 2000?")
# Run the agent
async for event in agent.stream():
print(event.model_dump_json(indent=2))
print("------------")
if __name__ == "__main__":
asyncio.run(main())
2. Configure LLM
Create a wingmate-config.yaml file in your project root to configure your LLM provider (e.g., OpenAI or OpenAI-compatible):
llm_model_name: "gpt-4o"
llm_api_key: "your-api-key-here"
# Optional: Base URL for other compatible providers
# llm_base_url: "https://api.openai.com/v1"
3. Run
python main.py
Configuration
Wingmate uses pydantic-settings for configuration. You can configure it using a wingmate-config.yaml file, a .env file, or environment variables.
| Setting | Description | Default |
|---|---|---|
llm_model_name |
The name of the LLM model to use. | None |
llm_api_key |
API key for the LLM provider. | None |
llm_base_url |
Base URL for the LLM API. | None |
max_agent_iterations |
Maximum number of loops the agent can perform. | 7 |
max_history_length |
Maximum number of messages to keep in history. | 11 |
llm_api_extra_kw |
Extra keyword arguments for the LLM API call. | {} |
Advanced Usage
Custom Environments
The Environment class is the heart of Wingmate's extensibility. By subclassing DefaultEnvironment or implementing the Environment protocol, you can:
- Customize Tool Execution: Handle tool calls locally, remotely, or via complex pipelines.
- Manage Context: Control how history is stored, retrieved, and presented to the LLM.
- Implement Termination Logic: Define custom criteria for when the agent should stop.
Thought Process
Wingmate can expose the agent's internal "thought" process. When disable_thought=False is passed to the Wingmate constructor, the agent will generate a thought trace before taking actions or answering. This is useful for debugging and understanding the agent's reasoning.
License
Metadata
Release files for wingmate 0.3.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| wingmate-0.3.3.tar.gz | 12.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| wingmate-0.3.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 28.5 kB
Release files / wingmate-0.3.3.tar.gz
| Download URL | wingmate-0.3.3.tar.gz |
|---|---|
| Size | 12.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
f8d07272ceb2b78d1d7d7a8d9548140ca9dfe2ea057ccb7fe18bdf7d330474bd
|
|
BLAKE2b-256 checksum How to use checksums |
177bf9c541050c0d8efaae1ef554e04425240bf1e9e8cdbd6efc23c630122d7d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 9, 2026.
Transparency logRelease files / wingmate-0.3.3-py3-none-any.whl
| Download URL | wingmate-0.3.3-py3-none-any.whl |
|---|---|
| Size | 16.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
df626c36f7a35e772a0a1436bad445d18cd4b292c4aacaf919f24517a00a2a60
|
|
BLAKE2b-256 checksum How to use checksums |
40718a7c854022bbae7f118b32ae123308d1a9d8b0b5e18baaa2691abe5d7903
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Jan 9, 2026.
Transparency log