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.

Let an agent explore the catalog.

The public catalog tools need no token: an agent can list published setups, read one in full, find setups within a reported capacity, search by keyword and filters, find setups similar to one, start from a task, or summarise what a task actually reports. Read-only, published data only, and missing capacity is never estimated.

Public toolslist_catalogget_catalog_setupfind_setups_for_capacitysearch_setupssimilar_setupscapacity_forby_task

Turn “can I run this?” into a personal answer.

Can I run it locally? shows what other people run within a memory budget. With the read-only catalog tools, your own agent answers the same question for your exact machine, task and constraints, grounded in those setups and citing them. It calls capacity_for and search_setups, then similar_setups or get_catalog_setup when it needs more.

Example brief: “I have an 8GB GPU and want to extract data from invoices, plus the odd small script. Using the vram.wiki catalog, tell me what people actually run for this and at what reported speed, and cite the entry IDs you used.” The agent must never invent a setup or estimate memory; when nothing matches, it says so and invites you to add your own setup.

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 accesscatalog:readsetups: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.