Directory
AGENT / MCP

Keep your setup
current, with control.

vram.wiki is a community-built record of real local AI setups. An MCP-compatible agent can help you prepare a contribution, while you decide what it may access and nothing is published automatically.

Community project Human review before publication OAuth access you can revoke

A community wiki with a visible trail.

The project started from an r/LocalLLM discussion and is maintained as a curated community record. Read how the dataset is built and how data is handled before authorizing an agent.

Meet the project maintainer

What the connection can and cannot do.

ALLOWED
  • Read setups you have explicitly made available to the agent.
  • Prepare a complete new setup or revision proposal.
  • Read the status of proposals submitted through that connection.
NOT ALLOWED
  • Publish anything or bypass human moderation.
  • Read another contributor’s private data or moderation notes.
  • Access your GitHub repositories, email or GitHub token.

The agent sends the proposal content to vram.wiki. Review what it drafted before confirming a submission, and never include passwords, API keys or private client information.

You stay in the approval loop.

1

Add the endpoint in your MCP client. The client starts an OAuth flow with PKCE.

2

Sign in with GitHub and review the requested scopes on vram.wiki.

3

Allow the connection. Its access token expires after 15 minutes and its refresh token rotates automatically.

4

Revoke it immediately from Connected agents whenever you want.

Add this endpoint to your agent.

Copy the address into an MCP-compatible client and choose OAuth. The client will open the authorization page and return here only after you approve it.

Requested accesssetups:readproposals:readproposals:writesetups:create
https://vram.wiki/api/mcp

Connecting an agent is optional.

Use the route that matches your situation. Both routes enter the same human moderation queue.