fabrcore-mcp

Integrates Stdio and HTTP MCP servers with FabrCoreAgentProxy via ResolveConfiguredToolsAsync.

Updated Feb 16, 2026
One-click install
npx skills add https://github.com/vulcan365/FabrCore --skill fabrcore-mcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fabrcore-mcp
Source: https://github.com/vulcan365/FabrCore/tree/main/docs/skills/fabrcore-mcp
Command: npx skills add https://github.com/vulcan365/FabrCore --skill fabrcore-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

FabrCore MCP integration solves the challenge of connecting AI agents to external tool servers, enabling discovery and use of MCP tools alongside plugins and standalone tools.

Core Features & Use Cases

  • MCP Transport Support: Stdio and HTTP transports to reach external MCP servers.
  • Config-Driven & Code-Driven: Automatic and programmatic MCP server configuration and tool resolution.
  • Tool Integration: Tools discovered via MCP are merged with existing plugin and standalone tools for LLM access.
  • Lifecycle & Troubleshooting: Managed MCP client lifecycle with guidance for diagnosing connection and tool availability issues.
  • Use Case: Deploy an agent that calls filesystem, Git, or data-science MCP tools to perform automated tasks in a workflow.

Quick Start

Add MCP server configurations to your AgentConfiguration.McpServers and call ResolveConfiguredToolsAsync to load MCP tools.

Frequently Asked Questions about fabrcore-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I connect AI agents to external MCP servers for tool integration?

To connect AI agents to external MCP servers, you add MCP server configurations to AgentConfiguration.McpServers and call ResolveConfiguredToolsAsync to automatically discover and load the external tools for agent access.

Can I use both Stdio and HTTP transports for MCP server configuration?

Yes, MCP server configuration supports both Stdio and HTTP transports, allowing agents to reach external MCP servers over local standard input/output streams or remote HTTP connections depending on the setup.

How are MCP tools merged with existing plugins and standalone tools?

Tools discovered via MCP are merged with existing plugin and standalone tools, consolidating all available functions into a single toolset that the LLM can seamlessly access during automated workflows.

What is the difference between config-driven and code-driven MCP tool discovery?

Config-driven discovery automatically resolves MCP tools from server configurations, while code-driven discovery allows programmatic configuration of MCP servers, offering flexible integration for dynamic agent workflows.

How do I troubleshoot MCP client connection and tool availability issues?

Troubleshooting MCP client connection and tool availability issues is handled through managed MCP client lifecycle features, providing built-in guidance to diagnose why external tools fail to load or respond.

Do I need to manage the MCP client lifecycle manually when integrating tools?

No, the Skill implements automatic MCP client lifecycle management within FabrCoreAgentProxy, handling initialization and teardown so agents can reliably access filesystem, Git, or data-science MCP tools without manual oversight.