Your first context server

Build an MCP server from the documentation you already keep open in browser tabs, so your AI editor stops inventing functions. No terminal, no server code.

Build absolutely anything...with the right context.

Audience	Anyone building with an AI editor who is tired of hallucinated APIs
Prerequisites	An MCP Studio account and three or four documentation links
Time	About 2 minutes

Want the why first?

This tutorial is just the steps. Vibe coding without the hallucinations explains why AI editors invent functions in the first place, and MCP for vibe coders is the short overview.

Step 1 — Collect your links

Look at the documentation tabs you keep open while building. Copy those URLs into a note.

Three or four is the right number to start. Good candidates:

• Your framework's documentation
• The UI library you are using
• Your database or backend service's getting-started guide
• Whatever you deploy with

Narrower is better

If a docs site is huge, use the URL of the section you actually read rather than the homepage. A narrow source returns better answers because the search has less unrelated material to rank against.

Step 2 — Create the server

1. Go to the wizard.
2. Start a new server and name it something you will recognise later, like my-app-docs.

Step 3 — Paste your links

In the Sources step, paste one URL per source. Each is validated as you add it, and MCP Studio estimates how large the crawl will be.

The free tier includes two sources per server. If you have more links than that, start with the two you consult most.

Step 4 — Keep the suggested tools

The defaults are fine. If you want to be deliberate, confirm these two are on:

Tool	What it does
ask_question	Answers plain-English questions from your sources
get_code_examples	Returns snippets the library authors actually wrote

Step 5 — Deploy

Click through Review and press Deploy. You get a URL and a small block of JSON. Indexing continues in the background; the server works immediately.

Step 6 — Paste the JSON into your editor

{
  "mcpServers": {
    "my-app-docs": {
      "url": "https://appatools.com/mcp-studio/api/mcp/my-app-docs-q7t4n1"
    }
  }
}

Where this goes depends on your editor:

Editor	Location
Cursor	.cursor/mcp.json in your project folder — create it if it does not exist
Claude Desktop	Settings → Developer → Edit Config
Windsurf	Settings → MCP Servers

Full details in Connect to AI clients.

Step 7 — Restart your editor

Not optional. Editors read MCP configuration at startup, and skipping this is the most common reason people conclude it did not work.

Step 8 — Test it

Ask something your editor got wrong before. Or try one of these:

• "What options does this component actually accept?"
• "Show me the real example from the docs for setting this up."
• "Is this function still supported, or was it replaced?"

That last question is the interesting one. An editor working from memory cannot tell you what changed after its training cutoff. One reading current documentation can.

You will know it worked when answers arrive with a citation — the page and passage they came from. If there is no citation, the editor is not calling your server. Recheck the config location and confirm you restarted.

Troubleshooting

Symptom	Cause
No citations in answers	Editor not restarted, or config in the wrong location
Answers are vague	Sources too broad — scope them to the section you actually use
A source failed to add	Site blocks crawlers, or requires a login. Try the GitHub repo instead
"Source limit reached"	Free tier allows two sources per server. Create a second server or remove one

Related

• MCP for vibe coders — the overview page
• Vibe coding without the hallucinations — why this happens and why prompting harder does not fix it
• Create an MCP server — the full wizard reference
• Choose tools — all ten tools explained