VRChat MCP
Related Servers
Alternatives to VRChat MCP
No user-submitted related servers found.
Related Servers
- AlicenseCqualityBmaintenanceConnects an ER:LC private server's API to MCP clients so users can read live players, locations, vehicles, staff, queues, logs, bans, and emergency calls, and send remote server commands. It covers API v2 with v1 compatibility, structured error and rate-limit handling, and works over local stdio transport.17MIT
- FlicenseNot gradedqualityDmaintenanceA basic MCP server implementation for testing purposes. Communicates via stdio and is designed to work with MCP-compliant clients.-
- AlicenseAqualityCmaintenanceMCP server for Rocket.Chat — messages, DMs, search, files, and channels over stdio1224 PyPI1MIT
- AlicenseNot gradedqualityCmaintenanceMCP server for the Steam Web API, exposing your game library, playtime, achievements, friends, wishlist, and the Steam store to MCP clients over stdio.14 npmMIT
- AlicenseAqualityBmaintenanceZero-dependency MCP server and CLI that proxies, inspects, and analyzes JSON-RPC message streams between MCP clients and servers.3MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for Signal via signal-cli that enables sending and receiving messages, managing contacts and groups, and reacting over stdio.8 npm-
TDQS
Scored across 73 tools
Several clusters overlap heavily: five invite tools (vrchat_invite_user, vrchat_invite, vrchat_invite_self, vrchat_invite_user_to_me, vrchat_group_invite) are hard to tell apart, and the generic vrchat_read/vrchat_write/vrchat_delete layer duplicates most named tools. Event tools (event vs events, group_event vs group_events) also blur together, though descriptions do provide some guidance.
Names use a consistent vrchat_/vrcx_ snake_case prefix with mostly verb_noun ordering. Minor deviations exist (vrchat_me, vrchat_boop) and singular/plural mixing (event vs events), but the overall pattern is predictable and readable.
73 tools is very heavy for any single server, and the count is inflated by redundant invite/event variants plus a generic operations escape hatch. The broad VRChat domain justifies many tools, but this exceeds the workable range.
Coverage is broad: CRUD across events, posts, favorites, profile, avatar, status, instances, and groups, plus vrcx_ activity history. The generic read/write/delete layer ensures any missing operation is still reachable, though a few named surfaces (e.g. gallery update) are thin.