Resources and prompts complement tools. Administrators configure them for a particular server, while the AI application determines how users discover and use those capabilities.
Add a resource#
Open the intended server's resources area. Give the item a clear name, description, URI and appropriate content type. Choose the supported source type, such as static content or a documented dynamic source, and configure any permitted variables.
Use only content that the server's audience is allowed to read. Resource discovery can itself reveal names and descriptions, so keep private account identifiers out of items exposed to an unrelated audience.
Test resource access#
Connect with the credential type intended for the user. Confirm that the client discovers and reads the correct content. Check that variables cannot select a different organisation's records. A tools-only credential can intentionally reject resource operations; do not broaden its scope without an agreed need.
Add a prompt template#
Define the task the template should help with, its inputs and the expected output. Describe the account and date context the user must supply. Avoid including credentials, real customer examples or an instruction that assumes broad permission to send or delete.
Preview the rendered prompt with fictional inputs. Confirm that the actual client exposes it in the expected way. A template may guide a workflow, but it does not grant access or enforce an approval boundary.
Maintain reusable content#
Give instructions a clear owner and review them when a tool name, schema or account boundary changes. Check links and variables after copying a prompt or resource to another server. Use imports and exports when moving a whole configuration.