List resources and tools, call tools, and read resources across MCP servers.
npx skills add https://github.com/lofibrainwav/AFO_Kingdom --skill mcp-tool-bridge
Please help me install this Agent Skill. Skill: mcp-tool-bridge Source: https://github.com/lofibrainwav/AFO_Kingdom/tree/main/skills/mcp-tool-bridge Command: npx skills add https://github.com/lofibrainwav/AFO_Kingdom --skill mcp-tool-bridge
This Skill acts as a universal connector to access and orchestrate external MCP (Model Context Protocol) servers and their tools, enabling infinite extensibility.
tools = await mcp_bridge.list_tools("afo-ultimate-mcp") result = await mcp_bridge.call_tool(server="trinity-score-mcp", tool="calculate", args={"truth_base": 95, "goodness_base": 90})
High-intent search queries and answers about installing and using this skill.
MCP bridge acts as a universal connector to discover and invoke tools across multiple registered MCP servers. Use list_mcp_tools() to enumerate available tools from any server, then call_mcp_tool() with the server name and tool parameters to execute them, enabling seamless orchestration across diverse MCP implementations.
Register MCP servers in a centralized config location, then use the bridge to list available resources and tools via list_mcp_resources() and list_mcp_tools(). Execute tools with parameterized inputs using call_mcp_tool(), and read resource content with read_mcp_resource() for downstream processing.
Yes. The bridge provides tool discovery across registered MCP servers through list_mcp_tools(), which enumerates all available tools and their capabilities. This enables you to explore server functionality before invoking specific tools with call_mcp_tool().
MCP bridge uses a centralized config registry at standard locations to manage multiple registered MCP servers and their capabilities. This single configuration point eliminates per-server setup and enables unified discovery and orchestration across all connected servers.
Use call_mcp_tool() specifying the server name, tool identifier, and arguments object containing parameterized inputs. The bridge executes the tool on the target MCP server and returns results for downstream tasks or analysis.
MCP bridge handles server communication through standard MCP protocol operations. Error handling depends on server availability and tool implementation; the bridge surfaces server responses and failures so you can implement retry logic or fallback workflows in your integration.
eddieluengDiscover and register MCP server tools as native Hermes Agent tools.
ofelixdevParse SARIF files from static analysis tools and deduplicate findings.
blueskies1818Manage MCP servers and tools via the mcporter CLI.
VKirillManage and execute tools across multiple MCP servers.
