Skip to main content
​
Operated by the agent + browser login

​
Set up Nous from inside your agent

Nous is now operated by the agent. The MCP server exposes seventeen tools — seven new ones let the agent set the workspace up itself instead of a human clicking through the app:
  • get_workspace_status — the whole setup state in one call (onboarding, GTM playbook, integrations, CRM sync, triggers) plus a ranked next-steps list. The first call in a session.
  • set_workspace_profile — agent-driven onboarding: name, website, business type, and a sentence on the ICP.
  • build_icp_model — turn the recorded GTM context into the ICP model.
  • connect_integration — connect a key-based integration (Apollo, Prospeo, HubSpot token, …); credentials are verified before saving.
  • configure_crm_sync — set the CRM sync rules (auto-sync, create policy, hygiene cadence). Growth+.
  • set_trigger / list_triggers — wire outbound event triggers for the user’s stack.

​
Browser login, no copy-paste

Sign in with npx @opennous/cli login — it opens your browser, you approve, and a workspace API key is minted and saved automatically; the plugin’s MCP reads it. No copy-paste. Pasting a key still works as a fallback. New sign-ups go straight from signup to a connect screen and let the agent handle onboarding.Install or update with @opennous/mcp@0.19.0 and @opennous/cli@0.4.0.
​
Notes & GTM write-back

​
Notes on contacts, and a living GTM profile

The MCP server now exposes ten tools. Three are new since the last release:
  • save_note — keep a meeting brief, transcript, prep, or plain note on a contact’s record. Append-only and dated, so a contact builds a history across meetings. (POST /v2/notes)
  • search_notes — semantic search across saved notes & documents, so an agent pulls the relevant passage instead of loading whole documents. (POST /v2/notes/search)
  • set_workspace_profile — write back a lasting change to a GTM section. The section evolves and the prior version is kept as history, never silently contradicted. (POST /v2/workspace/facts)
get_context now also surfaces a DOCUMENTS block — an overview of the notes kept on a contact — alongside the account’s ICP fit score.save_note keeps the document itself; record still logs that an interaction happened. After a meeting, use both.
​
Week of May 18–22

​
Rebrand: Proply is now Nous

We’re shipping under a new name. Nous is the context graph that GTM agents run on, and the rename reflects that focus. The product, self-hosting story, and roadmap are unchanged — only the branding and a handful of integration points have moved.

​
⚠️ Breaking changes

If you’re on Nous Cloud or self-hosting, update your integrations this week.
  • Environment variables. PROPLY_API_KEY → NOUS_API_KEY, PROPLY_BASE_URL → NOUS_BASE_URL. Rotate your .env and redeploy.
  • HTTP header. Custom clients must send x-nous-client instead of x-proply-client when calling the REST API.
  • MCP server. Install @opennous/mcp (npm). The old @goproply/* package is no longer published.
  • Domains. The app moved to app.opennous.cloud, the API to api.opennous.cloud, and the docs to docs.opennous.cloud. Update any bookmarks, OAuth redirect URIs, and webhook destinations that point to goproply.com.

​
What stays the same

  • Your workspace, contacts, context, and provider connections.
  • All REST API and MCP endpoints, request shapes, and response formats.
  • Pricing and plans on Nous Cloud.
Need help migrating? Ping us on Discord.