Remote MCP Integration
Clous publishes remote MCP servers rather than bundling local server binaries in this plugin.
Servers
clous-platform:https://mcp.clous.app/clous-hr:https://mcp.clous.app/hrclous-employee:https://mcp.clous.app/employee
Workflow
- Load
.mcp.jsonfrom the plugin root or generate equivalent config with the SDK. - Confirm the host supports remote HTTP MCP servers.
- Authenticate through the host's OAuth flow when required.
- Run discovery/list tools before invoking mutations.
- Inspect tool schemas, scopes, and resource exposure before wiring host prompts or agent actions.
- Treat UI resources, structured content, and conversational text as separate output channels.
- Preserve traceability: keep the MCP server, tool name, resource id, and host/client assumption visible in integration notes.
Safety
- Do not pass raw employee data to unrelated tools.
- Do not bulk export without destination, purpose, and user confirmation.
- Confirm write tools have a response path back to the product or conversation.
- Prefer least-privilege scopes and explain which people-data context each tool can read or mutate.
- For HR or performance data, require citation or resource references in answers so the host does not present retrieved context as unsupported fact.