Skip to main content
Nebyoulous speaks the Model Context Protocol. Connect an AI assistant and it can list your integration sets, build rigs, recommend and start stacks, read frame QA results, and draft posts, all as you.

​
Two ways to connect

Hosted server

https://api.nebyoulous.space/mcp over Streamable HTTP. Nothing to install. You sign in with OAuth in the browser. Start here.

CLI server

nebyoulous mcp:serve over stdio. Adds local tools that read your disks: scan a card, plan and run a sync.
Use the hosted server unless your assistant needs to read files on your machine. You can add both; tool names don’t collide, but the CLI server already includes every hosted tool.

​
What an assistant can do

“Create an integration set called Rosette 2026-04-20.” “What’s in my M31 set, by folder?” “Delete the flats-old folder from that set.”
“Add my RedCat 51, ASI2600MC, and AM5 as gear, then make a rig called Travel from them and link it to the Rosette set.”
“Recommend a stack config for the Rosette set, then start it.” “Is the stack done? Give me the master download link.”
“Run frame QA on lights-300s and tell me which frames were rejected and why.”
“Look up NGC 2237 in the catalog and draft a post for it linked to the Rosette set.”

​
Safety

  • Every call acts as you. Identity comes from your token, never from a tool argument, so an assistant can only read and change your own data.
  • Destructive tools are marked. Tools that delete or cancel carry the MCP destructiveHint, and read-only tools carry readOnlyHint. Claude Code, Cursor, and other hosts use these to ask you before a destructive call runs.
  • Connections expire. When you approve a hosted connection you choose how long it stays signed in: 7, 30, or 90 days. To disconnect sooner, remove the server from your client.