External MCP servers and Marketplace

Agor can attach external MCP servers to individual sessions. Use Marketplace for reviewed remote endpoints, or Settings → MCP Servers for configurations you manage yourself.

Authentication

Marketplace checks the live endpoint before installing it. An entry may be:

Open: Agor connects it and opens a session ready to use.
OAuth: Agor creates the server and session first. Complete Sign in in that session or in MCP Server settings before sending the starter prompt. OAuth grants are per user.
Bearer token: Marketplace accepts this only when the checked-in catalog explicitly prescribes the reviewed bearer scheme. The token is verified against the catalog endpoint before storage. A generic 401 or 403 is not proof that a bearer token will work.
Unknown: Agor checks the endpoint at connect time. If it has changed to OAuth or open access, the drawer updates. An unreviewed custom-header, Basic, multi-key, or signed scheme is refused.

For unsupported schemes, configure the server in Settings → MCP Servers. Custom headers support services such as Datadog API/application-key pairs; Marketplace’s Datadog entry instead asks for the bearer PAT/SAT described in Datadog’s MCP setup guide.

Storage, reconnecting, and removal

Bearer tokens are stored in the installed MCP server’s auth configuration. Catalog installs are private to their owner, access controls restrict the row, and API and UI reads redact the token. Do not assume application-level encryption from those protections; encryption at rest applies only when the deployment’s documented database or storage configuration guarantees it. OAuth access and refresh tokens use Agor’s per-user OAuth token store.

Connecting an entry again opens a new session but reuses the same owner-specific install. Supplying a new bearer token verifies and atomically rotates that install; the previous token is not retained in another catalog row. Remove the MCP server in Settings → MCP Servers to delete Agor’s stored configuration and token. Also revoke the token or OAuth grant at the provider when access should end immediately.

Catalog curation for operators

The public catalog is packages/core/src/mcp-catalog/curated.yaml. auth_type is presentation policy, while live probing remains authoritative. Every credentials entry must include a reviewed credentials block with scheme: bearer, an accurate vendor acquisition_url, and an optional user-facing label. Never put a secret in the catalog.

Review the exact endpoint, redirect behavior, vendor authentication documentation, permission disclosure, and acquisition link. Do not classify a non-OAuth challenge as bearer support without that evidence. OAuth-specific compatibility fields are escape hatches and should be added only after reviewing the provider’s discovery behavior.