Vrchat Mcp

Created By
sawa-zena year ago
This project is a Model Context Protocol (MCP) server for interacting with the VRChat API.
Overview

What is VRChat MCP?

VRChat MCP (Model Context Protocol) is a server designed for interacting with the VRChat API, allowing users to retrieve various information from VRChat using a standardized protocol.

How to use VRChat MCP?

To use VRChat MCP, clone the repository from GitHub, install the dependencies, set up your environment variables, and start the server to interact with the VRChat API.

Key features of VRChat MCP?

  • User authentication and information retrieval
  • Access to avatar and world data
  • Support for various VRChat API endpoints

Use cases of VRChat MCP?

  1. Retrieving user profiles and friends list from VRChat.
  2. Accessing avatar details and world information.
  3. Integrating VRChat functionalities into other applications.

FAQ from VRChat MCP?

  • Is VRChat MCP free to use?

Yes! VRChat MCP is free to use for everyone.

  • What programming language is used?

The project is developed in TypeScript.

  • How can I contribute to the project?

Contributions are welcome! You can fork the repository and submit a pull request for improvements or bug fixes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
sawa-zen
Star
34
Language
TypeScript
License
MIT license
Tags

Recommend Servers

View All
Voyei

2 hours ago
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