Skip to main content
Glama
Sign In
Agent Connector Hub

Agent Connector Hub

by koushikmohanbhat
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

agent-connector-hub

Governed enterprise tools for AI agents, over MCP. One MCP endpoint per agent that fronts the vendors' own MCP servers (Salesforce, ServiceNow, AWS for SAP) and your own APIs, and adds what agent pilots get stuck on:

  • Per-user identity downstream. Token exchange (RFC 8693), MCP Enterprise-Managed Authorization (ID-JAG), linked accounts, or a service account that filters per user, so each system applies the end user's own permissions.

  • Business tools, not raw APIs. A few typed, documented actions per system (open_claim, create_return_request), with data rules inside the tool and no free-form SOQL or OData from the model.

  • Policy and approvals. Deny, require approval and rate limits per tool; held calls run later with the original user's identity, with the approver recorded as the actor.

  • Audit. Every call, with user, tool, decision and outcome; identifiers tokenised; OpenTelemetry spans.

  • Fakes for everything. Each pack runs offline against an emulator of the system on the same request path, so agents, evals and CI work without accounts. A conformance kit checks every pack.

It is catalog item 3.2 of the partner accelerators. It works with any MCP client, and with agent-starter-kit (kit add connectors).

Protocol

MCP 2026-07-28 (stateless) and 2025-era clients, Streamable HTTP, MCP Python SDK 2.x

Packs

salesforce-service, servicenow-itsm, sap-s4-orders, insurance-core, warranty-api (generated from OpenAPI)

Auth into the hub

OIDC (the user's token), API key + end-user header (trusted agent backend), dev

Stores

SQLite, Postgres

Deploy

Docker, Compose, Terraform for ECS Fargate and Cloud Run; notes for AgentCore Gateway and Agent Registry

Python

3.11+

Status

v0.1.0. All packs fixture tested offline; nothing live tested yet (see limitations)

Quick start (offline, no accounts)

pip install "agent-connector-hub @ git+https://github.com/koushikmohanbhat/agent-connector-hub"
hub init my-hub && cd my-hub
hub conformance             # every pack against its fakes
hub dev                     # http://127.0.0.1:8000: dev page; MCP at /mcp/<profile>

Call a tool from the command line, as a user:

hub call support-agent get_case --args '{"case_number": "00001001"}' --user cust-001
hub call support-agent update_case_status --args '{"case_number": "00001001", "status": "Closed"}' --user cust-001
#   -> pending_approval: a support lead decides on the dev page or POST /v1/approvals/{id}

Point any MCP client at http://127.0.0.1:8000/mcp/support-agent (dev mode takes the user from X-User-Id).

Related MCP server: mcp-gateway

How it fits

agent (any framework)  --MCP-->  hub /mcp/<profile>  --> policy --> identity broker --> pack tool
                                    |  audit, approvals          (token for this user)    |
                                    v                                                       v
                               Postgres / SQLite          vendor MCP server, REST API, or fake

A profile is the tool set one agent sees (profiles/*.yaml). A pack is everything for one system (packs/<name>/: tools, backends, auth, policies, fake, conformance cases, README).

Docs

License

Apache-2.0.

This server cannot be deployed

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues

Resources

Related MCP Connectors

Related MCP Servers

  • foral

    foralofficial

    foral-dev
    A
    license
    Not graded
    quality
    C
    maintenance
    Enables AI agents to access internal systems without public APIs as typed, governed MCP tools, with human-approved writes and fail-closed contract updates.
    Apache 2.0

  • mcp-gateway

    leandro-jm
    A
    license
    Not graded
    quality
    B
    maintenance
    Turns existing REST/OpenAPI APIs into governed MCP tools for AI agents without modifying the APIs themselves, generating agent-friendly tools from specs, Postman collections, HAR files or cURL commands. Owners enable tools and set policies, while every call injects upstream credentials, redacts PII, projects responses to fit context limits, and produces a full audit trail.
    41 npm
    5
    Apache 2.0

  • gatehouse

    srikrishnavansi
    A
    license
    Not graded
    quality
    C
    maintenance
    Sits between an agent and an upstream MCP server to enforce per-profile tool grants, deterministic allow/deny/handoff rules, field and PII masking, idempotent writes, and one-line audit logging from a single YAML config. Enables regulated deployments to add guardrails that fail closed without changing the customer's tools or the agent's prompt.
    MIT

  • Bulwark

    claudius-ars
    A
    license
    Not graded
    quality
    D
    maintenance
    Acts as an MCP gateway between AI agents and upstream tool servers, evaluating YAML policies on every tool call, injecting real credentials at the last mile, scanning requests and responses for secrets, PII, and prompt injection, and recording each action in a tamper-evident audit log. Also supports HTTP forward-proxy governance with rate limiting, cost tracking, and policy replay against historical audit data.
    4
    Apache 2.0