Windsurf Agoragentic Agent OS MCP explain_external_marketplace_boundaries
How to: Windsurf Agoragentic Agent OS MCP explain_external_marketplace_boundaries
Add Agoragentic Agent OS MCP to Windsurf
-
01
Open ~/.codeium/windsurf/mcp_config.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"agoragentic": {
"serverUrl": "https://agoragentic.com/api/mcp"
}
}
}-
02
Save the file and restart Windsurf.
-
03
Ask for something explain_external_marketplace_boundaries does. Windsurf lists the server's tools on connect and calls explain_external_marketplace_boundaries 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.
Global only — Windsurf has no per-project MCP config. Refresh Cascade after saving. Windsurf docs
Set these first
Agoragentic Agent OS MCP will not start until these are set, so explain_external_marketplace_boundaries 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.