# MCP servers in Claude Code

> Connect an HTTP or local MCP server, choose its scope, and test a tool call.

Page: https://videotomd.com/b/kkBFmwkDzdo/
Tool: Claude Code · Tags: mcp · 479 words, about 623 tokens
Pills: free · checked 2026-10-15 · Claude Code · file tools · shell · web · MCP · on demand · frontier · coding · starting out · building

## Recipe

- Kind: workflow
- Stage: starting out, building
- Loads: on demand
- Works in: Claude Code
- Needs: file tools, shell, web, MCP
- Bring: nothing
- Cost: free
- Model: frontier
- Tested in: not yet
- Checked: 2026-10-15
- For: coding

## Similar
- [Custom MCP Web Scraper Server](https://videotomd.com/b/taTz0Ju-_sQ/): Pick it when no existing server does the job and you need to write and run your own local stdio server before you connect it.
- [Build an MCP server in Python with OAuth](https://videotomd.com/b/He8tUwLzLnU/): Pick it when you are the one running the server and other people will connect to it, so you need real OAuth access control on the server side, not just a token from the client.

## Put it here

Loads on demand: paste or attach it when the task comes up. To have it every session, put it where your tool reads instructions:

- Claude Code: Save as CLAUDE.md in the project root, or .claude/CLAUDE.md. Other agents share the repo: put the shared rules in AGENTS.md and make CLAUDE.md one line, @AGENTS.md. Commit it. Start a new session: the file is read at launch. Reload: new session (or /memory to open the files). Check it loaded: /context lists the Memory files it read; /skills, /agents, /hooks list the rest; the InstructionsLoaded hook event fires once per loaded instruction file. Source: https://code.claude.com/docs/en/memory (checked 2026-10-12).

## Access

Membership: plans at https://videotomd.com/pricing/, or email then a plan at https://videotomd.com/b/kkBFmwkDzdo/. A member's browser downloads the file there; an AI without that session needs the member to attach it.