MCP server de Arbiter
Commit 11 nov 2026Proporciona un firewall de capacidades que permite a los agentes de IA interactuar con servicios como SMTP e IMAP mediante un acceso controlado por políticas.
También conocido como omry/arbiter
- Stars
- 3
- Herramientas
- —
- Descargas, 30 días
- —
- Última versión
- —
- Último commit
- 11 nov 2026
- Licencia
- MIT
¿Qué es Arbiter MCP?
Proporciona un firewall de capacidades que permite a los agentes de IA interactuar con servicios como SMTP e IMAP mediante un acceso controlado por políticas.
Resumen generado a partir del README del proyecto
Acerca del MCP server de Arbiter
Arbiter permite asegurar las interacciones de los agentes de IA con los servicios de correo electrónico mediante un firewall de capacidades. Proporciona una forma controlada para que los agentes accedan a servicios SMTP e IMAP utilizando políticas de cuenta explícitas. Esto evita el acceso sin restricciones al garantizar que cada acción esté regida por reglas y metadatos predefinidos.
Los desarrolladores utilizan el MCP server de Arbiter a través de una API HTTP nativa y lo gestionan mediante la CLI arbiter-server. El sistema soporta el envío de SMTP con identidades de remitente y configuraciones TLS configuradas, junto con herramientas IMAP para gestionar carpetas y mensajes. Los usuarios pueden interactuar con el servicio en ejecución a través de la CLI nativa arbiter o apuntando integraciones locales como VS Code a la URL del servidor.
La configuración implica el arranque de configuraciones y la gestión de cuentas de servicio mediante objetos especializados como arbiter.account y arbiter.policy. La arquitectura soporta despliegues con Docker y permite un control granular sobre operaciones específicas como buscar, mover o eliminar mensajes IMAP dentro de carpetas delimitadas.
Qué puedes hacer con él
- 1Transmisión de correo controladaUn agente de IA puede enviar correos electrónicos con identidades de remitente específicas y cuerpos en HTML a través de una interfaz SMTP segura.
- 2Interacción gestionada de la bandeja de entradaUn desarrollador puede permitir que un agente busque, lea y organice correos electrónicos dentro de carpetas IMAP específicas.
- 3Acceso a servicios basado en políticasLos administradores pueden definir reglas de acceso estrictas para diferentes cuentas de servicio utilizando objetos de política especializados.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Configuración
IMAP_PRIMARY_ACCOUNT_HOSTIMAP_PRIMARY_ACCOUNT_PASSWORDIMAP_PRIMARY_ACCOUNT_USERNAMESMTP_PRIMARY_ACCOUNT_HOSTSMTP_PRIMARY_ACCOUNT_PASSWORDSMTP_PRIMARY_ACCOUNT_USERNAME
| Nombre | Descripción | Tipo |
|---|---|---|
| IMAP_PRIMARY_ACCOUNT_HOST | — | |
| IMAP_PRIMARY_ACCOUNT_PASSWORD | — | |
| IMAP_PRIMARY_ACCOUNT_USERNAME | — | |
| SMTP_PRIMARY_ACCOUNT_HOST | — | |
| SMTP_PRIMARY_ACCOUNT_PASSWORD | — | |
| SMTP_PRIMARY_ACCOUNT_USERNAME | — |
Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Aún no verificado. Un servidor necesita una puntuación de 80, ningún hallazgo grave y suficientes datos para que podamos revisarlo. Cómo funcionan las verificaciones · Qué corregir para obtener más puntos
- Repositorio de origen vinculado y accesibleomry/arbiter is public and reachablegithub.com/omry/arbiter ↗Aprobado
- El paquete indica este repositorio como su origenNo verificado
- Procedencia de la compilación (atestación de Sigstore)No verificado
- Licencia de código abierto (OSI)MITspdx.org/licenses/MIT.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit or release 2026-11-11github.com/omry/arbiter ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo verificado
- No hay avisos críticos en el paquete ni en sus dependenciasNo verificado
- Sin instrucciones ocultas para el modelo0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo verificado
- El endpoint remoto responde al handshake de MCPNo verificado
README
Ver en GitHubArbiter
| Description | |
|---|---|
| Meta packages | |
| Core packages | |
| Plugins | |
| Python | |
| Docs, support, and ecosystem | |
| General |
Arbiter is a capability firewall between AI agents and services. Today it exposes policy-controlled access through an Arbiter server and client CLI; additional interfaces may be added later. The current service surface covers sending mail over SMTP and reading IMAP folders through explicit account policies.
Project Status
Current implementation status:
- Arbiter server over a native HTTP API
- capability discovery with SMTP and IMAP account and operation metadata
- SMTP submission with configured sender identity, TLS/auth settings, text/HTML bodies, and Bcc kept out of message headers
- IMAP list/get/search/move/mark-read/delete tools scoped to configured accounts and folders
arbiter.account.<service>and reusablearbiter.policy.<service>objects for per-service account policy- native
arbiterclient CLI andarbiter-serverserver/operator CLI - Reploy blueprint material for staged and installed Docker deployments
Known open gaps:
- durable audit storage is parked for post-v1, while startup/runtime logging is the v1 observability focus
- normalized error-code responses are still a design contract, while the implementation currently surfaces Python and transport errors
- the agent-facing skill integration path is intentionally not implemented in this repository yet
Development
Create and use the repo-local virtualenv with:
python3 -m venv .venv.venv/bin/python -m pip install --upgrade pip.venv/bin/python -m pip install -r requirements-dev.txt
The repository root is a workspace, not an Arbiter runtime package. The dev
requirements file installs server, plugins/smtp, and plugins/imap
editably so the arbiter-server command and service plugins come from this
checkout.
Install the native client separately when you need the repo-local arbiter
command:
.venv/bin/python -m pip install -e client
Run the test suite from the repo root with:
.venv/bin/python -m nox -s tests.venv/bin/python -m nox -s lint
The lint session runs both black --check and pyrefly check.
For focused local runs without nox, use the same environment directly, for example:
.venv/bin/python -m pytest server/tests/unit/test_config.py.venv/bin/python -m pytest server/tests/unit/test_app.py
GitHub Actions references
External actions use full commit SHAs with version comments. Reusable workflows
also use full SHAs, with one explicit exception: the two Node maintenance calls
in .github/workflows/dependency-audit.yml follow
hydra-ecosystem/github-actions@v1 for automatic compatible fixes. This trusts
the release tag maintained by that repository. A different source, workflow,
caller, branch, or major release requires a separate policy update. Full SHA
references remain valid for maintenance too. See the shared
release policy.
The Docusaurus website lives in website/:
cd website && npm installcd website && npm run startcd website && npm run build
The native client implementation lives in client/go-cli/. Build all default release targets from the repo root with:
tools/build_go_client --clean
This writes stripped Linux, macOS, and Windows binaries for amd64 and arm64
under client/go-cli/dist/. Limit the matrix with one or more --target GOOS-GOARCH arguments, for example tools/build_go_client --target linux-arm64; pass --debug to keep debug symbols.
Package the platform-neutral agent skill with:
tools/build_release_dists --packages skill
This writes the platform-neutral arbiter-skill wheel under dist/. The skill
declares arbiter-client as an Agent Skill Installer companion wheel; ASI lets
pip select the current platform's native client wheel during install.
The native client can also be packaged as the arbiter-client PyPI project:
tools/build_release_dists --packages client
This builds one platform-tagged wheel per native target. Each wheel installs the
native arbiter executable directly as a wheel script; it does not contain a
Python wrapper.
The user-facing documentation lives in website/docs/. The root docs/ directory contains internal planning, security assessments, active designs and an archive of superseded drafts:
- docs/BACKLOG.md
- docs/testing_backlog.md
- docs/release-readiness.md
- Security assessment
- docs/future/
- Historical designs
Local Native HTTP Run
For local Codex or VS Code integration, run Arbiter over native HTTPS and point the client at:
https://127.0.0.1:8075
Arbiter does not ship a runnable service config. Bootstrap a Hydra
config, edit it, then run the server. Keep server-owned files together in a
deployment directory; for local development, arbiter-server/conf is a useful
repository-local config directory.
Plugin-owned object templates are created by the plugin command surface:
arbiter-server --config-dir ./arbiter-server/conf bootstrap --server
arbiter-server --config-dir ./arbiter-server/conf bootstrap --plugin smtp --account primary
${oc.env:...} reads the process environment that your shell, supervisor,
container runtime, or secret manager provides. For local runs, the root config
can name one optional dotenv-style file to load before composition.
See website/docs/operate/configuration-model.md for the generated file layout and composition flow.
For local development, the server env file lives beside conf/:
# arbiter-server/.arbiter.env
SMTP_PRIMARY_ACCOUNT_HOST=smtp.example.com
# SMTP_PRIMARY_ACCOUNT_PORT=587
SMTP_PRIMARY_ACCOUNT_USERNAME=agent@example.com
SMTP_PRIMARY_ACCOUNT_PASSWORD=change-me
IMAP_PRIMARY_ACCOUNT_HOST=imap.example.com
# IMAP_PRIMARY_ACCOUNT_PORT=993
IMAP_PRIMARY_ACCOUNT_USERNAME=agent@example.com
IMAP_PRIMARY_ACCOUNT_PASSWORD=change-me
Point the root config at the env file:
arbiter:
env_file: ../.arbiter.env
Existing process environment variables take precedence over values from the env file. Relative paths are resolved from the config directory.
Build or refresh that file from the active config:
arbiter-server --config-dir ./arbiter-server/conf env bootstrap
arbiter-server --config-dir ./arbiter-server/conf env check
env bootstrap keeps existing assignments, adds missing config references, and
groups entries under sorted # arbiter-* blocks plus # miscellaneous.
If arbiter.env_file is not set yet, it adds arbiter.env_file: ../.arbiter.env to the root config first.
Then run from this directory:
arbiter-server --config-dir ./arbiter-server/conf config check
arbiter-server --config-dir ./arbiter-server/conf serve
config check and serve require at least one configured service account.
Use arbiter-server plugins list to inspect installed service plugins before
validating a config. Once the server is running, point the client CLI at the
server URL. The client accepts Arbiter's local self-signed TLS certificates by
default; configure arbiter.tls_ca_file when you want certificate verification
against a specific certificate authority file:
arbiter info server arbiter.url=https://127.0.0.1:8075
arbiter plugins arbiter.url=https://127.0.0.1:8075
The client can also read the endpoint from a small config file:
~/.arbiter/arbiter-client.yaml.
arbiter:
url: https://127.0.0.1:8075
Override config values with Hydra-style key=value arguments after the
command, or bootstrap the client config:
arbiter bootstrap client arbiter.url=https://127.0.0.1:8075
IMAP operations use folder-scoped UIDs returned by imap:list_messages and
imap:search_messages; pass those ids back to imap:get_message,
imap:move_message, imap:mark_message_read, or imap:delete_message with
the same account and folder.
License
Arbiter is distributed under the MIT License. See LICENSE.
Preguntas sobre Arbiter MCP
¿Qué servicios soporta Arbiter actualmente?
La superficie de servicios actual incluye el envío de correos vía SMTP y la lectura de carpetas IMAP mediante políticas de cuenta explícitas.
¿Arbiter ofrece almacenamiento de auditoría?
El almacenamiento de auditoría duradero está pospuesto para después de la v1, pero el enfoque de la v1 para la observabilidad es el registro de inicio y de tiempo de ejecución.