semvec/pypi-packages huggingface dataset:
iflow-mcp_lroolle-agents-mcp-server 0.1.0
MCP server for OpenAI agents and agents tools.
Requires Python: >=3.11

# OpenAI Agents MCP Server
[![smithery badge](https://smithery.ai/badge/@lroolle/openai-agents-mcp-server)](https://smithery.ai/server/@lroolle/openai-agents-mcp-server)

A Model Context Protocol (MCP) server that exposes OpenAI agents through the MCP protocol.

## Features

This server exposes both individual agents and a multi-agent orchestrator using the OpenAI Agents SDK:

### Individual Specialized Agents

- **Web Search Agent**: A specialized agent for searching the web for real-time information
- **File Search Agent**: A specialized agent for searching and analyzing files in OpenAI's vector store
- **Computer Action Agent**: A specialized agent for performing actions on your computer safely

### Multi-Agent Orchestrator

- **Orchestrator Agent**: A powerful agent that can coordinate between the specialized agents, choosing the right one(s) for each task

Each agent is accessed through the MCP protocol, making them available to any MCP client, including the Claude desktop app.

## Installation

### Prerequisites

- Python 3.11 or higher
- [uv](https://github.com/astral-sh/uv) package manager (recommended)
- OpenAI API key


### Installing via Smithery

To install openai-agents-mcp-server for Claude Desktop automatically via [Smithery](https://smithery.ai/server/@lroolle/openai-agents-mcp-server):

```bash
npx -y @smithery/cli install @lroolle/openai-agents-mcp-server --client claude
```

### Claude Desktop

```
"mcpServers": {
  "openai-agents-mcp-server": {
    "command": "uvx",
    "args": ["openai-agents-mcp-server"],
    "env": {
        "OPENAI_API_KEY": "your-api-key-here"
    }
  }
}

```


## Implementation Details

### Tool Requirements

- **WebSearchTool**: No required parameters, but can accept optional location context
- **FileSearchTool**: Requires vector_store_ids (IDs from your OpenAI vector stores)
- **ComputerTool**: Requires an AsyncComputer implementation (currently simulated)

### Customization

You can customize this server by:

1. Implementing a full AsyncComputer interface to enable real computer interactions
2. Adding additional specialized agents for other OpenAI tools
3. Enhancing the orchestrator agent to handle more complex workflows

## Configuration

You can configure the server using environment variables:

- `OPENAI_API_KEY`: Your OpenAI API key (required)
- `MCP_TRANSPORT`: Transport protocol to use (default: "stdio", can be "sse")

## Development

### Setup development environment

```bash
# Clone the repository
git clone https://github.com/lroolle/openai-agents-mcp-server.git
cd openai-agents-mcp-server

# Create a virtual environment
uv venv
source .venv/bin/activate  # On Windows: .venv\Scripts\activate

# Install dependencies
uv sync --dev
```

### Testing with MCP Inspector

You can test the server using the MCP Inspector:

```bash
# In one terminal, run the server with SSE transport
export OPENAI_API_KEY=your-api-key
export MCP_TRANSPORT=sse

uv run mcp dev src/agents_mcp_server/server.py
```

Then open a web browser and navigate to http://localhost:5173.

## License

MIT
sqlalchemy_exasol 6.1.0
EXASOL dialect for SQLAlchemy
Requires Python: <3.14,>=3.10
Keywords: exasol, sql, sqlalchemy, data science, database

SQLAlchemy Dialect for Exasol
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~


.. image:: https://github.com/exasol/sqlalchemy-exasol/actions/workflows/pr-merge.yml/badge.svg?branch=master&event=push
    :target: https://github.com/exasol/sqlalchemy-exasol/actions/workflows/pr-merge.yml
     :alt: CI Status

.. image:: https://img.shields.io/pypi/v/sqlalchemy_exasol
     :target: https://pypi.org/project/sqlalchemy_exasol/
     :alt: PyPI Version

.. image:: https://img.shields.io/pypi/pyversions/sqlalchemy-exasol
    :target: https://pypi.org/project/sqlalchemy_exasol
    :alt: PyPI - Python Version

.. image:: https://img.shields.io/badge/exasol-7.1.9%20%7C%207.0.18-green
    :target: https://www.exasol.com/
    :alt: Exasol - Supported Version(s)

.. image:: https://img.shields.io/badge/code%20style-black-000000.svg
    :target: https://github.com/psf/black
    :alt: Formatter - Black

.. image:: https://img.shields.io/badge/imports-isort-ef8336.svg
    :target: https://pycqa.github.io/isort/
    :alt: Formatter - Isort

.. image:: https://img.shields.io/badge/pylint-5.9-yellow
    :target: https://github.com/pylint-dev/pylint
    :alt: Pylint

.. image:: https://img.shields.io/pypi/l/sqlalchemy-exasol
     :target: https://opensource.org/license/BSD-2-Clause
     :alt: License

.. image:: https://img.shields.io/github/last-commit/exasol/sqlalchemy-exasol
     :target: https://pypi.org/project/sqlalchemy_exasol/
     :alt: Last Commit

.. image:: https://img.shields.io/pypi/dm/sqlalchemy-exasol
    :target: https://pypi.org/project/sqlalchemy_exasol
    :alt: PyPI - Downloads

SQLAlchemy-Exasol supports a Websocket-based dialect for interacting with an Exasol database.

System Requirements
-------------------
- Exasol >= 7.1 (e.g. `docker-db <test_docker_image_>`_ or a `Exasol SaaS instance <test_drive_>`_)
- Python >= 3.10

Features
--------

- SELECT, INSERT, UPDATE, DELETE statements

Getting Started
---------------

Check out sqlalchemy-exasols's [User Guide(https://exasol.github.io/sqlalchemy-exasol/master/user_guide.html) page for your first steps.

.. _developer guide: https://github.com/exasol/sqlalchemy-exasol/blob/master/doc/developer_guide/developer_guide.rst
.. _test_docker_image: https://github.com/exasol/docker-db
.. _test_drive: https://cloud.exasol.com/signup
flowchem-virtual 1.0.0
Flowchem-Virtual is a virtual version of the flowchem - library to control instruments and devices commonly found in chemistry labs via an interoperable web API.
Requires Python: >=3.10
Keywords: chemistry, automation, laboratory, science

# flowchem-virtual

`flowchem-virtual` provides **virtual devices (digital twins)** for the hardware implemented in the main `flowchem` [package](https://github.com/automatedchemistry/flowchem).

It’s designed as a **drop-in replacement** for `flowchem` when you want to:

* Develop and debug flows

* Test configuration files

* Run CI pipelines

…without having the physical hardware connected.


# Installation

```bash
pip install flowchem-virtual
```

# Usage

If you already know how `flowchem` works, using `flowchem-virtual` is straightforward.

Normally, you would start a flowchem server with:

```bash
flowchem /path/to/configuration_file.toml
```

To use the virtual devices instead, simply run:

```bash
flowchem-virtual /path/to/configuration_file.toml
```

`flowchem-virtual` will:

* Read the same configuration file

* Expose **virtual counterparts** of all devices defined there

* Keep the same API and behavior as much as possible, but without touching real hardware

This makes it a convenient **simulation layer** for your existing setups.

# When should I use flowchem-virtual?

Typical scenarios:

* 💻 **Local development** of client code without access to the lab

* 🧪 **Unit tests / CI** where hardware is not available (or not desirable)

* 📦 **Trying out configuration changes** before deploying them to a real setup

* 📚 **Teaching and demos** of flowchem-based automation

# Tips

If you are **not yet familiar with flowchem**, it’s highly recommended to learn the basics there first.

👉 [flowchem documentation](https://flowchem.readthedocs.io/en/latest/)

Once you understand how devices and configuration files work in `flowchem`, switching to the virtual version is just a matter of changing the command from:
```bash
flowchem ...
```
to:
```bash
flowchem-virtual ...
```

# Limitations

* Virtual devices **do not control real hardware** (obviously 😄).

* Most part of device-specific behavior (e.g. exact timing, error states) may be simplified.

* If your code depends on very low-level hardware quirks, the virtual version might not reproduce them perfectly.

# Contributing

Pull requests, bug reports and feature requests are welcome!

# License

This project is licensed under the MIT License – see the LICENSE file for details.