AgentGem
Your agent setup, session transcripts, and usage data are a goldmine of how you get AI to deliver. AgentGem distills them into secret-safe, composable Gems you own — reuse, publish, and deploy them anywhere. Built on AgentBack.
https://agentgem.ai/Opens ChatGPT on the web or desktop and asks it to use the WebMCP tools available here.
Connect straight to this server’s public endpoint.
https://api.agentgem.ai/mcpWe add this server to your workspace, then open Studio — saved access, one connection to many servers, with a history of what ran.
Last probed Sep 14, 2026 · api.agentgem.ai
11tools discovered
Inventory
Introspect the local coding-agent config (skills, MCP servers, CLAUDE.md). Pass project roots to also include project-level artifacts. Secrets are redacted.
Build Gem
Build a redacted Gem from a selection of the introspected config artifacts.
Gem Export
Export a Gem (built from a selection of the local config) as a single portable .gem archive, returned base64-encoded. Share those bytes as a file/upload/gist; install elsewhere with gem_install. Secrets are redacted; no registry required.
Gem Install
Read and verify a shared .gem from a URL, local file path, or base64 bytes — returning the lock-verified Gem and its manifest meta. URL fetches are SSRF-guarded; tampered archives are rejected. Disk placement is performed via the REST /materialize endpoint.
Transfer Send
Share a Gem (built from a selection of the local config) store-and-forward: encrypts it client-side and stashes the ciphertext in the configured NATS Object Store, returning a one-time `agentgem://` ticket. Hand the ticket to a friend/coworker or your other device; they redeem it with transfer_receive. The broker never sees plaintext. Requires NATS_URL.
Transfer Receive
Redeem an `agentgem://` ticket: fetches the ciphertext from the configured NATS Object Store, decrypts it with the key carried in the ticket, verifies integrity (gem.lock), and returns the verified Gem + manifest meta. The object is burned after the first successful fetch. Requires NATS_URL. Disk placement is performed via the REST /materialize endpoint.
Registry Index
List the gems available in the configured registry (names, versions, dependencies).
Registry Search
Search the configured registry for gems by name/tags/description. Pass a `kind` (skill|mcp_server|instructions|hook) or `tag` to filter; an empty query browses the catalog. Returns ranked hits with latest version and description.
Registry Resolve
Resolve registry refs into an install plan (items, artifacts, required secrets, and a materialize preview for a target). No writes.
Registry Install
Resolve + merge registry refs, returning the merged Gem and install plan. (Disk/workspace placement is performed via the REST /registry/install endpoint.)
Registry Publish
Publish a workspace Gem to the registry as @scope/name@version (requires GITHUB_TOKEN).
Get your MCP into directories
A working endpoint is step one. Directory coverage is the coordinated launch across ChatGPT, Claude, Cursor, the MCP Registry, and community indexes.
Directory coverage for brandsYour agent setup, session transcripts, and usage data are a goldmine of how you get AI to deliver. AgentGem distills them into secret-safe, composable Gems you own — reuse, publish, and deploy them anywhere. Built on AgentBack.
Use the MCP endpoint listed on this page in your MCP client configuration. One-click install pills support Claude, Cursor, VS Code, and other hosts. Copy the remote MCP URL if your client needs a manual entry.
MCPBundles probed 11 tools on the live server. The tool list on this page reflects what was discovered at the last refresh — connect your client to see the full set available to your session.
No provider sign-in was required during MCPBundles' probe. Your client may still need MCPBundles credentials depending on how you connect.
Operate AgentGem? Verify ownership to take over this directory entry.
This server appears in the MCPBundles directory. Verify you operate it to take over the listing — name, description, logo, contact email, and skill content. We email a 6-digit code to a maintainer address your server publishes in /.well-known/security.txt or /.well-known/mcpbundles.json. Free, takes about a minute.