What is the difference between Claude Desktop and Claude Code for MCP servers?

Claude Desktop is the GUI chat app — MCP config goes in a JSON file under Application Support. Claude Code is the CLI agent — MCP servers are added with `claude mcp add` and stored in your project or user config. Both speak the same MCP protocol, so the same Zillapi MCP server works in either, but the install command is different.

Can I scope the Zillow MCP to one project in Claude Code?

Yes. `claude mcp add` defaults to user scope (every Claude Code session sees the server). Add `--scope project` to scope it to the current directory only, which writes a .mcp.json file to your project root. Add `--scope local` to scope it to one terminal session.

Do I need to install anything beyond Claude Code?

No. The Zillapi MCP server is hosted at api.zillapi.com/mcp. Claude Code calls it over HTTPS using the streamable-http transport built into the CLI. There's no SDK, no Python package, no Node module to install for the MCP path.

How do I remove the Zillow MCP server later?

Run `claude mcp remove zillapi`. If you added it with --scope project, also delete the entry from .mcp.json in the project root. Removing the server does not affect your API key or credits.

Can Claude Code call the Zillow REST API directly without MCP?

Yes. You can use the agent skills at github.com/nikhonit/zillow-skills (install with `npx skills add nikhonit/zillow-skills`) or just curl the REST endpoints from inside a Claude Code session. MCP is the cleanest path because tool definitions and auth are wired up once, then the model routes calls automatically.

← Blog

Connect Zillow to Claude Code in 60s

Add Zillapi's MCP server to Claude Code with one CLI command. Pull Zestimates, listings, and property records into your terminal agent.

By Zillapi May 12, 2026

Wire Zillow data into Claude Code with one command. Get a free Zillapi key — 100 credits, no card required — run claude mcp add with the streamable-http transport and the server URL, and the agent has property lookups, Zestimates, and listing search available in every session.

This guide is the one-line install, the scope flag you actually want, the verification commands, and the four prompts that prove it works.

The 60-second install

claude mcp add \
  --transport http zillapi \
  https://api.zillapi.com/mcp \
  --header "Authorization=Bearer zk_YOUR_KEY"

That’s it. Replace zk_YOUR_KEY with the API key from your Zillapi dashboard (sign up first if you haven’t — 100 free credits, no card).

The default scope is user — every Claude Code session on your machine sees the Zillapi server. If you only want it in one project, add --scope project and the entry goes in a .mcp.json file at the project root, where you can commit it for teammates.

Verify the connection

claude mcp list

You should see:

zillapi    https://api.zillapi.com/mcp    connected

Inside a Claude Code session, type /mcp to inspect the server. The four tools — lookup_property_by_address, lookup_property_by_zpid, get_zestimate, search_listings — should appear under zillapi.

Try it

In a Claude Code session, ask:

“Look up 17 Zelma Dr, Greenville SC and tell me the Zestimate and last sale price.”
“Find sold 3-bedroom houses in Austin TX in the last 90 days under $600k.”
“Pull this Zillow URL and summarize what’s interesting about it.”
“Who’s the listing agent on zpid 12345678?”

The agent picks the right tool, calls the MCP server, and returns structured data inline. You can pipe that into a script, a CSV, or just keep iterating.

Scope flags — which to use

Scope	What it does	Use when
`--scope user` (default)	Available in every Claude Code session on this machine	You always want Zillow data on-tap
`--scope project`	Writes `.mcp.json` to the current dir; available only in this project	You’re building a real-estate-specific app and want teammates to inherit the config
`--scope local`	Available only in the current terminal session	You’re experimenting and don’t want the entry to persist

For most users, the default (user scope) is right.

Troubleshooting

claude mcp add says “command not found”. Update Claude Code — mcp add is in 1.0.30 and later. Run claude --version to check.

claude mcp list shows status failed. Run claude mcp get zillapi to see the resolved URL and headers, then test the URL with curl:

curl -X POST https://api.zillapi.com/mcp \
  -H "Authorization: Bearer zk_YOUR_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

If curl returns 401, the key is wrong. If it returns 200, the issue is in how the header was added — re-run claude mcp add with the exact syntax above.

Tools show up but every call returns “Tool not available”. Restart the Claude Code session. The tool list is cached per session and only refreshes on start.

Calls return 429 Too Many Requests. Rate limit. Free plan is 20/min, Monthly is 200/min, Annual is 300/min. Wait, then retry — or upgrade at zillapi.com/pricing.

What you can build with this

Claude Code with the Zillapi MCP server connected is a thin shell on top of 300+ property fields. A few starting points:

A script that drops a CSV of comps for any address.
An overnight job that pulls fresh Zestimates for a watch list of zpids.
A REPL where you paste a Zillow URL and get an investor pitch back.
A test harness that snapshots listing data across your target ZIP codes.

The same Zillapi key works in Claude Desktop, Cursor, ChatGPT, and the standalone Python skills at github.com/nikhonit/zillow-skills.

Don’t have a key yet? Sign up free at zillapi.com/signup — 100 credits, no card required. Paid plans start at $5/month if you outgrow it.

Frequently asked questions

What is the difference between Claude Desktop and Claude Code for MCP servers?: Claude Desktop is the GUI chat app — MCP config goes in a JSON file under Application Support. Claude Code is the CLI agent — MCP servers are added with `claude mcp add` and stored in your project or user config. Both speak the same MCP protocol, so the same Zillapi MCP server works in either, but the install command is different.
Can I scope the Zillow MCP to one project in Claude Code?: Yes. `claude mcp add` defaults to user scope (every Claude Code session sees the server). Add `--scope project` to scope it to the current directory only, which writes a .mcp.json file to your project root. Add `--scope local` to scope it to one terminal session.
Do I need to install anything beyond Claude Code?: No. The Zillapi MCP server is hosted at api.zillapi.com/mcp. Claude Code calls it over HTTPS using the streamable-http transport built into the CLI. There's no SDK, no Python package, no Node module to install for the MCP path.
How do I remove the Zillow MCP server later?: Run `claude mcp remove zillapi`. If you added it with --scope project, also delete the entry from .mcp.json in the project root. Removing the server does not affect your API key or credits.
Can Claude Code call the Zillow REST API directly without MCP?: Yes. You can use the agent skills at github.com/nikhonit/zillow-skills (install with `npx skills add nikhonit/zillow-skills`) or just curl the REST endpoints from inside a Claude Code session. MCP is the cleanest path because tool definitions and auth are wired up once, then the model routes calls automatically.