What strata MCP server does
The strata MCP server provides a way to organize access to multiple MCP servers for an AI agent. Its purpose is progressive tool usage: an agent can work with selected connectors while avoiding an unnecessarily large tool and context surface.
The repository presents Strata alongside Klavis MCP integrations and MCP Sandbox. Strata itself is the connector layer. Examples in the quick start combine Gmail and Slack in one Strata server, while another example creates a standalone Gmail server instance.
The available integrations depend on the servers selected when the Strata instance is created. The supplied examples identify Gmail and Slack, but do not provide a complete catalog of supported servers.
How it works
Strata can be used through several delivery paths. Klavis provides a hosted option at klavis.ai. For local use, the open-source package is installed with pipx, then its add command registers an MCP server. The documented local example adds Playwright as a stdio server launched through npx.
Applications can provision Strata through the Klavis Python or TypeScript SDK. Both examples create a Strata server for a user and pass a list of MCP server names. The SDKs also support creating an individual server instance instead of a combined Strata server.
The REST API exposes equivalent operations. A POST request to the Strata endpoint supplies a user identifier and server names, while a separate instance endpoint creates one MCP server. API requests use a Klavis API key in the authorization header.
Setup and configuration
For a local strata MCP server, install the package with pipx install strata-mcp. The documented command is then strata add --type stdio playwright npx @playwright/mcp@latest. This configures a stdio connection to the Playwright MCP server; the excerpt does not describe additional local configuration files or environment variables.
The cloud and API approaches require a Klavis API key. SDK examples pass the key when constructing the client, and the REST example sends it as a bearer token. Provisioning also uses a user_id and a list of MCP server names, such as GMAIL and SLACK.
The repository also shows a Docker path for running an individual GitHub MCP server on port 5000. That command demonstrates the broader Klavis MCP integration option rather than a documented Strata-specific container.
Tools and capabilities
- Combine selected MCP server integrations in a Strata instance.
- Create individual MCP server instances when aggregation is not needed.
- Add stdio MCP servers from the local command line.
- Provision servers through Python and TypeScript SDKs.
- Provision Strata or individual instances through REST endpoints.
- Use hosted Klavis deployment or run the open-source CLI locally.
Limitations and notes
The provided material does not list every available integration, define Strata’s internal routing behavior, or describe authentication flows for individual third-party services. It also does not specify a fixed tool catalog exposed by the strata MCP server. Confirm the current Klavis documentation for supported server names and deployment details before building against a specific integration.
The README names no MCP client, so client-specific compatibility is not established by the supplied material. The local example uses stdio, while the hosted and API examples rely on Klavis infrastructure and credentials.