MCP clients can now fetch NOAN's setup guides

get_setup_guide serves NOAN's first-connect and writing-facts guidance over MCP, so a client without the NOAN skill still knows how to get started, for builders working with NOAN's API.

Until now an MCP client that did not carry the NOAN skill had no setup guidance to fall back on. It could call the tools but had nothing telling it how to connect or how to write facts well.

What's new

• A setup guide over MCP. get_setup_guide now serves first-connect (the connector, first-connect and interview guidance) and writing-facts, drawn from the public getnoan/skills repository.
• Know whether a project is new. get_me and GET /me return isNewProject, so a client can tell an empty workspace from an established one without counting facts itself.
• Clearer fact writes. create_fact now states that its content replaces the block's fact, so callers merge what they want to keep into one write instead of sending a fragment per call.

Why it matters

When you point a fresh MCP client at a workspace, it can now ask for the same first-connect and writing guidance a skill-equipped client would have, and tell whether it is looking at a brand new project. That means less guesswork in the first few calls and fewer facts written as scattered fragments.

Where to find it

The tools are documented at api.getnoan.com, and the guides live in github.com/getnoan/skills.