Skip to main content
The Nous MCP server gives your agent the context graph as a focused set of tools, engineered and sourced context ready to act on. Have your agent call get_workspace_status first. It can set up the workspace itself.

​
Fastest setup

One command installs the CLI, signs you in, and registers the MCP with your agent.
Then tell your agent “set up my Nous workspace”. It finds your ICP, or drafts one from your website, and syncs it. That is onboarding. Prefer to run it yourself.
init signs you in through the browser, saves a workspace key to ~/.nous/config.json, and registers the server with your agent.

​
Connect any client

Run npx @opennous/cli login once. It saves your key to ~/.nous/config.json, so no key goes in your config. Then add Nous to your client.
No API key is needed once you have run login. The server reads your key from ~/.nous/config.json. To pin a specific key instead, add "env": { "NOUS_API_KEY": "..." } with a key from Settings → API Keys.

​
Hosted server (remote HTTP)

For clients that cannot run a local process, like n8n cloud. Create an API key at Settings → API Keys, then add Nous with the URL and a Bearer token.
  • n8n cloud. MCP Client Tool node, Transport HTTP Streamable, Endpoint https://mcp.opennous.cloud/mcp, Auth Bearer.
  • Claude Code. claude mcp add --transport http nous https://mcp.opennous.cloud/mcp --header "Authorization: Bearer YOUR_API_KEY"
  • Hermes. In MCP settings set the name to nous, then paste the inner object { "url": "https://mcp.opennous.cloud/mcp", "headers": { "Authorization": "Bearer YOUR_API_KEY" } }.

​
The tools

​
Daily

Read context, record what happened, keep notes, check what to work next.

get_context

Engineered context for a task about one entity. The headline call before outreach or a meeting.

get_account

The full account, every claim with epistemics plus the recent timeline.

query

Retrieve and summarise activity across many people.

attention

What needs attention. Accounts gone quiet, facts decayed.

get_action_items

Open action items and commitments, grouped by account. What you owe them and what they owe you.

record

Record what happened. You observe, Nous derives the claims.

save_note

Keep a meeting brief, transcript, or note on a contact’s record.

search_notes

Semantic search across saved notes and documents.

get_playbook

Read the user’s rules (voice, outreach, icp, positioning) before you act.

verify

Re-check a specific fact before you act on it. The calibration check.

​
Setup

The agent sets the workspace up itself. Call get_workspace_status first. It returns a ranked next-steps list.

get_workspace_status

The whole setup state plus ranked next steps. The first call in a session.

set_workspace_profile

Agent-driven onboarding. Set name, website, business type, and ICP.

build_icp_model

Build the ICP scoring model from the synced GTM context.

train_icp_model

Train the ICP model on real closed-won and closed-lost deals.

sync_icp

Sync the user’s ICP and context files into the graph (file to graph).

export_icp_model

Get the learned ICP model to write back into the ICP file (graph to file).

sync_playbook

Push an edited playbook file into Nous so every agent obeys the same rules.

connect_integration

Connect a key-based integration (Apollo, Prospeo, HubSpot token, and more).

set_trigger

Create an outbound event trigger (webhook).

list_triggers

List the workspace’s triggers plus the catalog of available events.
Nous Cloud only. set_trigger and list_triggers. On a self-hosted instance, Lead Lists, CRM Sync, Triggers, and Reports are Cloud-only. Everything else, including the ICP scoring model, is open.

​
The daily loop

  1. Start a task. Call get_context with the right intent for a ranked, budget-fit context block.
  2. Need the user’s rules. Call get_playbook (voice, outreach, icp, positioning). Never use query or get_account for this.
  3. Something happened. record it. Nous derives the claims.
  4. Made something durable. save_note the brief or transcript onto the contact.
  5. End of session. Call attention for what to work next.
record versus save_note. record logs that something happened (an email, a meeting) and Nous derives claims from it. save_note keeps the document itself (a brief, a transcript), append-only and dated. Use both.

​
Environment

Source lives at apps/mcp. Each release ships to npm as @opennous/mcp@<semver>. Pin a version for reproducible installs with npx -y @opennous/mcp@0.43.0.