usefulsoftwareco/executor

The missing integration layer for AI agents. Let them call any OpenAPI / MCP / GraphQL / custom js functions in secure environment.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 hour ago
Added to GitGenius on September 17th, 2026
Created on February 7th, 2026
Open Issues & Pull Requests: 135 (+0)
GitHub issues: Enabled
Number of forks: 325
Total Stargazers: 3,940 (+1)
Total Subscribers: 6 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 33.7 hours
Mean response time: 10.3 days
90th percentile: 26.0 days
Tracked items: 161

Most active contributors

Sign in to see contributor activity.

How this project is maintained

About 19% of issues opened in the past year have never received a reply. 93% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Almost all tracked open issues have seen activity in the last three months. 71% of issues opened in the past year have been closed, leaving a working backlog. Three people close 93% of everything that gets resolved.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 58
New in 7 days: 10
Closed in 7 days: 9
Avg open age: 29 days
Stale 30+ days: 13
Stale 90+ days: 2

Recent activity

Opened in 7 days: 9
Closed in 7 days: 9
Comments in 7 days: 5
Events in 7 days: 11

Top labels

  • bug (11)
  • enhancement (6)
  • crash-triage (1)

Most active issues this week

Sign in to see which issues are moving.

Detailed Description

Executor is an integration layer for AI agents that lets them call any OpenAPI, MCP, GraphQL, or custom JavaScript functions in a secure environment.

The problem Executor solves is the fragmentation of integrations across multiple AI agents. Each agent typically requires its own copy of every integration, with credentials and policies configured separately in each place. Executor centralizes this by acting as a single catalog that any MCP-compatible agent can access. You configure an integration once with its authentication and per-tool policies, then all your agents share that same setup over MCP. The tool supports MCP servers, OpenAPI specs, GraphQL APIs, and Google Discovery APIs as first-class integration types, with an open plugin system for custom integrations.

Executor suits teams using multiple AI agents who want to avoid duplicating integration setup across Claude Code, Cursor, ChatGPT, and similar tools. It works best when you need consistent policies and authentication across agents, and when you want integrations to live in one place rather than scattered across client configurations. The tool offers multiple deployment options: Executor Cloud for hosted setup with no installation, a local CLI for Node.js environments, a desktop app, or self-hosted deployment on Docker or Cloudflare. The README does not compare Executor to alternative solutions.

The project maintains active engagement through its Discord community channel and provides comprehensive documentation including a setup prompt that agents themselves can follow to configure Executor end-to-end. Development activity shows ongoing refinement of the integration model, with clear conceptual documentation and multiple deployment pathways being actively supported. The tool is packaged to work the same way across all its runtime options, suggesting consistent maintenance of feature parity across different installation methods.