Adding Shared Tools
This page covers platform-managed shared tools.
It does not cover:
- user-installed marketplace runtimes
- sandboxes
- built-in
infrastrActureMCP tools
Authoring Model
The preferred source of truth is the registry-backed tool model in PostgreSQL.
src/config/sharedTools.ts still exists as a compatibility layer and fallback for startup/OAuth behavior, but it should not be treated as the final long-term authoring surface.
Decision Checklist
Before adding a shared tool, answer:
- Is this really shared, or should it be user-installed?
- Should normal users ever receive it through standard sync?
- Does it use an org-wide credential?
- Does it need OAuth callback handling?
- Does it need non-default Docker host config?
If it uses an org-wide credential, default to admin.
Minimum Definition
You need:
| Field | Why |
|---|---|
| id / name | stable identity |
| image | runtime deployment |
| port layout | routable endpoint |
| tier | standard vs admin |
| shared-service marker | integration filtering |
| auth config | OAuth or secret handling |