foxctl-integrations

Synchronize AI provider and MCP integration configurations for foxctl workflows.

3|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/joshka0/foxctl --skill foxctl-integrations
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: foxctl-integrations
Source: https://github.com/joshka0/foxctl/tree/main/configs/skills-pack/foxctl-integrations
Command: npx skills add https://github.com/joshka0/foxctl --skill foxctl-integrations

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the setup drift and manual glue work required to keep multiple AI provider configurations consistent while exposing a unified interface for operators and tooling.

Core Features & Use Cases

  • Provider config synchronization: keeps Claude/Codex/OpenCode settings aligned so MCP-serving and provider requests behave consistently.
  • MCP server enablement: runs foxctl as an MCP server for operator-controlled skill execution and integration workflows.
  • OpenAPI-backed request support: provides a universal REST-style client workflow with dry-run validation before executing operations.

Use Case

When you onboard a team or switch providers, you can sync MCP-related configuration across tools and then verify an OpenAPI request with a dry run before serving or executing it.

Quick Start

Run provider and MCP integration sync, then start MCP serving and verify status in one flow by asking for it to be executed for your configured providers.

Frequently Asked Questions about foxctl-integrations

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

FAQPage Schema
How do I sync MCP configurations across multiple AI providers?

To sync MCP configurations across Claude, Codex, and OpenCode, you apply deterministic config synchronization operations. This eliminates manual glue work and ensures provider requests behave consistently across all integrated tools.

What is the best way to validate an OpenAPI request before executing it?

The best way to validate an OpenAPI request is by using explicit dry_run validation. This REST-style client workflow allows you to verify operations against your provider configurations safely before serving or executing them.

Can I run foxctl as an MCP server for operator-controlled integrations?

Yes, you can run foxctl as an MCP server to enable operator-controlled skill execution. It provides a complete serving lifecycle with serve, status, and stop commands for managing integration workflows.

Does provider configuration synchronization work for both Claude and Codex scenarios?

Provider configuration synchronization works for Claude, Codex, and OpenCode scenarios. It aligns settings across these platforms so MCP-serving and provider requests maintain consistent behavior without setup drift.

How do I manage the MCP server lifecycle after syncing provider configurations?

You manage the MCP server lifecycle using serve, status, and stop operations. After synchronizing your provider settings, you can start serving and verify the server status in a single integrated workflow.

When do I need deterministic config synchronization for AI provider integrations?

You need deterministic config synchronization when onboarding a team or switching providers to prevent setup drift. It keeps MCP-related configurations aligned across tools, ensuring consistent operator-controlled skill execution.