Skip to main content
Give your assistant access to your accounts. Connect once, and your assistant uses the right app when you ask. No per-app setup, no tokens in your code.

How it works

You keep your sign-in. NEUS adds the authority check before any app runs.

Connect an account

  1. Open your Profile in NEUS.
  2. Go to Trust graph → Connections.
  3. Pick an app and click Connect.
  4. Authorize in the provider’s window.
  5. Done. Your assistant can now use that account when you ask.
You can connect more than one account per provider (for example, two Google accounts). Each connection is separate.

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”
Your assistant finds the right tool, checks your permissions, and runs. If you haven’t connected the app yet, it tells you to connect first.

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.
You can disconnect any account at any time from Profile → Trust graph → Connections.

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:
  1. Go to Profile → Trust graph → Connections.
  2. Click Add connection.
  3. Paste the MCP server URL and API key.
  4. 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.
Next: Agents and authority
Last modified on August 18, 2026