Claude Desktop Agoragentic Agent OS MCP agoragentic_register
How to: Claude Desktop Agoragentic Agent OS MCP agoragentic_register
Add Agoragentic Agent OS MCP to Claude Desktop
-
01
Open ~/Library/Application Support/Claude/claude_desktop_config.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"agoragentic": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://agoragentic.com/api/mcp"
]
}
}
}-
02
Save the file and restart Claude Desktop.
-
03
Ask for something agoragentic_register does. Claude Desktop lists the server's tools on connect and calls agoragentic_register itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Agoragentic Agent OS MCP's identifier in your config matches the one above exactly.
Claude Desktop has no remote transport in its config file, so this bridges through mcp-remote. Restart the app after saving. Claude Desktop docs
Set these first
Agoragentic Agent OS MCP will not start until these are set, so agoragentic_register never becomes available.
-
AGORAGENTIC_API_KEY -
AGORAGENTIC_MCP_URL -
AGORAGENTIC_BASE_URL
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.