Tool Connector

This is what you reach for when you need Claude to actually talk to your work tools. It handles commercial stuff like Slack, Jira, and GitHub, but the real value is connecting internal tools like your company's deployment portal or incident tracker. The approach is practical: it asks for a URL before credentials, runs commands itself instead of making you paste them, and prioritizes API tokens over OAuth dance. Pre-built recipes exist for common tools, but it walks you through adding new ones from scratch. If you've ever wanted your agent to read from Confluence or file a ticket without leaving the conversation, this gets you there.

GitHub stars: 357
last updated: Jun 11, 2026

View on GitHub

Install

$ npx -y skills add zhixiangluo/10xproductivity --skill tool-connector --agent claude-code

Installs into .claude/skills of the current project.

Files

Tool Connector — Connect Any Work Tool to Your Agent

Requires the repo cloned locally. Check if it's already present (ls setup.md), then read setup.md — that is the full entry point. The sections below summarize the approach for reference.

Full methodology and pre-built recipes: https://github.com/zhixiangluo/10xProductivity

Internal tools are first-class citizens

Internal and custom-built tools are often the most valuable to connect — deployment portals, incident trackers, internal knowledge bases, custom dashboards, HR systems, anything your company built or runs. They follow the exact same setup path as commercial tools and stay private in personal/ (gitignored, never committed).

If a tool has an API or a web UI, it can be connected.