GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
Create, watch, pay for and connect hosted AI agent pods on AgentsPodium. Needs an API key.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
AuthorizationValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Run this in your terminal
claude mcp add --transport http hosting https://mcp.agentspodium.com/mcp --header 'Authorization: your-value'Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"hosting": {
"url": "https://mcp.agentspodium.com/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"hosting": {
"type": "http",
"url": "https://mcp.agentspodium.com/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This address needs a key in a request header, which the add-connector menu cannot set. Use Claude Code, Cursor or VS Code instead.
Your choice stays on this device in a cookie; no account needed.
Authorization secret required HTTP headerThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Tool names and descriptions exactly as the server reported them on Nov 9, 2026. The maker wrote them, not us; we show them as plain text.
list_platformsList available AgentsPodium engines (platforms) and hosting plans (tiers), with prices and capabilities.
list_instancesList the caller's AgentsPodium instances (agents): id, name, engine, tier, status, endpoint and A2A URL, domain, creation date. Never returns secrets.
create_instanceCreate (deploy) a new AgentsPodium instance. Returns the instance id and, when enableA2A is true, the a2aUrl and a2aToken the caller should keep. After creating, poll get_instance_health until it is serving, then call set_llm_key to give it a working LLM key.
get_instance_healthCheck whether an instance is reachable and serving, plus its status and quota state.
get_instance_termGet the billing term (trial/paid/grace) for an instance, including when it renews or expires.
set_llm_keySet (or clear, with key=null) the LLM provider API key an instance uses to answer. Required before a freshly created instance can actually respond.
pause_instancePause an instance: stops it and its billing lease. Data is archived, not deleted.
resume_instanceResume a previously paused instance, rebuilding it from its archive.
rebuild_instanceRebuild an instance's pod (e.g. after a config change that needs a restart).
delete_instancePermanently delete an instance. This cannot be undone.
get_payment_optionsGet ways to pay for an instance's plan: card/subscription buy links, crypto payment info, and Telegram Stars info (crypto and Stars are in beta testing), plus the instance's current term.
set_peersSet the list of other A2A agents this instance is allowed to call by name.
set_webhookRegister a URL that receives signed POSTs when the instance comes up, stops, fails, is deleted, when a payment is confirmed and before deletion for non-payment — instead of polling get_instance_health. Returns the HMAC secret once.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026
The registry name was verified against the domain agentspodium.com (the registry checks domain ownership)
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
Responded in 135 ms (HTTP 200)
No sign-in needed
Read 13 tool descriptions and found no hidden instructions to the AI
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: Authorization
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
The GitHub repo last changed –, and the latest version (1.0.4) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Lets other AI agents drive AgentsPodium hosting (create/monitor/manage instances) through two machine protocols — MCP (Streamable HTTP) and A2A (Agent2Agent JSON-RPC) — both backed by the existing account API at https://agentspodium.com/api.
The gateway holds no state and no secrets of its own. Every call carries the caller's own AgentsPodium API key (Authorization: Bearer ak_live_..., or a session token), which is forwarded verbatim to the account API. Missing that header always answers 401 with a JSON body pointing at https://agentspodium.com/account ("API keys for agents") and https://hosting.defispace.com/docs/auth.
One process serves both hostnames, selected by the Host header wherever a path is shared between the two (only GET /); everything else defaults to MCP behaviour, and mcp.agentspodium.com / a2a.agentspodium.com route to the same Deployment.
npm install
npm run build ACCOUNT_API=https://agentspodium.com/api PORT=3200 npm start
npm run dev
Env vars:
ACCOUNT_API — base URL of the account API (default https://agentspodium.com/api).PORT — HTTP port (default 3200).A2A_HOST — hostname that selects A2A behaviour for GET / (default a2a.agentspodium.com).mcp.agentspodium.com/mcpStreamable HTTP, stateless (no session id). Requires Accept: application/json, text/event-stream.
# initialize
curl -s -X POST https://mcp.agentspodium.com/mcp \ -H "Authorization: Bearer ak_live_..." \ -H "Content-Type: application/json" \ -H "Accept: application/json, text/event-stream" \ -d '{ "jsonrpc": "2.0", "id": 1, "method": "initialize", "params": { "protocolVersion": "2025-06-18", "capabilities": {}, "clientInfo": { "name": "example-client", "version": "0.1.0" } } }'
curl -s -X POST https://mcp.agentspodium.com/mcp \ -H "Authorization: Bearer ak_live_..." \ -H "Content-Type: application/json" \ -H "Accept: application/json, text/event-stream" \ -d '{ "jsonrpc": "2.0", "id": 2, "method": "tools/call", "params": { "name": "list_platforms", "arguments": {} } }'
Tools: list_platforms, list_instances, create_instance, get_instance_health, get_instance_term, set_llm_key, pause_instance, resume_instance, rebuild_instance, delete_instance, get_payment_options, set_peers, set_webhook. Plus one resource, agentspodium://docs (the hosting docs).
a2a.agentspodium.com/curl -s https://a2a.agentspodium.com/.well-known/agent-card.json
curl -s -X POST https://a2a.agentspodium.com/ \ -H "Authorization: Bearer ak_live_..." \ -H "Content-Type: application/json" \ -d '{ "jsonrpc": "2.0", "id": 1, "method": "message/send", "params": { "message": { "parts": [{ "kind": "data", "data": { "skill": "create-instance", "params": { "engine": "hermes", "tier": "small", "name": "My Agent" } } }] } } }'
curl -s -X POST https://a2a.agentspodium.com/ \ -H "Authorization: Bearer ak_live_..." \ -H "Content-Type: application/json" \ -d '{ "jsonrpc": "2.0", "id": 2, "method": "message/send", "params": { "message": { "parts": [{ "kind": "text", "text": "platforms" }] } } }'
Text grammar: create [name ...], health , term , platforms, payment . Anything else answers with the skill list and the exact JSON shape.
Public, no auth: GET /catalog.json (proxy of the account API's /a2a-catalog).
docker build -t agentpodium-agent-gateway apps/agent-gateway
kubectl apply -f apps/agent-gateway/deploy/gateway.yaml
deploy/gateway.yaml creates namespace ap-agentgw, a Deployment/Service on port 3200, and two HTTPRoutes (mcp.agentspodium.com, a2a.agentspodium.com) against the shared akash-gateway Gateway. Swap __IMAGE_TAG__ for the built image tag before applying.