One home for your agent skills and MCPs.
Create, version, and sync the skills and tools your agents run — then share them with your whole team, instead of copying files between machines and hand-editing config.
In development — we're talking to teams before we build it.
Reviews a pull-request diff for correctness and reuse, then posts inline comments. Pulls repo context through the GitHub MCP server.
Files
- SKILL.md
- references/checklist.md
- references/style.md
History
- v1.2.0Group findings by file2d ago
- v1.1.0Add reuse checklist3w ago
- v1.0.0First publishedJun 4
---
name: pr-review
description: Review a diff for correctness and reuse.
allowed-tools: [github.get_diff, github.comment]
---
# PR review
When someone shares a pull request:
1. Fetch the diff through the GitHub MCP server.
2. Flag correctness bugs first, then reuse and simplification.
3. Post findings as inline comments, grouped by file.Stop treating skills like loose prompt files.
A skill is a real artifact your team depends on. It should have versions, a history, and one place everyone gets it from.
Draft, publish, roll back
Refine a skill safely before it ships, then publish a version. Every change has a number, an author, and a date — and you can roll back to the one that worked.
Create or import
Start from a blank SKILL.md or import an existing one from GitHub. Reference files come along with it, so a skill stays whole.
Sync to every agent
Install a skill once through the plugin. When you publish an update, the agents that use it pick it up — no re-copying files between machines.
Connect the tools your agents need.
Browse the catalog, install an open-source server from our MCP directory, or deploy your own for internal systems — once, for everyone.
Catalog or your own
Connect an MCP server from the catalog, or deploy your own from npm, PyPI, GitHub, or a container image.
Credentials that stay put
OAuth and API-key connections are held by the server, not pasted into each teammate’s config file.
Tools · 6
Source
ghcr.io/acme/orders-mcp:1.4.2
Environment
- API_KEYRequired••••••••••••
- WEBHOOK_SECRETRequired••••••••••••
- BASE_URLOptional••••••••••••
One toolkit instead of a pile of configs.
Group the skills and tools a role actually uses, share it as a single plugin, and decide who gets it.
Bundle tools and skills
Pull the tools you actually want from several MCP servers, add your published skills, and ship them as one toolkit.
Assign who gets what
Give a toolkit to one teammate or the whole workspace. Members connect their own accounts, so sharing a toolkit never means sharing a secret.
Connected MCP servers
- Notion3 of 12 tools
- Gmail2 of 9 tools
- Sentry4 of 7 tools
- Internal Orders MCP6 of 6 tools
Skills · 8
Assigned to
One install, every client
npx @metatext/hub install customer-success
See what your agents actually use.
Tool-call volume, error rates, and latency across your connected servers — so you know what's working, what's failing, and what nobody ever calls.
Usage you can act on
Find the skill everyone leans on, the server that's been degraded all week, and the ten tools you can retire.
6.5k
Skills invoked
18.2k
Tool calls
0.4%
Error rate
| Name | Type | Calls | p95 | Health |
|---|---|---|---|---|
| pr-review | Skill | 2,310 | 1.8s | Healthy |
| github.get_diff | Tool | 4,120 | 0.6s | Healthy |
| notion.search | Tool | 1,740 | 4.2s | Degraded |
| standup-digest | Skill | 980 | 2.1s | Healthy |
Invite your team. Share everything but the secrets.
Roles that map to reality
Owners, admins, and members. Decide who can publish a skill, edit a toolkit, or add a server.
Per-user credentials
Each person authenticates their own accounts against a shared toolkit — no shared API keys in a pinned message.
One source of truth
Everyone runs the same published versions. No drift between the skill on your laptop and the one in the repo.
One command, every client.
Pick a client, paste one command. The plugin installs the toolkit — skills and tools — and keeps it in sync as you publish updates. No hand-edited JSON.
- Claude Code
- Claude Desktop
- Codex
- Cursor
npx @metatext/hub install customer-successStart free. Pay when your team shares it.
Indicative only — nothing is on sale yet. These tiers are here so you can tell us whether the shape is right.
Free
$0/mo
For trying it on your own machine.
- 1 user
- 3 catalog MCP servers
- Up to 3 skills
- Updates overwrite in place — no version history
Pro
$19/mo
For individual builders who want custom servers.
- 1 user
- 10 MCP servers + custom deployments
- Up to 100 skills
- 30-day version history
Team
$149/mo
For teams sharing skills and infrastructure.
- 5 users included, $9 per extra seat
- Unlimited MCP servers + custom deployments
- Unlimited skills and version history
- Toolkit assignments and per-user credentials
Get early access — and tell us what you actually need
We're building this with the first teams that use it. Leave your email, answer as much as you like, and say yes to a short interview if you want a say in what ships.
- Early access to Hub as it opens up
- A 20-minute interview if you want one — research, not a pitch
- No spam — early-access updates only
Questions
- Is Metatext Hub available today?
- No — this page describes what we're building, and we're talking to teams before we build it. Join the early-access list and we'll reach out as it opens up.
- What is an agent skill?
- A folder with a SKILL.md file that tells an agent how to do a specific job, plus any reference files it needs. Agents like Claude Code load them to pick up a repeatable workflow — you can browse real ones in our skills directory at /tools/skills.
- Do I have to use it as a team?
- No. It works as a personal library — version your own skills, connect your own servers. Sharing is there when a second person needs the same setup.
- Which clients does the plugin support?
- Claude Code, Claude Desktop, Codex, Cursor, and other MCP-enabled clients. One install command wires up every skill and tool in a toolkit.
- Is the pricing final?
- No. The tiers above are indicative — they exist so you can tell us whether the shape is right. Early-access pricing will be set with the first teams we work with.