MCP servers and plugins
Give Claude Code, Codex and Cursor new tools from one library. Pick an MCP server or a Claude Code plugin, and TaskWire writes it into each agent's own config.
MCP servers give agents new tools: a browser to test with, your database, Sentry errors, Figma files, Stripe. Plugins add commands, agents and skills to Claude Code. Setting them up by hand means a different config file for every agent tool. TaskWire does it from one place, for one project.
Open them from Skills in the left rail: the MCP servers and Plugins tabs sit beside Library and Installed.
Both run in the desktop app (or npm start), because they write config files on your computer. That holds in Live mode too: the board is online, but the install happens here, in the project's folder.
MCP servers
The library has 38 servers. Each card shows who publishes it, its license, what it can reach and the date we last checked it. Verified means the company behind the product runs it, it's maintained and released in the last six months, and we've read what it does. Servers that can change things, spend money or touch your infrastructure carry a warning.
| Group | Servers |
|---|---|
| Core | Filesystem, Git, Fetch, Memory, Sequential Thinking, Time |
| Code and issues | GitHub, Linear, Atlassian, Azure DevOps |
| Browser and testing | Playwright, Chrome DevTools |
| Docs and search | Context7, Brave Search, Exa, Tavily, Firecrawl |
| Databases | Supabase, Neon, MongoDB |
| Cloud and infrastructure | Cloudflare docs, Cloudflare Workers bindings, Vercel, AWS documentation, AWS API, Azure, Terraform, Kubernetes, Heroku |
| Errors and analytics | Sentry, Grafana, PostHog |
| Design, docs and chat | Figma, Framelink Figma, Notion, Slack |
| Payments | Stripe, PayPal |
Click Install…, fill in any keys it asks for, and under Give it to pick which agents get it. TaskWire writes it where each tool looks:
| Agent | Without keys | With keys |
|---|---|---|
| Claude Code | the project's .mcp.json | ~/.claude.json, for this project only |
| Codex | ~/.codex/config.toml | ~/.codex/config.toml |
| Cursor | the project's .cursor/mcp.json | ~/.cursor/mcp.json |
Keys never go into the project folder, so they can't end up in your repository. TaskWire keeps them encrypted, like model keys, so Update can rewrite a server later without asking again. The board never shows them.
Not in the library? Add your own server with the command it runs or its URL, and it's installed the same way. Remove takes a server out of every file it was written to. A server shared by several projects stays until the last of them removes it.
Plugins
The Plugins tab lists Claude Code plugins from four marketplaces, read live from GitHub, so new plugins show up within the hour:
- Anthropic's official plugins (
anthropics/claude-plugins-official) - Claude Code Workflows (
wshobson/agents) - Superpowers (
obra/superpowers-marketplace) - Cursor's plugins (
cursor/plugins)
Before you install, TaskWire looks at what the plugin bundles (commands, agents, skills, MCP servers, language servers, scripts or hooks) and says so. Installing turns it on for the project the way Claude Code documents it, in .claude/settings.json, and Claude Code fetches it the next time it opens the folder.
Hooks run commands by themselves, so a plugin with hooks, or one whose contents can't be read, only installs after you say yes to that.
Who can install
Only you, signed in to the app. An agent's key can't install servers or plugins, so an agent can't give itself new powers.