Skip to content
code-config.com

Share your toolkit

Share a published version of your toolkit by link or through Community. The version is a snapshot, not a live mirror of your working toolkit.

Review the toolkit’s contents, sources, and compatibility. The current publication form rejects toolkits with MCP attachments or credential-bound setting values. Resolve any eligibility message before sharing; do not remove a required safeguard just to publish.

Use content you are allowed to share. The form has no license selector; source terms and the Terms of service still matter.

  1. Open Toolkits and the toolkit’s menu.
  2. Choose Get share link for an unlisted page, or Share with Community for a discoverable listing.
  3. Complete the requested title, summary, tags, domain, and use cases. Tags are limited to five and use cases to seven.
  4. Review what is being published and confirm the form’s action.
  5. Open the published page and copy its link.

An unlisted link is accessible to anyone who has it. It stays out of Community browse, but it is not a private invitation to named recipients.

Community listings are moderated after publication and can be reviewed or removed after a report.

The page shows title, summary, tags, use cases, publisher, published version, tool names and counts, compatibility, public source repositories, and usage information. Credential requirements are represented by permitted metadata, not credential values.

A public preview listing is not a display of every file’s full text. Publishing selected authored content can involve a separate, explicitly authorized upload step that you start yourself. The publication preview is what tells you which of your local configuration a listing includes. Review it before publishing.

Open the link in a signed-out browser and verify its title, contents summary, compatibility, and Use this toolkit action. Confirm an unlisted version is not presented as a Community listing.

Send recipients to Use a shared toolkit. They save their own toolkit, then select it for a project or launch; opening the link does not configure their computer.

Edit your toolkit, then use Submit Community update for a listing. For link sharing, Copy share link opens Share a new version. Review and publish to replace the snapshot at the same address.

People following updates are notified. Their existing toolkits do not update or merge automatically; adopting the new version creates another toolkit.

Choose Stop sharing and confirm. The link or listing becomes unavailable. This does not delete copies already saved by other people; followed toolkits can show Community source withdrawn.

Use a shared toolkit explains the recipient’s experience.