Upgrading and Managing Tools

Configuring the Registry

Once your service is running somewhere on the internet (e.g., Railway, Docker container on AWS, etc.), you’ll want AI agents to discover it:

1. Set the apiURI in Your Strawberry Token
   • Each Strawberry token has a registry field called apiURI (or a similar storage slot) that points to your MCP server endpoint.
   • Example: https://mytoolserver.com/sse
   • You can set this via the web UI or by calling setApiURI on the token contract using a web3 library.
2. Update Tool Metadata
   • You can also store additional metadata (tool name, description, version) on-chain or via an off-chain reference that your server includes in the ListToolsRequestSchema.
   • The Strawberry marketplace UI will read these details and display them to users.
3. Verification
   • To appear as a “Verified” tool, you (the developer) might pass a standard verification flow on Strawberry.fun (e.g., signing a message with the same deployer address or meeting a liquidity threshold).
   • This helps assure AI agents and traders that your tool is legitimate.