Aura Backend - Advanced AI Companion

Created By
angrysky56a year ago
Aura system (Adaptive socio-biological emotional knowledge ecosystem) now has fully functioning fluid internal memory and MCP server Client ie web search file read write, code execution, anything- for free!!!
Overview

What is Aura Backend?

Aura Backend is an advanced AI companion system that integrates emotional intelligence and sophisticated memory systems to provide personalized interactions and insights.

How to use Aura Backend?

To use Aura Backend, clone the repository, set up the environment with the required dependencies, and run the application. You can interact with the API endpoints for various functionalities.

Key features of Aura Backend?

  • Real-time emotional state detection and cognitive focus tracking.
  • Persistent conversation memory with vector database integration.
  • Model Context Protocol (MCP) integration for external tool compatibility.
  • Advanced analytics for emotional trend analysis and cognitive pattern recognition.

Use cases of Aura Backend?

  1. Providing emotional support through personalized interactions.
  2. Analyzing user emotional patterns over time for better engagement.
  3. Integrating with external tools for enhanced functionality.

FAQ from Aura Backend?

  • Can Aura Backend analyze emotional states?

Yes! It can detect and analyze various emotional states in real-time.

  • Is Aura Backend free to use?

Yes! Aura Backend is open-source and free to use.

  • What are the system requirements?

You need Python 3.12+, at least 4GB RAM, and 2GB+ storage space.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
angrysky56
Star
3
Language
Python
License
-
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Voyei

4 hours ago