tramAI vs mcp-agent
AI workflow frameworks compared
tramAI is a Kotlin-first JVM runtime for typed AI workflows with configurable governance controls. mcp-agent is a Python framework for building agents around MCP servers and composable workflows, with optional Temporal execution. The main difference is tramAI’s focus on governing model and tool use inside JVM applications, versus mcp-agent’s focus on MCP integrations and agent workflow patterns.
tramAI: Govern AI Workflows on the JVM
TramAI is a Kotlin-first JVM runtime for typed AI workflows with configurable policy, provider routing, tool controls, approvals, and execution evidence. It suits teams that need governance around model use, not just a way to call an LLM.
mcp-agent: Build Agents with Model Context Protocol
A Python framework for building LLM agents around Model Context Protocol servers and composable workflow patterns. It suits developers who need MCP integrations, multi-agent workflows, or durable execution with Temporal.
| tramAI | mcp-agent | |
|---|---|---|
| Language | Kotlin | Python |
| License | Apache-2.0 | Apache-2.0 |
| Stars | 35 | 8.6k |
| Forks | 0 | 893 |
| Last analyzed | Oct 9, 2026 | Oct 3, 2026 |
Key differences
- tramAI is written in Kotlin for JVM applications, while mcp-agent is written in Python and uses asynchronous patterns in its examples.
- tramAI emphasizes configurable policy, data controls, provider routing, approvals, and execution evidence; mcp-agent emphasizes MCP server connections and reusable agent workflow patterns.
- mcp-agent includes routers, map-reduce, orchestrator-worker, and evaluator-optimizer patterns; tramAI defines AI operations through typed JVM interfaces with structured output and validation.
- mcp-agent supports asyncio or Temporal execution, with Temporal enabling durable workflows such as pause, resume, and retries; tramAI offers approval and continuation capabilities, with persistence and recovery options when configured.
- tramAI supports standalone and Spring Boot integrations and lists several provider adapters; mcp-agent can expose applications as MCP servers and offers configuration through YAML, environment variables, or Python settings.
- Both use Apache-2.0. tramAI’s README describes its 0.6.x line as frozen for bug and security fixes, while mcp-agent’s cloud deployment is described as beta.
Choose tramAI if you…
- need typed AI workflows inside a Kotlin or Spring Boot application.
- want configurable controls for provider routing, sensitive actions, approvals, and execution evidence.
- are building on the JVM and can assess evolving APIs and configure the relevant governance components.
Choose mcp-agent if you…
- need Python agents that connect to MCP servers and compose reusable workflow patterns.
- want asyncio execution or durable workflows through Temporal.
- want to expose an application or agent as an MCP server.
Compare the numbers side by side, or add more projects
This comparison is generated with AI from the OSRepos analyses of both projects. Always check each project's repository and documentation before choosing.