composio vs adk-recipes

Two of the top projects in Agent and MCP starters, side by side: who leads on each score part and who each one suits, then setup, license, activity and what each review found.

22nd of 74 in Agent and MCP starters

composio

TypeScript and Python SDKs that give agents authenticated tools across 1000+ apps

#1515th of 74 in Agent and MCP starters

adk-recipes

Runnable Agent Development Kit recipes, from single patterns to deployable agents

Verdict

composio ranks higher, 93 to 76. Of the 4 score parts we measure for both, composio leads on 3, adk-recipes on none and 1 is even.

  • Adoptioncomposio leads by 12 points, 94 to 82.
  • FreshnessEven at 100.
  • Maintenancecomposio leads by 26 points, 87 to 61: a wide gap.
  • Agent-readycomposio leads by 55 points, 85 to 30: a wide gap.

Pick composio if you are

Developers wiring agents to third-party apps with managed per-user auth

  • Adapters for about 16 frameworks, including OpenAI Agents, Claude Agent SDK, LangChain and Mastra
  • Per-user sessions handle authentication, so the agent does not manage OAuth flows

Pick adk-recipes if you are

Teams standardizing on ADK and Google Cloud

  • Core recipes isolate one pattern each, so they lift cleanly into your project
  • Vertical agents include deploy paths to Agent Engine and Cloud Run
composio vs adk-recipes: score parts and facts
What we comparecomposioadk-recipes
Score parts, out of 100
Adoption94, widely used82, widely used
Freshness100, active100, active
Maintenance87, healthy61, fair
Agent-ready85, ready30, minimal
Facts from GitHub and the README
Stars31.2k10.6k
LicenseMIT (permissive)Apache-2.0 (permissive)
Last commitNov 2026Nov 2026
Last releaseNov 2026None published
LanguageTypeScriptPython
DockerNoNo
GPUNot neededNot needed
arm64 or Apple SiliconMentionedNot stated

composio

Composio is an SDK monorepo (TypeScript, Python, and a CLI) that creates per-user sessions exposing pre-authenticated toolkits to an agent. Sessions default to meta tools that discover, authenticate and execute app tools at runtime, and can also be served through a hosted MCP endpoint. Provider adapters convert the tools to the formats of OpenAI, Anthropic, LangChain, Vercel AI SDK, Google ADK, CrewAI and others.

Who it is for: Developers wiring agents to third-party apps with managed per-user auth

Strengths

  • Adapters for about 16 frameworks, including OpenAI Agents, Claude Agent SDK, LangChain and Mastra
  • Per-user sessions handle authentication, so the agent does not manage OAuth flows
  • Meta tools load tools at runtime instead of putting hundreds of definitions in context
  • Each session can also be exposed as a hosted MCP URL for Claude, Cursor or other clients

Weaknesses

  • Requires a COMPOSIO_API_KEY from the hosted dashboard; the README documents no self-hosted option
  • The SDK is open source, but toolkits and auth run through Composio's service
  • Provider coverage is uneven: Vercel and Mastra are TypeScript only, CrewAI and AutoGen Python only
  • Pi provider is experimental and ships from a separate package
  • TypeScript, OpenAI, Anthropic, Google GenAI, LangChain
  • Needs Composio API key (hosted service), Node 22+ for TypeScript SDK, Python 3.10+ for Python SDK

adk-recipes

A recipe collection for Google's Agent Development Kit: core/ holds single-pattern agents (OAuth flows, session memory, guardrails, RAG), contrib/ holds deployable vertical agents targeting Agent Engine, Cloud Run and Gemini Enterprise, and plugins/ holds skills packaged with SKILL.md and EVAL.yaml. Each recipe has its own README; ADK SDKs exist for Python, TypeScript, Go, Java and Kotlin. For teams standardizing on ADK and Google Cloud.

Who it is for: Teams standardizing on ADK and Google Cloud

Strengths

  • Core recipes isolate one pattern each, so they lift cleanly into your project
  • Vertical agents include deploy paths to Agent Engine and Cloud Run
  • Recipe checklist and handbook define a contribution standard; tests and AGENTS.md included
  • Committed within the last day

Weaknesses

  • Root README is an index; no single app, no shared setup
  • Gemini and Google Cloud are the assumed model and deploy target
  • README states recipes are demonstrations, not for production use
  • Mixed languages and maturity across folders
  • Python, google, google-adk
  • Needs google-adk, google-api-key-or-vertex-ai

More in Agent and MCP starters

Building with these?

We help teams pick an open-source AI stack and run it in production. Client work never changes a rank.