15 new capabilities across MCP transport, caching, agent orchestration,
key management, enterprise identity, and policy compliance.
Any MCP server using streaming push notifications — real-time data feeds, live monitoring tools, event-driven integrations — can now be registered and used through Smartflow.
The entire catalogue of standard community MCP servers — GitHub CLI, filesystem access, local databases, shell tools — all of which run as STDIO processes. This was the largest gap in MCP transport coverage.
Server URLs and configurations can change without breaking integrations. Teams use human-readable names (github, internal-search) rather than raw server IDs throughout their tooling.
Dynamic tool discovery for agents and orchestrators. Finding capabilities by intent rather than hard-coded names. Useful for inspecting large MCP deployments and building intent-driven routing logic.
no-cache (bypass read),
no-store (bypass write), custom ttl,
and namespace for scoping entries.
Applications mixing cacheable and non-cacheable calls — deterministic queries alongside real-time lookups that must never be served stale — can handle both in the same integration without separate configurations.
x-smartflow-cache-key
header containing the resolved cache key.
Clients can implement their own cache invalidation, debug cache behaviour, or correlate requests to cached entries for cost attribution and auditing.
Enterprise MCP servers protected by an identity provider (Azure AD, Okta, Auth0) can be registered and used without callers managing OAuth tokens themselves.
x-mcp-{alias}-{header-name} headers. Smartflow extracts and
forwards them only to the intended server, and strips them before the request reaches the end LLM.
User-specific or request-specific credentials (session tokens, scoped API keys) forwarded to MCP servers without central storage. Credentials are scoped strictly by alias — no leakage between servers.
Connecting personal SaaS accounts to MCP tools — GitHub, Google Workspace, Slack, and any OAuth provider — where each user authorises with their own identity. Tokens are scoped per user and server, expire independently, and are never shared.
sk-sf-...) now carry hard spend limits.
Budgets are checked before every request — if the limit is reached the request returns429 with X-Smartflow-Budget-Remaining
before any cost is incurred. Spend is recorded after each response using actual token cost.
Budget periods reset automatically.
Per-user, per-team, or per-application spend caps with automatic enforcement. Budget periods (daily, weekly, monthly, lifetime) reset automatically. Issue keys to internal users or external partners with full cost control and no surprise invoices.
High-availability LLM routing with no single point of failure. Automatic handling of rate limits and provider outages. Multi-provider redundancy configurable per model or use case without any application-level changes.
External agent systems (LangGraph, Vertex AI, Azure AI Foundry, Bedrock AgentCore, Pydantic AI) can connect to Smartflow-hosted agents without custom integration code. Cross-agent tracing via X-A2A-Trace-Id links task chains across services. Task history persisted in Redis for replay and audit.
/cursor/* are treated as OpenAI-compatible calls;
requests at /anthropic/*are forwarded natively to Anthropic.
Provider detection is automatic from the model name —claude-* routes
to Anthropic, gemini-* to Google. The [1m]
extended-context suffix Claude Code injects into model names is stripped automatically.
Route every developer's Cursor or Claude Code session through Smartflow for centralised logging, budget enforcement, virtual key management, and policy application — with zero changes on the client side. SetANTHROPIC_BASE_URL=https://mcp.langsmart.app/anthropic and you're done.
id_token, extracts
the user's Entra group memberships and App Role claims, and automatically creates or updates corresponding
Smartflow teams in Redis. Users are added to teams they belong to and removed from teams they have left.
App Role values map to internal roles:
proxy_admin, org_admin,
proxy_admin_viewer, internal_user.
Zero-touch team provisioning from Entra ID — no manual group-to-team mapping. Access controls, budgets, and guardrail policies attached to teams take effect immediately when group membership changes in Entra. Works with any OIDC-compatible IdP that includesgroups and roles claims.
health-*) — and
evaluated on every proxied request. Matched policies are merged into the Maestro pre/post
validation pipeline. Results are surfaced in response headers.Org-wide compliance baselines with team- or product-level overrides. Apply the right guardrail set to the right requests automatically, without code changes. Tag-based scoping means attaching a policy to all hipaa-* keys takes a single API call. The resolve endpoint lets you preview exactly which guardrails would fire for any given request context before deploying.
| # | Feature | Area |
|---|---|---|
| 01 | MCP SSE Transport | MCP Gateway |
| 02 | MCP STDIO Transport | MCP Gateway |
| 03 | Per-Request Cache Controls | Caching |
| 04 | Cache Key in Response Header | Caching |
| 05 | MCP Server Aliases | MCP Gateway |
| 06 | OAuth Client Credentials for MCP | MCP Auth |
| 07 | Per-Server Auth Header Forwarding | MCP Auth |
| 08 | Virtual Key Budget Enforcement | Key Management |
| 09 | Load Balancing with Fallback & Retry Chains | Routing |
| 10 | Semantic Tool Search | MCP Gateway |
| 11 | A2A Agent Gateway | Agent Orchestration |
| 12 | OAuth PKCE Browser Consent for MCP | MCP Auth |
| 13 | Claude Code / Cursor Passthrough | IDE Routing |
| 14 | Microsoft Entra ID SSO Group Sync | Enterprise IAM |
| 15 | Guardrail Policy Groups with Inheritance | Policy & Compliance |