Sixty-four tools over the Model Context Protocol. A terminal CLI for everything. A reusable skill marketplace. OAuth 2.1 with PKCE for any agent client. Bring Claude, ChatGPT, or your custom agent — they all see the same substrate, governed by the same trust posture.
Sixty-four typed tools exposed over MCP 2025-03-26 Streamable HTTP. OAuth 2.1 with auto-discovery, dynamic registration, refresh tokens. Bring any MCP-compatible client — Claude Code, ChatGPT, custom agents. Same authentication, same governance, same audit trail across all of them.
Every MCP tool has a terminal equivalent. Context loading, capability execution, document and knowledge management, system introspection. Scripting-friendly JSON output. Endpoint override for local development against a self-hosted instance.
Generic-first skills: a "send email" skill exists once and configures per use. New apps inherit the entire library. Custom skills go through the same security review as built-in ones. No second-class extensions — the marketplace is the platform.
Most platforms expect you to build a connector for each tool you integrate. Different authentication, different schemas, different error handling. The connector backlog grows; the maintenance burden compounds.
Meridian speaks Model Context Protocol — the open standard for agent-tool communication. Any MCP-compatible client connects with three fields of configuration. The auth flow is OAuth 2.1 with discovery; the token lifecycle is automatic. New tools that join the MCP ecosystem inherit the integration the day they ship.
Chat interfaces are good for exploration. Production automations need scriptability — exit codes, JSON output, deterministic argument handling. AI agents that work through a chat interface are slow and expensive for repetitive tasks.
The Meridian CLI exposes every capability as a scriptable command. Pipe-friendly. JSON output for parsing. Exit codes for control flow. The same operations a chat agent performs are reachable from a shell, a CI pipeline, or a cron job. Same authentication. Same audit. Same governance.
The standard answer is a shared library that everyone imports — and then everyone's version drifts when one team needs a special case. Three implementations later, none of them are quite right.
Meridian's skill marketplace inverts the pattern. Generic skills are first-class objects. The "send email" skill is one entity in the system, governed by one set of policies, audited under one identity model. Every app that needs email references the same skill with different configuration. There is one place to fix a bug. There is one place to add multi-region support. The compounding effect is that every app you build adds capability the next app can borrow.
Most AI platforms have a privileged surface for "official" integrations and a degraded surface for "third-party" ones. The official surface gets full features, full auth, full support. The third-party surface gets webhooks and best wishes.
Meridian has one surface. The Model Context Protocol is open. The OAuth flow is standard. The governance posture is the same whether the caller is the official Meridian web UI, a customer's terminal CLI, or a partner's agent client. Custom skills go through the same security review and registration process as the built-in marketplace. Custom apps deploy through the same factory as Meridian's own apps. There is no privileged caller. There is no second-class integration.
The implication is that what you build on Meridian is a first-class citizen of the substrate. Your custom app inherits cryptographic compartmentalization. Your custom skill inherits audit. Your custom agent client inherits the trust posture. You don't bolt safety onto your integration. You build on a platform that enforces it for you.
"You came here to integrate. By the time you go to production, you'll discover the integration surface is the same surface that runs Meridian itself — and your custom logic gets the same audit, governance, and compartmentalization that the built-in capabilities do."
Seven other domains running on the same substrate
Get a private walkthrough of the developer surface.