What problem does it solve?
This Skill eliminates the need for separate bridge CLIs or manual tool configuration to access external MCP server tools directly within Spark Agent, streamlining workflows that rely on third-party integrations.
Core Features & Use Cases
- Automatic Tool Registration: Discovers MCP server tools on startup and registers them as native Spark tools with a consistent
mcp_{server}_{tool} naming convention.
- Multi-Transport Support: Works with both local stdio-based MCP servers (run via npx, uvx, or custom commands) and remote HTTP/StreamableHTTP MCP servers.
- Built-in Security: Filters environment variables passed to stdio subprocesses and redacts credentials from error messages to prevent accidental leakage.
- Use Case: Connect a GitHub MCP server to access issue tracking and pull request tools directly in your Spark coding workflows, or link a filesystem MCP server to manage project files without switching contexts.
Quick Start
Add your desired MCP server configuration to the mcp_servers section of your ~/.spark/config.yaml file, then restart Spark Agent to auto-register all available MCP tools for use in conversations.