MCP Access

VibeKit can expose a remote MCP endpoint at /api/mcp. It uses Better Auth and explicit user consent.

MCP is optional. Enable it in PRODUCT.json with features.mcp: true only when the product needs remote agent access. MCP_ENABLED=false is an additional deployment kill switch. It can turn MCP off, but it cannot turn a product-disabled capability on.

Security model

• Existing narrow MCP scopes remain read only.
• api:read exposes the full tRPC query surface available to the connected account.
• api:write exposes the full tRPC mutation surface and is never selected by default.
• Scopes limit what a client can access.
• Team access stays limited to approved current memberships.
• Admin scopes need a current admin account and explicit consent.
• Revocation blocks future access.
• Access audit records do not store tokens or result bodies.

Agent First setup

Ask your coding agent to use the MCP setup guidance in the auth skill.

Configure MCP access for my supported client.
Request only the scopes I need and prove revocation works. Use api:read for the full query API. Add api:write only when I explicitly need the client to change data.

A saved client entry is not proof of a working OAuth session. Test the actual client version you plan to support.