Package the best of it and put it on the right desks.
One person's working method, packaged so it behaves the same on somebody else's machine, published where the team can find it, assigned by role, and reaching its tools through a single governed connector.
Skills, context and tools, packaged
One person's working method, packaged so it behaves the same on somebody else's machine: the instructions, the context they assume, the exact tools they may reach, and the guardrails.
- Package skills, context files and named MCP tools as one unit
- Version it, ship updates to everyone, roll back if it regresses
- Guardrails travel with it, so a copy cannot do more than the original
- Publish from the machine it was built on
- outreach-playbook.md
- reply-triage.md
- pricing-tiers.md
- icp-definition.md
- competitor-notes.md
- read_account
- enrich_lead
- send_email
- log_note
- delete_record — off
- send_email — approve over 50
47 people upskilled, and anyone who joins those roles later arrives with it.
Where published work lives
The registry everyone installs from. Browse what has been published, see who owns it and what version you are on, and install in one action.
- One place to find every published capability
- Install without copying files or setting anything up
- Assigned capabilities arrive ready to run: no setup, no keys, no file-sharing
- Update in place; deprecate without breaking whoever is still on the old version
- Request access to something you can see but have not been given
Every tool ready, nothing to set up
Connor is a single MCP server. Somebody assigned a capability has every tool it needs the moment they open it — nothing to install, no accounts to create, no keys to find. They connect once to Connor and everything their role is allowed to reach is already there.
- Assigned capabilities work immediately: no tools to add, nothing to configure
- One URL and one auth in place of one entry per tool
- The tool list is produced from the caller's role at connection time
- Per-user keys injected at call time, never shared and never on disk
- Every call routed, decided and recorded on the way past
read_account
enrich_leadsearch_contactssend_email
list_issues
search_pages
post_message
query_recordsdelete_recordexport_all
drop_tableIdentity, roles and who gets what
Assign to a role rather than to a person. Everybody in it has the capability today, and anyone who joins it next month arrives with it already.
- Roles built from your directory, not maintained separately
- Assign capabilities and tool access per role
- Joiners inherit; leavers lose access without anyone remembering to act
- Add people, group them into roles, and see exactly who can reach what
- One identity answers for both distribution and attribution