osFoundry 的 MCP 工具清單會吃掉 Codex 多少 token，又該如何依專案精簡？
下面是 MCP 用戶端在 handshake 之後馬上會送出的呼叫。2026-11-06 從東京的一台 Mac 用 curl 打到 osFoundry 的伺服器，這個呼叫不需要 token： $ curl -s -D - -X POST https://api.osfoundry.io/api/v1/external-mcp \ -H 'content-type: application/json' \ -H 'accept: application/json, text/event-stream' \ -d '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}' HTTP/2 200 content-type: application/json content-length: 45368…
The MCP client sends a call to the osFoundry server after a handshake, which does not require a token. This call includes a POST request to https://api.osfoundry.io/api/v1/external-mcp with a JSON payload containing the method "tools/list" and an empty params object. The server responds with a 200 status code and a JSON payload containing a list of 59 tools.
Each tool includes a name, title, description, input schema, and annotations. The Codex CLI uses a table called "mcp_servers.osfoundry" to connect to the server, and each request sent by the client includes one of the 59 tool declarations. The size of these declarations in tokens is approximately 7,609, depending on the included fields such as the name, description, and input schema.
Brief written by urgent.news from Dev.to's own syndicated text. Machine-written — may contain errors; check the original before relying on it.
