Open-source MCP router from Klavis AI that progressively exposes actions from multiple configured MCP servers instead of flooding Claude with every tool.
Open the source and read safety notes before installing.
Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.
Decision playbook
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
0
63
—
No baseline selected
No major trust-signal divergence detected in the current selection.
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Source provenance statusRequired
Marked as source-backed.
Metadata reviewed
No reviewed flag detected in metadata.
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Trust level risk gateRequired
Trust level does not block evaluation.
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Package verification flag
No package verification flag provided.
Checksum metadata
No checksum provided for downloaded artifact.
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
Baseline comparison available
No baseline peer selected yet.
Diverging trust signals identified
No major trust-signal divergence found.
Setup at a glance
Copy-ready — paste the snippet to get started.
Adoption plan
Current risk score 24/100. Use staged verification before broader rollout.
Validate source and review signals before any execution.
Confirm source provenanceRequired
Source URL/provenance metadata is present.
Confirm metadata review state
No review metadata found; increase manual validation.
Verify install payload
Install/config payload exists and can be inspected.
Confirm safety, privacy, and package integrity signals.
Review safety notesRequired
Safety notes are present.
Review privacy notesRequired
Privacy notes are present.
Verify package integrity metadata
No package verification/checksum metadata.
Adopt in controlled steps based on the selected plan.
Run in isolated sandbox firstRequired
Use a constrained sandbox and observe behavior across multiple tasks.
Roll out graduallyRequired
Roll out to a small cohort before wider usage.
Set monitoring and fallback
Define rollback path and monitor errors after adoption.
Evidence readiness
Missing required evidence: Metadata review. Risk score 31.
Source repository/provenance is listed.
Required in this preset
Review metadata is missing.
Required in this preset
Safety notes are present.
Required in this preset
Privacy notes are present.
Optional in this preset
Package integrity metadata is missing.
Optional in this preset
Install payload is available.
Required in this preset
Required gaps: Metadata review
Decision timeline
Blocking gaps: Check metadata review status. Risk 28.
triage
Source/provenance metadata is available.
triage
Review metadata is missing.
verify
Safety notes are available.
verify
Privacy notes are available.
verify
Package integrity metadata is missing.
rollout
Install payload is available.
Blockers: Check metadata review status
Prerequisite readiness
5 prerequisites to line up before setup. Have accounts and credentials ready first.
Safety & privacy surface
5 safety and 4 privacy notes across 5 risk areas. Review closely: credentials & tokens, network access, third-party handling.
Disclosure: Klavis AI also offers hosted MCP integration APIs and managed Strata services; this entry focuses on the open-source `strata-mcp` router in the public repo.
{
"mcpServers": {
"strata": {
"command": "strata"
}
}
}Klavis Strata is an open-source MCP router that sits between Claude and a set of configured MCP servers. Instead of exposing every downstream tool at once, it provides a smaller set of discovery, inspection, execution, documentation search, and authentication helper tools.
The open-source implementation lives under open-strata in the Klavis
repository and is published as the strata-mcp Python package. It can run in
stdio mode for local MCP clients or in HTTP/SSE mode for deployments that need a
network transport.
These sources were reviewed on 2026-06-05. Prefer the live repository, open-strata README, package metadata, router source files, PyPI metadata, and Klavis docs for current install commands, router modes, tool names, supported transports, and hosted-service boundaries.
strata CLI.Install the open-source router package:
pipx install strata-mcp
Add trusted downstream MCP servers with the Strata CLI. For example, a stdio server can be registered by name:
strata add --type stdio playwright npx @playwright/mcp@latest
Then configure Claude to launch Strata:
{
"mcpServers": {
"strata": {
"command": "strata"
}
}
}
For HTTP or SSE downstream servers, use private endpoint placeholders and secret-managed headers rather than committing real bearer tokens or URLs into project files.
Strata concentrates access to many downstream tools. That is useful for context management, but it also means one MCP server entry can route to high-impact actions across files, browsers, SaaS APIs, databases, developer tools, and other systems. Audit each downstream server independently and keep the enabled set as small as the task allows.
The open-source source code stores server configuration in a local JSON file and supports headers and environment variables for downstream servers. Treat this configuration as sensitive. The HTTP/SSE router mode should be deployed behind appropriate network controls because it can expose access to every enabled server action.
No Klavis-AI/klavis, strata-mcp, Klavis Strata, or matching source URL was
found in content/mcp.
Show that Klavis Strata MCP Router is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/klavis-strata-mcp-router)Klavis Strata MCP Router side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
1 trust signal differ across this comparison (Submitter).
| Field | Open-source MCP router from Klavis AI that progressively exposes actions from multiple configured MCP servers instead of flooding Claude with every tool. Open dossier | Open-source MCP servers for accessing ACI.dev managed functions through app-specific tools or a unified search-and-execute interface. Open dossier | Remote Agentage Memory MCP server giving Claude one shared, portable memory across every AI you use - search, read, write, edit, list, and delete plain Markdown notes you own, over Streamable HTTP with OAuth 2.1. Open dossier | Apache-2.0 agentic proxy that can expose stdio, HTTP, SSE, and Streamable HTTP MCP servers through a managed gateway with federation, OAuth/JWT authentication, RBAC/CEL policy, CORS, TLS, observability, and Kubernetes Gateway API support. Open dossier |
|---|---|---|---|---|
| Next steps | ||||
| Trust | ||||
| Review status | Not reviewed | Not reviewed | Not reviewed | Not reviewed |
| Package trust | Package not verified | Package not verified | Package not verified | Package not verified |
| Source provenance | Source-backed | Source-backed | Source-backed | Source-backed |
| SubmitterDiffers | oktofeesh1 | oktofeesh1 | vreshch | oktofeesh1 |
| Install risk | Review first | Review first | Review first | Review first |
| Notes | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ | Safety ✓ Privacy ✓ |
| Brand | ||||
| Category | mcp | mcp | mcp | mcp |
| Source | Source-backed | Source-backed | Source-backed | Source-backed |
| Author | Klavis AI | Aipolabs | agentage | agentgateway |
| Added | 2026-06-05 | 2026-06-05 | 2026-06-18 | 2026-06-06 |
| Platforms | ||||
| Harness | ||||
| Source repo | — | — | — | — |
| Safety notes | ✓Strata can execute tools on every enabled downstream MCP server; treat it as a privileged router, not a harmless discovery layer. Review each downstream server before adding it, because Strata can route file, browser, database, SaaS, shell, or write-capable actions through one interface. The HTTP/SSE mode starts an ASGI server and the source currently binds uvicorn to all interfaces; restrict network exposure with firewall rules, reverse proxies, or local-only deployment. Store bearer tokens, OAuth credentials, headers, and environment variables in a secret manager or private config file rather than committing Strata configuration. Disable or remove servers that should not be available to a specific project, user, or model session. | ✓The unified server can discover and execute many ACI.dev managed functions, so restrict permissions before connecting it to an autonomous agent. App-specific servers should be preferred when a workflow only needs a small set of integrations. Connected apps may read, create, update, delete, or send data depending on the selected functions and linked account permissions. Require human approval before email, calendar, CRM, ticketing, infrastructure, billing, deployment, or account-administration actions. | ✓The memory__write, memory__edit, and memory__delete tools create, modify, and remove your stored notes; review actions before granting broad access. | ✓Agentgateway can aggregate and expose many downstream MCP targets through one endpoint; every target's permissions become part of the gateway surface. Stdio targets are spawned by the gateway process, so commands such as package runners or containers inherit the gateway host's trust boundary. Demo configs use permissive CORS and local authorization servers; lock down origins, headers, issuers, audiences, JWKS, and resource metadata before production use. CEL/RBAC policies can inspect MCP tool names, arguments, results, prompts, resources, request bodies, JWT claims, API keys, and backend metadata; test policies before relying on them. Remote MCP proxying, OAuth provider adaptation, Kubernetes routing, TLS termination, and guardrails are infrastructure changes that should go through normal security review. |
| Privacy notes | ✓Strata stores configured server names, commands, URLs, headers, and environment variables in a local JSON configuration file. User prompts, action discovery queries, tool schemas, tool arguments, and downstream server responses can all become visible to the MCP client and model provider. Routed tools may expose third-party account data, files, repositories, browser state, database rows, or workspace context depending on which servers are enabled. Hosted Klavis APIs and SDKs are separate from the local open-source router; review Klavis account, API-key, and data-handling terms before using hosted instances. | ✓Tool names, function arguments, prompts, linked account identifiers, execution results, logs, and connected-service data may pass through ACI.dev, the selected third-party apps, the MCP client, and the model provider. API keys and linked-account credentials must be protected in client config, environment files, logs, screenshots, and shared prompts. Review ACI.dev account, tenant, retention, audit-log, and OAuth settings before routing production or customer data through the server. | ✓Notes you read or write are stored server-side in your Agentage Memory and mirrored locally as Markdown you can export anytime; note contents pass through model context. | ✓MCP requests, tool arguments, tool results, prompt names, resource names, session IDs, JWT/API-key claims, raw request/response bodies, logs, traces, and telemetry may pass through the gateway. CEL policy and observability features may buffer or inspect request and response bodies depending on configuration. OAuth/JWT metadata, bearer tokens, API keys, DCR secrets, Keycloak/Auth0/Okta settings, and upstream MCP credentials must be protected as secrets. Any data returned by downstream MCP tools can still be sent onward by the MCP client to the configured model provider. |
| Prerequisites |
|
|
|
|
| Install | | | | |
| Config | | | | |
| Citations | ||||
| Claim | Unclaimed | Unclaimed | Unclaimed | Unclaimed |
Connect Claude and other MCP clients to ACI.dev managed functions through unified or app-specific MCP servers.
One memory for every AI - search, read, and write Markdown notes you own, from Claude over OAuth.
Put agentgateway in front of MCP tools to aggregate multiple targets, proxy remote servers, spawn stdio servers, serve Streamable HTTP and SSE endpoints, and add auth, policy, telemetry, guardrails, and Kubernetes-native routing.
Source-backed guides for putting this to work.
Write a claude-code-hint tag to stderr under CLAUDECODE, and Claude Code prompts users once to install your official-marketplace plugin.
Loading live community signals…
A short, calm digest of reviewed Claude resources. Unsubscribe any time.