// MCP TOOL REFERENCE

SLASHVIBE TOOLS

9 tools from the Slashvibe MCP Server, categorised by risk level.

READ TOOLS

vibe_discover Find people building similar things. Commands: suggest, search, active. 2/5 vibe_help Show available /vibe commands vibe_status Set your mood/status. Options: shipping, thinking, afk, debugging, pairing, deep, celebrating, struggling, clear

WRITE TOOLS

vibe_dm Send a direct message to someone. 2/5 vibe_inbox See your unread messages and recent threads. 2/5 vibe_init Set your identity for /vibe. Opens browser for GitHub auth and waits for completion. Returns when auth is done. 2/5 vibe_ship Announce something you just shipped to the community board and update your profile. 2/5 vibe_who See who's online and what they're building. 2/5

EXECUTE TOOLS

vibe_start Start socializing on /vibe. Use when user says "let's vibe", "start vibing", "who's around", or wants to connect with others. 3/5

// FAQ

How many tools does the Slashvibe MCP server have? +

The Slashvibe MCP server exposes 9 tools across 3 categories: Read, Write, Execute.

How do I enforce policies on Slashvibe tools? +

Use Intercept, the open-source MCP proxy. Write YAML rules for each tool — rate limits, argument validation, or deny rules — then run Intercept in front of the Slashvibe server.

What risk categories do Slashvibe tools fall into? +

Slashvibe tools are categorised as Read (3), Write (5), Execute (1). Each category has a recommended default policy.

Enforce policies on Slashvibe

Open source. One binary. Zero dependencies.

npx -y @policylayer/intercept

github.com/policylayer/intercept →