🤖 YETR AI Agent - Your Enhanced Task Runner

Created By
yethikrishnaa year ago
🤖 YETR AI Agent - Your Enhanced Task Runner. Powerful AI agent system that connects to multiple MCP servers simultaneously, providing unified access to diverse tools and data sources through a modern web interface.
Overview

what is YETR AI Agent?

YETR AI Agent is an advanced AI agent system designed to connect to multiple Model Context Protocol (MCP) servers simultaneously, providing users with unified access to various tools and data sources through a modern web interface.

how to use YETR AI Agent?

To use YETR AI Agent, visit the live demo at yethikrishna.github.io/yetr-ai-agent or clone the repository from GitHub and follow the setup instructions for local development.

key features of YETR AI Agent?

  • Advanced AI Engine: Utilizes sophisticated natural language processing for intelligent task management.
  • Multi-MCP Integration: Connects to over 50 MCP servers for diverse tool access.
  • Interactive Chat Interface: Offers real-time responses and context-aware conversations.
  • Tool Discovery & Orchestration: Automatically discovers tools and manages task execution across servers.

use cases of YETR AI Agent?

  1. Automating development tasks such as repository analysis and deployment.
  2. Managing project workflows across multiple tools for enhanced collaboration.
  3. Integrating data from various sources for real-time synchronization and reporting.

FAQ from YETR AI Agent?

  • Can YETR AI Agent connect to any MCP server?

Yes, it supports connections to a wide range of MCP servers including GitHub, GitLab, and various databases.

  • Is there a demo available?

Yes, you can try the interactive demo on the live website.

  • What technologies are used in YETR AI Agent?

The project uses React, FastAPI, PostgreSQL, and various AI/ML models for its functionalities.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
yethikrishna
Star
0
Language
TypeScript
License
-

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)

a day ago