Designed for non-developers who want guided setup. The agent works only with accounts connected to your Nilyo user.
What you can ask your agent to do
Discover the common MCP URL
Your agent completes a clear Nilyo action and keeps the result linked to the correct provider account for the next step.
Choose OAuth or a personal token based on runtime support
Your agent completes a clear Nilyo action and keeps the result linked to the correct provider account for the next step.
Guide provider connection without exposing secrets
Your agent completes a clear Nilyo action and keeps the result linked to the correct provider account for the next step.
How this workflow works
- Paste the setup URL into your agent.
- Follow its sign-in and Nilyo connection instructions.
- Connect only the provider accounts needed for your intended tasks.
Never paste a personal bearer token into public content or an untrusted agent. Prefer OAuth whenever the runtime supports it.
Questions people ask
Do I need to understand MCP?
No. The setup page gives the runtime both human and machine-readable instructions.
Is there a separate MCP for each agent?
No. ChatGPT, Claude, OpenClaw, Hermes and generic clients use the same endpoint.
Where do personal tokens come from?
Authenticated, entitled users can create a token from the Nilyo account page; it is shown once.
Why use Nilyo for this?
Nilyo gives your chosen agent access only to the accounts you connect. Your provider passwords are never shown to the agent, and reading information does not silently authorize sending, inviting or deleting.
If several accounts, people or companies match, the agent asks you to clarify. If the result of an important action is uncertain, it checks what happened before attempting it again.