MCP servers for Claude Code and Codex

Add any MCP server to both agents, with the tokens in your keychain.

One TUI and one command for every MCP server you use: npm and Python packages, any CLI that speaks MCP, or a remote URL. toolshed checks that a server works before your agent tries it, installs it into Claude Code and Codex, and keeps API tokens in the macOS Keychain or Linux Secret Service, never in a config file.

$ brew install bartdegoede/tap/toolshed

or go install github.com/bartdegoede/toolshed/cmd/toolshed@latest · more ways

The toolshed TUI: browsing MCP servers, adding one, entering a secret, seeing its tools, and installing it into Claude Code and Codex

What it does

Add anything: An npm or Python package, any CLI that speaks MCP, or a remote URL. toolshed starts it and lists its tools, so you know it works. Getting started
Both agents, equally: One keypress installs it into Claude Code and Codex, for every project or one repository, without touching the settings you made yourself. Claude Code and Codex
Secrets in the keychain: Servers start through a small wrapper that reads the token from your keychain, for local and remote servers alike. Secrets
Import what you have: Adopt the servers you set up by hand, and move their tokens out of plain text. Import
Let your agent do it: toolshed is an MCP server itself: ask your agent to add a server, and approve what it will run with one keypress. Your agent
Share a toolbox: Your tools live in one small YAML file. Commit it, and your team gets the same setup. The registry

Open source, MIT licensed, macOS and Linux. github.com/bartdegoede/toolshed