Let the chat use your tools, with approval for writes.
Connect GitHub, Google Drive, Slack or your own database once, and the assistant can call its tools in any thread. Reads run on their own; anything that would change something asks you first.
- services over OAuth
- 10
- connectors of your own
- 3
- named tools
- 32
- Reading tree of acme/site
- Reading deploy.toml
- Cloudflare needs to be connected
Browse the integrations and what each one can access.
Every tool the assistant gets, whether it reads or writes, the scopes it asks the service for, and how to connect it. Taken from the code that runs the chat.
13 integrations shown
- DevelopmentGitHubWalk a repository tree, read its files and list its issues. Open an issue or comment on one when you approve it.Reads and writesPermissions
- CommunicationSlackList the channels your workspace exposes, and post a message to one when you approve it.Reads and writesPermissions
- ProductivityNotionSearch the pages you share by keyword, and create a page under one of them when you approve it.Reads and writesPermissions
- StorageGoogle DriveSearch your Drive by name or full text, then read a file. Docs, Sheets and Slides come back as text.Read onlyPermissions
- DevelopmentLinearList and search your issues, so a roadmap question gets answered from where the work is tracked.Read onlyPermissions
- DevelopmentJira and ConfluenceSearch Jira issues with JQL and Confluence pages by keyword, from one Atlassian grant.Read onlyPermissions
- StorageDropboxList a folder and read a file across your Dropbox.Read onlyPermissions
- InfrastructureCloudflareList zones, DNS records and Workers. Create, update or delete a DNS record when you approve it.Reads and writesPermissions
- CommunicationResendList your sending domains and read a sent email. Send real mail, or delete a domain, when you approve it.Reads and writesPermissions
- DevelopmentSupabaseList your organization's projects and read one. Create or delete a project when you approve it.Reads and writesPermissions
- ConnectorPostgres and MySQLPoint the assistant at your own Postgres or MySQL database. Reads run, anything else asks.Reads and writesPermissions
- ConnectorSSH serverGive the assistant a shell on a server of yours. Every single command asks first.Every call asksPermissions
- ConnectorMCP serverConnect any MCP server over HTTP or SSE. Its own tools appear with their real names.Reads and writesPermissions
Reads run. Writes wait for you.
Integrations are OAuth connections to services you already use. Connectors point at things of yours: a database, a server, an MCP server. Both follow the same gate.
- 01
You grant it once.
An integration goes through the service's own consent screen, so you see its scopes there. A connector's credentials are sealed and only decrypted for the length of one call.
- 02
Reads run.
Listing, searching and reading happen without a prompt, and only inside what you granted. A SQL read goes out as one statement in a read only transaction.
- 03
Writes stop and ask.
Posting, sending, creating and deleting pause the turn until you choose. Dangerous ones are marked as such and can only ever be approved one at a time.
CNAME docs.example.com → example.nemu.pageA old.example.comOn a connector, an allow list entry remembers that shape of call for one chat and one connector. It never carries over to another conversation.
Tokens go to your provider
The model deciding which tool to call runs on your own key, and your provider bills those tokens. nemu never charges for one, and calling a tool is not something credits pay for.
Disconnecting is final
It removes the stored authorization permanently and the assistant loses access at once. Coming back means going through consent again.
Connect a service from the chat sidebar.
Switch it on in a thread and approve each write as it comes up. Disconnecting removes the access immediately.