Score8.4
Popularity0.0
Risklow
TierGold
Score breakdown
Usefulness9.0
Novelty8.0
Momentum8.0
Maturity6.6
Open-source/build8.4
Evidence7.2
Workflow potential9.5
Setup ease8.8
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Most AI agent developers today who need to wire integrations to multiple agents (Claude Code + Cursor + ChatGPT + custom agents) wire per-agent MCP integrations (one for Claude Code, one for Cursor, one for ChatGPT, one for each custom agent), repeat auth + per-tool policies in each agent, and rebuild the integration layer on every new agent. UsefulSoftwareCo/executor inverts that pattern: a singl
Who should use it
AI agent developers, MCP-compatible agent users, Claude Code / Cursor / ChatGPT users, integration developers, OpenAPI / GraphQL users, security-conscious users, AI-curious readers tracking the MCP / agent-tool space, engineering teams wiring MCP integrations to their agent fleet, and any developer wiring a unified integration layer + per-tool policies + multi-agent MCP sharing to their agent workflow -- and who can pair UsefulSoftwareCo/executor with the Executor Cloud for the cloud-runtime surface, the Local CLI for the local-runtime surface, the Desktop App for the desktop-runtime surface, the Self-hosted on Docker for the docker-runtime surface, the Self-hosted on Cloudflare for the cloudflare-runtime surface, the `npm install -g executor` install for the npm-surface install, the `pnpm add -g` install for the pnpm-surface install, the `bun add -g` install for the bun-surface install, the `yarn global add` install for the yarn-surface install, the `executor install` CLI for the durable-service surface, the `executor web` CLI for the web-UI surface, the `executor web --foreground` CLI for the throwaway-foreground surface, the MCP servers for the MCP-source surface, the OpenAPI specs for the OpenAPI-source surface, the GraphQL APIs for the GraphQL-source surface, the Google Discovery for the Google-Discovery-source surface, the per-tool policies for the policy-governance surface, the `apps/` directory for the apps surface, the `packages/` directory for the packages surface, the `e2e/` directory for the e2e-tests surface, the `tests/` directory for the unit-tests surface, the `examples/` directory for the examples surface, the `turbo.json` for the monorepo-build surface, the `bun.lock` for the bun-lockfile surface, the `vitest.config.ts` for the test-config surface, the `design.md` for the design-doc surface, the `vision.md` for the vision-doc surface, the `RELEASING.md` for the release-doc surface, the `RUNNING.md` for the run-doc surface, the `AGENTS.md` for the agent-instructions surface, the `CLAUDE.md` for the Claude-instructions surface, the `.claude/` directory for the Claude-Code config, the `.codex/` directory for the Codex config, the `.agents/` directory for the agents config, the `.skills/` directory for the skills config, the `.vscode/` directory for the VS Code config, the `opencode.json` for the opencode config, the `autumn.config.ts` for the autumn-billing config, the `knip.config.ts` for the knip-unused-exports config, the `warden.toml` for the warden config, and a target agent + integration workflow (MCP + OpenAPI + GraphQL + per-tool policies) for the eval surfaceAI agent developers + MCP-compatible agent users that want the any-source (first-party support for MCP servers + OpenAPI + GraphQL + Google Discovery + custom JS) -- the right source-flexibility primitive for any AI agent developer who has been wiring per-source-type adaptersAI agent developers + multi-agent users that want the one-catalog-every-agent (anything MCP-compatible connects to the same set of tools) -- the right unification primitive for any AI agent developer who has been wiring per-agent tool registriesAI agent developers + security-conscious users that want the per-tool policies (allow / approval / block with sensible defaults derived from the spec) -- the right policy primitive for any AI agent developer who has been writing custom approval flowsAI agent developers + ops users that want the 4 run modes (Local CLI + Desktop App + Hosted Executor Cloud + Self-hosted on Docker or Cloudflare) -- the right deployment-flexibility primitive for any AI agent developer who has been locked to a single deployment modelAI agent developers + engineering teams that want the 4 install surfaces (npm + pnpm + bun + yarn) + the executor install + the executor web + the executor web --foreground + the e2e + the tests + the vitest + the turbo + the bun + the design.md + the vision.md + the AGENTS.md + the CLAUDE.md + the .claude/ + the .codex/ + the .agents/ + the .skills/ + the .vscode/ + the 4-field corroboration (forks 167, size 76079KB, subscribers 3, pushed 2026-07-08) + MIT -- the right install-friction + transparency primitive for any AI agent developer who has been locked to a single install path
Who should skip it
Skip Executor: Open-Source Integration Layer for AI Agents if the source repository or demo is inactive, unmaintained, or no longer matches the description shown here.
About this signal
Executor: Open-Source Integration Layer for AI Agents is tracked by RepoRadar as a tool in the Radar section. It was first seen on 2026-07-08 and last updated on 2026-07-08. The current verdict is 'try now' with a Gold tier and easy setup difficulty. The standout signals for Executor: Open-Source Integration Layer for AI Agents are workflow potential (9.5) and practical usefulness (9.0), while maturity (6.6) trails — that balance shapes where it fits best. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned Executor: Open-Source Integration Layer for AI Agents a composite score of 8.4 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 0.0 and never affects the composite score or tier. The risk label of 'low' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Risk explanation
The 2625* / 167-fork / 3-subscriber / 76079KB repo is at active maintenance (pushed 2026-07-08) but the project is in active development -- the consumer SHOULD pin the Executor version and review the changelog; the consumer SHOULD benchmark the integration layer on the consumer's specific agent workflow before adopting; the consumer SHOULD note Executor Cloud is a hosted offering (Local CLI + Desktop App + Self-hosted are the free options); the consumer SHOULD review the per-tool policies before adding new integrations.
Evidence links
Closest alternatives / related signals
open-sourcemitrhys-sullivanexecutormcpopenapigraphqlgoogle-discovery
