How it works
Connect an account
- Open your Profile in NEUS.
- Go to Trust graph → Connections.
- Pick an app and click Connect.
- Authorize in the provider’s window.
- Done. Your assistant can now use that account when you ask.
What you can connect
The backend details (how each app is wired) stay under the hood. You just see “Connect” and “Connected.”
Ask your assistant
Once connected, just ask:- “Read my latest emails”
- “Find the Q3 roadmap in my Drive”
- “Send a Slack message to the engineering channel”
- “Create a GitHub issue for this bug”
Permissions and control
Your assistant only does what you allow. Every call goes through a permission check:- Reads (email, files, messages) run when you ask.
- Sends, creates, and deletes go through your delegation policy. You can require approval for high-impact actions.
- Every action is recorded as a saved result you can review.
For developers
Call a connected account from your app
Use the NEUS SDK or API to call a connected account on behalf of a user. The user must have connected the account first.Search 1,200+ apps
Use Composio-powered tool discovery to find the right tool for a natural-language query:Add a custom MCP server
For apps that expose their own MCP server (like Figma), connect the server URL directly:- Go to Profile → Trust graph → Connections.
- Click Add connection.
- Paste the MCP server URL and API key.
- Your assistant discovers the server’s tools at runtime.
Security
- NEUS never stores your provider tokens for Composio-managed apps. Composio handles auth, refresh, and storage.
- For native OAuth apps (Google, Microsoft, GitHub, Linear, Slack), tokens are encrypted and sealed in private storage, never exposed to the browser or assistant.
- Every call is checked against your delegation policy before it runs.
- Every action is saved as a verifiable result.
