Arbiter MCP server
Commit 11 Nov 2026Menyediakan capability firewall yang memungkinkan AI agent berinteraksi dengan layanan seperti SMTP dan IMAP melalui akses yang dikontrol oleh kebijakan.
Juga dikenal sebagai omry/arbiter
- Stars
- 3
- Tools
- —
- Unduhan, 30 hari
- —
- Versi terbaru
- —
- Commit terakhir
- 11 Nov 2026
- Lisensi
- MIT
Apa itu Arbiter MCP?
Menyediakan capability firewall yang memungkinkan AI agent berinteraksi dengan layanan seperti SMTP dan IMAP melalui akses yang dikontrol oleh kebijakan.
Ringkasan dibuat dari README proyek
Tentang Arbiter MCP server
Arbiter memungkinkan pengamanan interaksi AI agent dengan layanan email melalui capability firewall. Sistem ini menyediakan cara yang terkontrol bagi agent untuk mengakses layanan SMTP dan IMAP menggunakan kebijakan akun yang eksplisit. Hal ini mencegah akses tanpa batas dengan memastikan setiap tindakan diatur oleh aturan dan metadata yang telah ditentukan sebelumnya.
Developer dapat menggunakan Arbiter server melalui native HTTP API dan mengelolanya menggunakan arbiter-server CLI. Sistem ini mendukung pengiriman SMTP dengan identitas pengirim dan pengaturan TLS yang telah dikonfigurasi, serta tool IMAP untuk mengelola folder dan pesan. Pengguna dapat berinteraksi dengan layanan yang sedang berjalan melalui native arbiter client CLI atau dengan mengarahkan integrasi lokal seperti VS Code ke URL server.
Setup melibatkan bootstrapping konfigurasi dan pengelolaan service account melalui objek khusus seperti arbiter.account dan arbiter.policy. Arsitekturnya mendukung deployment Docker dan memungkinkan kontrol granular atas operasi spesifik seperti mencari, memindahkan, atau menghapus pesan IMAP di dalam folder yang telah ditentukan cakupannya.
Apa yang bisa Anda lakukan dengannya
- 1Transmisi email terkontrolAI agent dapat mengirim email dengan identitas pengirim tertentu dan body HTML melalui interface SMTP yang aman.
- 2Interaksi inbox yang terkelolaDeveloper dapat mengizinkan agent untuk mencari, membaca, dan mengatur email di dalam folder IMAP tertentu.
- 3Akses layanan berbasis kebijakanAdministrator dapat menentukan aturan akses yang ketat untuk berbagai service account menggunakan objek policy khusus.
Ditulis berdasarkan README proyek. Setiap use case diperiksa terhadap kutipan dari README tersebut.
Konfigurasi
IMAP_PRIMARY_ACCOUNT_HOSTIMAP_PRIMARY_ACCOUNT_PASSWORDIMAP_PRIMARY_ACCOUNT_USERNAMESMTP_PRIMARY_ACCOUNT_HOSTSMTP_PRIMARY_ACCOUNT_PASSWORDSMTP_PRIMARY_ACCOUNT_USERNAME
| Nama | Deskripsi | Tipe |
|---|---|---|
| IMAP_PRIMARY_ACCOUNT_HOST | — | |
| IMAP_PRIMARY_ACCOUNT_PASSWORD | — | |
| IMAP_PRIMARY_ACCOUNT_USERNAME | — | |
| SMTP_PRIMARY_ACCOUNT_HOST | — | |
| SMTP_PRIMARY_ACCOUNT_PASSWORD | — | |
| SMTP_PRIMARY_ACCOUNT_USERNAME | — |
Pengecekan otomatis
Berjalan 14 Nov 2026Laporan lengkap →Belum diverifikasi. Sebuah server memerlukan skor 80, tidak ada temuan serius, dan data yang cukup untuk kami periksa. Cara kerja checks · Yang perlu diperbaiki untuk menambah poin
- Source repository terhubung dan dapat dijangkauomry/arbiter is public and reachablegithub.com/omry/arbiter ↗Lolos
- Nama paket mencantumkan repositori ini sebagai sumbernyaTidak diperiksa
- Provenance build (atestasi Sigstore)Tidak diperiksa
- Lisensi open source (OSI)MITspdx.org/licenses/MIT.html ↗Lolos
- Ada commit atau release dalam satu tahun terakhirLast commit or release 2026-11-11github.com/omry/arbiter ↗Lolos
- OpenSSF ScorecardTidak diperiksa
- Nama package tidak mirip dengan package populerTidak diperiksa
- Tidak ada advisory kritis pada paket atau dependensinyaTidak diperiksa
- Tidak ada instruksi tersembunyi untuk model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersLolos
- Tools yang bersifat destruktif telah diberi labelTidak diperiksa
- Endpoint remote merespons handshake MCPTidak diperiksa
README
Lihat di 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.
Pertanyaan tentang Arbiter MCP
Layanan apa saja yang saat ini didukung oleh Arbiter?
Cakupan layanan saat ini mencakup pengiriman email melalui SMTP dan pembacaan folder IMAP melalui kebijakan akun yang eksplisit.
Apakah Arbiter menyediakan penyimpanan audit?
Penyimpanan audit yang tahan lama (durable audit storage) saat ini dijadwalkan setelah v1, namun fokus v1 adalah pada logging saat startup dan runtime untuk observabilitas.