Fern (Public API) integration for AI agents.
Fern (Public API) integration for AI agents with secure authentication and server-side credential injection. Open Connector runs the OAuth, seals the token in an encrypted vault, and serves Fern (Public API) tools to your agent over MCP or a typed API — credentials injected server-side, every call audited, nothing leaving your infrastructure. Open source (AGPL-3.0) and self-hostable.
Real Fern (Public API) actions, managed and audited.
Your user connects Fern (Public API) once; your agent can then secure AI-agent actions — scoped to the OAuth permissions you grant and the tool allowlist you configure. Every action is least-privilege and written to a tamper-evident audit trail.
- 1
Your user grants Fern (Public API) access once (OAuth) — the token lands in the vault.
- 2
Your agent calls a tool over MCP or the typed API; Open Connector injects the credential server-side.
- 3
Every routed call appends a hash-chained audit record — nothing leaves your infra.
Supported Fern (Public API) tools.
0 tools are generated from the published Fern (Public API) catalog. Descriptions are plain text; each action remains subject to its configured authentication and tool allowlist.
Showing 0 tools. All published catalog entries are included in this page's server-rendered HTML.
No tools match “”.
Fern (Public API) integration, answered
- How do AI agents use Fern (Public API) through Open Connector?
- Your user connects Fern (Public API) once with one of its cataloged authentication methods. Open Connector stores the credential in an encrypted vault and exposes Fern (Public API) tools to your agent over MCP or a typed API, with credentials injected server-side on each call.
- Is this a Fern (Public API) MCP server?
- Yes. Open Connector can serve Fern (Public API) as a named MCP server with a scoped allowlist and a per-user connection URL, so any MCP client can call Fern (Public API) actions with credentials injected server-side.
- Where do Fern (Public API) credentials live?
- In your own infrastructure. Open Connector keeps credentials in its own vault and injects them at call time, so they never leave your environment.
Give your agents Fern (Public API) — keep the keys.
Open source, self-hostable, with Fern (Public API) credentials that never leave your infrastructure. Run it from source today.