Notamos MCP
Connect your agents to what actually happened
Notamos MCP is a read-only connection scoped to one workspace. It provides retrieval and structured data; Codex, Claude or another connected agent synthesizes the results using your own account.
Choose your agent
Open Customize → Connectors, then + Add → Add custom connector. In an organization, an administrator must add it first.
https://notamos.app/api/mcpSetup guide; it does not verify your connection. MCP does not install skills automatically. Steps may vary by account.
Official documentation ↗Before you start
- You need a Notamos account with MCP enabled.
- The connection is created for one specific workspace without PHI.
- This can be your private workspace, or a work workspace where an owner or admin has enabled external agents (Settings → Connect Notamos to your agent). They choose who can connect: nobody, owners and admins only, or all members.
- In a work workspace, your agent reads notes you created, including transcripts, tasks and moments. If an owner or admin allows it, it can also read notes shared with you through the company or a team you belong to, including their transcripts and the creator’s moments. It never reads another person’s private notes, even if you are an owner or admin. For a meeting recorded by someone else and not shared, your agent receives the title and date from your card, not its content.
- What your agent can read is shown in Settings and when you authorize the connection. It can change according to the workspace’s owners and admins.
- In Codex, you can use remote OAuth without installing Node.js, opening PowerShell or copying a key.
- The manual CLI requires Node.js 18 or later.
Connect Codex without Terminal (recommended)
- In Codex, open Settings → MCP servers → Add server.
- Choose Streamable HTTP, name it “Notamos” and use:
https://notamos.app/api/mcp - Save and click Authenticate. Notamos will open in your browser.
- Sign in and choose the single workspace you want to give the agent access to. The others remain isolated.
- Restart Codex and type
/mcpto check that Notamos is connected. - Optional: to install the four skills in Codex, you need Node.js 18 or later and the Notamos CLI. First run npm install -g @notamos/cli, then:
notamos skills install --client codex
This method uses Notamos sign-in, PKCE and renewable tokens. It does not store your password in Codex or require pasting secrets.
Manual CLI alternative
Use this for Claude Code or other clients that do not yet support remote OAuth. First install npm install -g @notamos/cli and create the dedicated credential in Settings.
Command for your operating system
Paste the command without running it; then copy the key and press Enter in Terminal. This sends the key from the clipboard to the CLI without writing it to command history. Do not copy anything else between these steps.
Windows PowerShell
Get-Clipboard | notamos setup --token-stdin --client codexmacOS
pbpaste | notamos setup --token-stdin --client codexLinux with xclip
xclip -selection clipboard -o | notamos setup --token-stdin --client codex For Claude Code, replace codex with claude-code. For another client, first save the key with notamos mcp configure --token-stdin and use the STDIO configuration returned by notamos mcp print-config.
STDIO fallback in Codex Desktop for Windows
notamos setup --client codex also configures the desktop app, even if the codex command is not installed. If diagnostics still report a client error, check these values:
- Open Settings → MCP servers and create “Notamos”.
- For “Command”, use
C:\Program Files\nodejs\npx.cmd. If Node is installed elsewhere, PowerShell can find it with:(Get-Command npx.cmd).Source - Add four arguments on separate rows:
-y,@notamos/cli@latest,mcpandserve. - Leave the directory blank or use your user folder.
- Install the skills explicitly:
notamos skills install --client codex
“Authentication not supported” is normal only for this STDIO fallback. The recommended remote option should show the Authenticate button.
Check that everything is ready
notamos doctor --client codexnotamos mcp statusnotamos skills status --client codexAfter restarting, try in a new conversation:
Use Notamos to list my latest classes and their dates.Use Notamos to create interactive flashcards from my recent classes.Included academic skills
notamos-study-guideStructured guides with objectives, concepts, practice and sources.
notamos-flashcardsActive recall cards, also exportable as TSV or JSON.
notamos-quizQuizzes with answers, rubrics, grading and citations.
notamos-study-presentationPresentations with narrative, notes and sources for each slide.
The CLI installs these skills for Codex and Claude Code. Connecting MCP in Claude web, ChatGPT or Grok does not install these skills. The agent generates content using the user’s model and its capabilities; artifacts are not automatically saved in Notamos.
Other MCP clients
Get the STDIO configuration without including the key:
notamos mcp print-config The remote endpoint is https://notamos.app/api/mcp. HTTP clients that support headers can use the credential as Authorization: Bearer ….
Available tools
get_workspace_profileConfirms the workspace and its category.
list_coursesLists courses and folders with pagination.
list_notesBrowses notes by course and date.
search_notesSearches text and returns excerpts you can cite.
get_noteReads authorized summaries and metadata; transcripts are retrieved separately.
get_transcript_segmentsReads transcript segments, speakers and timestamps.
list_tasksReads tasks and calendar dates.
list_momentsReads flags and analyzed moments.
Security and limits
- OAuth uses PKCE and renewable credentials. For manual keys, the server stores only the hash; the CLI stores the key in a local file with restricted permissions (0600).
- Each request revalidates membership, workspace, permissions and PHI status.
- In a work workspace, disabling external agents or access to shared content takes effect immediately for existing connections. Owners and admins can pause access at any time without deleting the connection. Leaving the workspace revokes your connections to it.
- If you share a note with the company or a team in a workspace where agents can read shared content, agents belonging to people who can see it can read the full transcript too. Content already read by an agent cannot be taken back.
- Tools are read-only and have pagination and usage limits.
- Generation happens in your agent: skills do not call
/api/askor consume a Notamos generation. - Audit logs record the tool and client, not the query or its content.
Troubleshooting
The key is not in MCP format
Copy only the key that begins with ntm_mcp_.
Codex says Notamos is unavailable
If using OAuth, confirm the URL, click Authenticate and restart Codex. If using the fallback, run notamos doctor --client codex.
Skills are missing
Run notamos skills install --client codex or --client claude-code and restart the client.
The note is missing
Confirm that the connection was created in the correct workspace and that you still have access to the note.