القائمة
Connect an MCP server (catalog or custom URL/stdio) and make its tools usable — including completing OAuth on a headless host.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | connect-mcp |
| description | Connect an MCP server (catalog or custom URL/stdio) and make its tools usable — including completing OAuth on a headless host. |
Connect an MCP server so its tools become available to the agent.
Pick the registration path:
list_mcp_catalog, then connect_catalog_mcp with the catalog id.register_mcp_server with one of: stdio (a command + args), http+bearer (a url + apiKey, using ${ENV_VAR} for the secret), or http+oauth (a url). Then connect_mcp_server.OAuth servers: connecting surfaces an authorization URL. The OAuth callback is a loopback (http://127.0.0.1:<port>/callback) on the AGENT HOST. If the host is headless (no browser), a laptop browser can't reach that loopback — tell the user to tunnel it first, then approve:
ssh -L <port>:127.0.0.1:<port> <host> (the host pins the port via OPENAGI_OAUTH_CALLBACK_PORT)Verify with list_mcp_tools. Large servers (lots of tools) may NOT be advertised as direct functions — a cap keeps the model's tool list within provider limits. Reach any capped tool with run_mcp_tool(server, tool, args); list_mcp_tools shows them all.
Secrets hygiene: never commit real keys. Reference them as ${ENV_VAR} that resolves from the host's .env.
User asked: {{input}}
Guide configuring proactive outreach so the main reaches out (digest + live decisions) and the Mac app surfaces it with notifications, an overlay list, and inline buttons.
Roll out new openAGI code to the main and to Mac nodes (iMessage / computer-use), and restart them safely.
Troubleshoot opaque model/tool failures and runaway budget — and their usual root causes.
Troubleshoot why the agent stopped replying to iMessages, in priority order.
Operate a connected computer-use node to accomplish an on-screen task — screenshot, reason, act in a loop.
Set up a recurring check that only does work (and spends tokens) when there's something new — e.g. "every hour, check BuildBetter for new calls".