How-toDraft ยท not yet verified
Other MCP Clients
The general recipe for any MCP client: the endpoint, the key header, the agent profile, and a first check.
- Endpoint.
http://localhost:8765/mcpover streamable HTTP, or/mcp/ssefor a client that speaks only the older SSE transport. A client that calls from a vendor's cloud needs the stack published over HTTPS. - Key. With
AUTH_ENABLED=true, sendAuthorization: Bearer <client key>on every request. Give each client its own key, so one can be revoked alone. See client keys. - Agent profile. The agent names it with the
agent_profileargument on its calls; tell it which in its instructions. With none, calls run as the engine's default agent profile. - Instructions. On connecting, the client receives the engine's instructions and the description of each tool. For a client without plugins, give the agent the text of the agent skills as well.
- First check. Call
e_propertywith{"action": "list"}. A reply listing labels (empty on a new stack) shows the connection works.