Shinkai Apps

Created By
dcSparka year ago
Shinkai is a two click install AI manager (Local and Remote) that allows you to create AI agents in 5 minutes or less using a simple UI. Agents and tools are exposed as an MCP Server.
Overview

What is Shinkai Apps?

Shinkai Apps is an AI manager that allows users to create AI agents quickly and easily, either locally or remotely, using a simple user interface.

How to use Shinkai Apps?

To use Shinkai Apps, clone the repository from GitHub, download the necessary binaries for your operating system, and follow the instructions to set up and run your desired project.

Key features of Shinkai Apps?

  • Rapid Agent Setup: Create and configure AI agents in under five minutes.
  • Local or Remote Operation: Run agents on your local machine or connect to a remote Shinkai Node.
  • MCP Server Integration: Easily expose agents and tools over an MCP server for automation.

Use cases of Shinkai Apps?

  1. Quickly deploying AI agents for various tasks.
  2. Automating workflows using AI tools.
  3. Managing multiple AI agents from a single interface.

FAQ from Shinkai Apps?

  • Can I run Shinkai Apps on any operating system?

Yes! Shinkai Apps supports MacOS, Linux, and Windows.

  • Is there a community for support?

Yes! You can join the Shinkai community on Discord for support and discussions.

  • How do I contribute to Shinkai Apps?

You can contribute by submitting issues or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dcSpark
Star
268
Language
TypeScript
License
Apache-2.0 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