@tank/tool-creator

Package MCP servers as Tank tool bundles with tank.json permissions.

1|1|Updated Feb 20, 2026
One-click install
npx skills add https://github.com/tankpkg/packages --skill tank-tool-creator
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: @tank/tool-creator
Source: https://github.com/tankpkg/packages/tree/main/skills/tool-creator
Command: npx skills add https://github.com/tankpkg/packages --skill tank-tool-creator

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you package an existing MCP server as a Tank tool bundle without rewriting the server itself. It removes the guesswork around transport choice, platform-specific config, permissions, and when to add usage guidance for the agent.

Core Features & Use Cases

  • Tool Atom Design: Define the minimal tool atom that points to a server by name and keeps implementation details out of the bundle.
  • Cross-Platform Wiring: Configure extension bags for Claude Code, OpenCode, Cursor, and other harnesses with the right command, url, env, and headers fields.
  • Transport and Security Decisions: Choose between local STDIO and remote HTTP wiring, then set subprocess and network permissions correctly in tank.json.
  • OAuth and Usage Guidance: Package remote authenticated servers with OAuth metadata and pair complex tools with an instruction atom that explains when and how to use them.
  • Use Case: If you already have an MCP server configuration, this Skill shows how to convert it into a portable Tank package that agents can install and use consistently.

Quick Start

Ask the AI to convert your MCP server config into a Tank tool bundle and generate the matching tank.json, permissions, and SKILL.md guidance for your target platforms.

Frequently Asked Questions about @tank/tool-creator

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

FAQPage Schema
How do I package an MCP server into a Tank tool bundle?

Package an MCP server into a Tank tool bundle by defining a minimal tool atom pointing to the server by name, then generate the matching tank.json with correct permissions, platform-specific extension bags, and SKILL.md guidance for your target agent harnesses.

When should I use STDIO versus HTTP transport for an MCP server bundle?

Use STDIO transport for local MCP servers requiring subprocess control permissions, and HTTP transport for remote servers requiring hostname-scoped network access and OAuth-enabled integrations in your tank.json configuration.

Can I configure MCP server bundles for multiple agent harnesses like Claude Code and Cursor?

Yes, you can configure cross-platform extension bags for agent harnesses like Claude Code, OpenCode, and Cursor by setting the correct command, url, env, and headers fields for each platform's specific wiring requirements.

How does OAuth work when packaging remote MCP servers as Tank bundles?

OAuth-enabled remote MCP servers are packaged by including OAuth metadata within the Tank bundle and pairing them with an instruction atom that explains to the agent when and how to use the authenticated server capabilities.

What permissions are required in tank.json for local MCP server subprocesses?

Local STDIO MCP server bundles require subprocess control permissions in tank.json to manage the server lifecycle, while remote HTTP bundles require hostname-scoped network access permissions for secure communication.

Why add an instruction atom to a Tank tool bundle for complex MCP servers?

Adding an instruction atom to a Tank tool bundle provides usage guidance that keeps agents aligned with the upstream MCP server's capabilities, ensuring the agent understands when and how to interact with complex tools correctly.