stdio · SSE

MCP

Plug in Model Context Protocol servers — browsers, issue trackers, internal APIs — without a marketplace.

MCP is how Eyeban grows beyond the built-in tools. You wire servers in JSON; the agent discovers their tools and can call them with the same permission loop as Shell or Git.

How you attach a server

  • User scope: ~/.eyeban/mcp.json
  • Project scope: .eyeban/mcp.json

Stdio servers and SSE / streamable HTTP servers both work. Resources and auth flows are supported when the server exposes them.

Why buyers care

A coding agent that cannot reach Jira, the browser, or your internal API stops at the repo boundary. MCP is that boundary crossing — still reviewed, still local to your config.

Trust

Prefer servers you can audit. Do not commit tokens. Read the tool schema before Allow all. There is no curated Eyeban store and no unsigned “plugin pack” to install from the internet.

Project-scoped MCP is useful when the whole team should share the same wiring.

Eyeban · shop/checkout.py Balanced
41 def charge(order, wallet):
42     tax = order.subtotal * 0.09
43     total = order.subtotal + tax
44     if wallet.balance < total:
45         raise InsufficientFunds(total)
46     wallet.debit(total)
47     return Receipt(order.id, total)

Split regional tax from the hardcoded rate, and check coverage before debit.

Read 6 files · 2 searches · 1 test

charge still hard-codes 0.09. tax_for(region) exists. I will wire can_cover to the wallet.

12-line patch across two files. Review the diff.

main Agent Balanced You stay in review