Skip to main content
Glama

agentora-all

ONE MCP URL. ONE OAuth connection. ALL Agentora plugin tools.

Unified Agentora MCP proxy for sandboxed chatbots with 1-connector limits (Claude.ai free tier, Grok free tier). Solves both limitations of the Agentora Plugin for cloud-based agents:

  1. 1-connector limit — users point their single connector at this one URL and get everything

  2. stdio unavailability — Web & Social Search tools are re-implemented natively on Cloudflare Workers

Endpoint

https://agentora-all.netflypsb.workers.dev/mcp

Health check: https://agentora-all.netflypsb.workers.dev/

Auth: Agentora token (OAuth agc_ via connector flow, or API key agk_) — same as both backend workers.

Related MCP server: Selat

44 Tools, One URL

Section

Tools

Routing

Agentora Core

26 (agentora_*)

proxied via service binding → agentora-mcp worker

Customer Outreach

8 (sme_*)

proxied via service binding → customer-outreach-mcp worker

Web & Social Search

10

native (ported from the plugin's stdio server)

Native web tools (hosted adaptations)

Tool

Backend

Notes vs stdio version

read_webpage

Jina Reader + direct-fetch fallback

fallback extracts text from raw HTML when Jina rate-limits

search_web

FreeSerp (keyless) + Jina fallback

same

search_hackernews

HN Algolia (keyless)

same

search_youtube

Jina Reader

no yt-dlp on Workers — returns IDs/URLs

get_youtube_transcript

YouTube timedtext API (keyless)

no yt-dlp — English captions only

search_reddit

Jina Reader + direct fallback

same

read_github

GitHub REST (unauth) + Jina fallback

no gh CLI — public repos only

search_github

GitHub REST search + Jina fallback

same

read_rss

Jina Reader

returns feed text for parsing

agent_reach_status

static notice

Agent-Reach is local-only; hosted reports this

The local stdio server (in the plugin) remains the full-fidelity version — it has yt-dlp, gh CLI, and Agent-Reach. This hosted version is the sandboxed-agent equivalent.

Why service bindings?

Cloudflare Workers cannot fetch another *.workers.dev URL on the same account — it returns 404 (error 1001). Service bindings (wrangler.toml [[services]]) bypass public DNS entirely and run on the same thread with zero latency. That's how this proxy reaches the two backend workers.

Installation (Claude.ai / Grok)

  1. Go to connector settings

  2. Paste https://agentora-all.netflypsb.workers.dev/mcp

  3. Log in to Agentora, click Allow

  4. All 44 tools available in one connection

Install (Claude Code)

/plugin marketplace add netflypsb/agentora-plugin

(Uses the plugin marketplace; this repo is the hosted-unified backend.)

Development

npm install
npx tsc -p tsconfig.json --noEmit   # typecheck
npm run deploy                       # deploy to Cloudflare

Secrets: optional JINA_API_KEY (wrangler secret put JINA_API_KEY) raises Jina rate limits. Core functionality is keyless.

License

MIT

Related MCP Connectors

Related MCP Servers

  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI agents to access a unified catalog of tools from various APIs (OpenAPI, GraphQL, MCP, Google Discovery) through the MCP protocol.
    MIT
  • A
    license
    Not graded
    quality
    A
    maintenance
    Centralizes OAuth connections and tool access for AI agents, providing a single credential to call multiple services via MCP and REST with consistent errors and pagination.
    34 npm
    4
    Apache 2.0
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to securely discover, invoke, and manage tools through a hardened MCP endpoint with protections like injection detection, circuit breakers, retry backoff, response caching, context-window limiting, and state snapshots.
    1 npm
    MIT