MCP integration
MCP lets an AI client discover tools and call them with a user’s authorization. This page defines the naming and permission requirements for a HarperHarbor integration.
To arrange MCP access, contact the integration team for an endpoint, transport, resource identifier and allowed scopes. There is currently no self-service MCP connection configuration in the console. Connect only after those details have been supplied and verified. For direct API access, follow the HTTP quickstart.
Tool descriptions
Section titled “Tool descriptions”Use the same asset names in tools and API documentation:
| Asset or operation | Description to show the user |
|---|---|
| Agent configurations | Read or edit instructions, example conversations and opening messages |
| Lorebooks | Manage knowledge entries and link them to an agent configuration |
| Presentation assets | Manage display rules, styles and scripts, subject to the integration’s permissions |
| Agent conversations | Start a conversation or send a message; disclose any credits it consumes |
| Account queries | Read only the account information covered by the granted scope |
The connected server’s tools/list response is the authority for tool names, input schemas and available operations. A display title may use “Agent configuration” while an existing identifier uses role or card. Send the exact identifier advertised by the server; do not invent aliases.
Authorization and confirmation
Section titled “Authorization and confirmation”- Use the resource and scopes specified for that endpoint. An Open API token must not be reused for another resource.
- Explain whether a tool reads private data, changes an asset, publishes content, deletes data or spends credits.
- Fetch the current asset before editing it. Preserve fields the requested change does not address.
- Obtain explicit approval for publishing, destructive actions and paid operations before executing them.
- Take asset and conversation IDs from API or tool results. Keep credentials in the client’s secret storage, outside prompts and tool arguments.
The platform’s public HTTP scopes are documented in Authentication. A separate MCP transport must enforce equivalent ownership, permission, quota and billing rules; this guide does not substitute for its advertised contract.
For project instructions and API reference material, see AI client integration.