Integration Overview
Before extending Captain Who, determine whether you want to add “reasoning capability,” a “working method,” or a “callable tool.”
How to choose
| Your goal | Recommended approach | Examples |
|---|---|---|
| Use another model or API gateway | Model Provider | OpenAI-compatible, Anthropic-compatible, DeepSeek V4 Chat |
| Capture a reusable operating method | Skill | Code-review standards, report templates, team workflows |
| Invoke an existing system or local service | MCP Server | Data queries, internal tools, specialized automation |
| Automate a website | Built-in browser automation | Find, click, fill in, or download in the managed browser |
A Skill can tell the Agent when to invoke an MCP Tool, and an MCP Server can be used with a model, but they do not authorize one another automatically. Every layer remains subject to the current task's permissions, approvals, and availability.
Integration boundaries
Model Provider
Model requests are sent to the API URL you configure. An endpoint that “looks compatible” is not guaranteed to fully support Tool invocation, streaming responses, Usage, or reasoning continuation. Verify it with a low-risk task after configuration.
Skill
A Skill is a content package containing instructions and optional resources. A Workspace Skill in a project is visible only to that project. Installed Skills are managed by the application and can be enabled, updated, or uninstalled in Settings. A trusted Skill source does not grant file, command, or network permissions.
MCP Server
User integrations currently support only local stdio MCP Servers. Saving a configuration, authorizing launch, enabling a connection, and approving Tool invocations are separate steps. An MCP Server is an external local process; what it can do also depends on the permissions the operating system grants that process.
Built-in capabilities
Built-in capabilities such as browser automation also use MCP technology, but they are managed by the application and are not user-editable external MCP Servers. Do not try to configure a third-party Server with internal connection parameters.
Recommended order
- Complete a task once with built-in Tools.
- Create a Workspace Skill when you need a consistent workflow.
- Connect an MCP Server only when an external capability is genuinely required.
- Start with an approval mode that requires confirmation for each call; evaluate automatic execution only after confirming the behavior.
- Keep separate source, version, and verification records for models, Skills, and MCP.
See Compatibility for the full support scope.