Connect Muse to LotsNotes
Ask Muse to read your business context in LotsNotes before it works, and keep it current. Add LotsNotes to Muse as a remote MCP server and sign in once.
LotsNotes MCP server URL
https://api.lotsnotes.com/mcpOr let Muse guide the setup: send it this prompt
Read https://lotsnotes.com/skill.md and help me connect LotsNotes for you.What Muse can do with LotsNotes
Once connected, Muse can:
- List your workspaces and folders, find notes by title and read only the notes the task needs. Workspace notes come back with every folder, so a workspace AGENTS.md reaches every agent.
- Create and update shared notes, move notes and folders, and create folders inside folders. Every note it returns carries its lotsnotes.com link.
- Read a note’s version history, restore an earlier version, and archive or restore notes and folders.
- Act as you, with your role: it sees only the folders you can access, and private notes are never returned to agents or the API.
The LotsNotes dashboard does the whole job too: write and organize notes, folders, workspaces and your team. Your agent for speed, the dashboard for control.
You need
- Muse, where it is available
- A LotsNotes account. You can create one during sign-in.
Connect Muse to LotsNotes
Ask Muse to add LotsNotes
Ask Muse to create a custom connector for LotsNotes. Share this endpoint and the API documentation at https://api.lotsnotes.com/docs. Muse guides the setup and asks for the authentication it needs.
https://api.lotsnotes.com/mcpSign in
When Muse asks how the server authenticates, choose sign-in. If it asks for a key instead, create one at https://www.lotstech.com/api and paste it into Muse’s credential prompt, never into the chat.
Set approval for changes
In Muse settings you can require approval for every action a connector takes. Keep it on for actions that change your data.
What to ask next
- “Read our AGENTS.md and the Marketing folder before you write anything”
- “Save this decision to the Product folder and send me the link”
- “Update the pricing FAQ note with today’s change”
If something goes wrong
- Muse cannot reach the server
- Check the URL ends in /mcp and that Muse chose HTTP, not a local command.
Steps checked on 1 October 2026 against Meta: Muse custom connectors.
Pricing
Current plans and prices are on https://lotsnotes.com/pricing. Your agent’s own plan or usage fees are separate.
Muse and LotsNotes: questions
How do I connect Muse to LotsNotes?
Follow the Muse setup above to add https://api.lotsnotes.com/mcp. Complete sign-in using the authentication method shown. Then ask “List my LotsNotes workspaces”.
Can I make Muse ask before it changes anything in LotsNotes?
Yes. In Muse settings you can require approval for every action a connector takes. Keep it on for actions that change your data.
Do I need an API key to use LotsNotes with Muse?
Only if the connector asks for one. Create one at https://www.lotstech.com/api and keep it out of chats, logs and committed files. Where Muse offers sign-in, use that instead.
What does LotsNotes cost?
Current plans and prices are on https://lotsnotes.com/pricing. Your agent’s own plan or usage fees are separate.
Can my agent read my private notes?
No. Private notes stay on lotsnotes.com and are never returned through MCP or the API. Shared notes follow your workspace roles.
Can my agent change or delete my notes?
Your agent can edit shared notes in the folders your role can edit, and it can trash or archive notes, delete a folder or, for a workspace you own, archive it. Notes and folders can be restored, a workspace you archive can be restored for 30 days, and every save keeps a version you can restore.
What stops two agents overwriting each other?
An agent can send the version it last read with a save. If the note changed since, the save is refused, and the agent reads it again and merges. Version history keeps every save either way.
Which folders can my agent see?
Your agent acts as you, with your role, so it sees only the workspaces and folders you can access. If you were given access to selected folders only, your agent sees those folders and no others.
Muse cannot reach the server
Check the URL ends in /mcp and that Muse chose HTTP, not a local command.
