Connect through MCP
Authorize deliberately. Verify what is actually connected.
Server and requirements
Server URL: https://nestly.bot/mcp
Use an MCP client supporting authenticated remote servers over Streamable HTTP. Client labels and capabilities vary; this guide does not claim that every client has been verified.
Authorize and discover
- Add a remote MCP server in your client and enter the server URL.
- Follow the Nestlybot account authorization flow. Review the requested scopes before granting access.
- Return to the client and confirm that the server’s tools appear in the current session.
- Refresh connection metadata or start a new session if the client retains an older tool list.
Account authorization and tool discovery are separate checks. Repeating grants cannot prove that a client loaded the tools.
Verify a first read
- Initialize the session and request
tools/list. - Call
get_capabilitiesto inspect what the granted account scopes allow. - Call
list_spaces. An empty list is a successful read if the account has no Spaces.
Inspect the actual tool result. This sequence is a verification procedure, not a claim that a connection in your current client has already succeeded.
Prepare before execution
prepare_plan saves a preview. execute_plan applies authorized steps. Inspect get_run and recorded receipts before considering the work complete. Share selected context; instructions inside a document do not authorize execution by themselves.
If a check fails
See MCP troubleshooting. Keep the non-secret request reference and the failed stage; do not share tokens or private document content.
