Weft — turn any website into an MCP server

Your tools have APIs. You just can't get keys.

Most web apps you use every day talk to a perfectly good JSON API behind the scenes — but there's no public API, no key you're allowed to create, or it's locked behind an enterprise plan. Weft lets your AI use that same API, as you, from your own machine.

No API keys

Weft rides the session you already have in Chrome. If you can see it in the browser, your AI can ask for it.

Local-only

Everything runs on 127.0.0.1. Nothing goes to us or anyone else — there is no "us" in the loop.

Any MCP client

One click connects Claude Code, Claude Desktop, Codex or Cursor. Ask in plain English; Weft handles the calls.

Set up a site once. Use it forever.

Three steps, about a minute per site.

Convert the site

Open a site you're logged into and click Convert this site to MCP in the Weft extension.

Use it once

Browse the pages you care about. Weft watches the site's own API calls and maps each one into a tool.

Ask your AI

Connect your AI client from the Weft app, restart it, and ask. It calls the same API the website does — with your session.

The Weft desktop app showing Medium converted and ready

The Weft app: every site you've converted, its status, and the endpoints it learned.

Real example: your Medium stats, in Claude Code

Medium has no public stats API. With Weft, Claude Code queries Medium's own GraphQL API — the one the Medium web app uses — through the session you're already signed into.

No scraping, no copied cookies, no third-party server. Anything other than a GET needs explicit confirmation, so you see the exact query before it runs.

See how to ask →

Claude Code answering a question about Medium post stats using Weft

Works with the AI tools you already use

Weft speaks the Model Context Protocol, so any MCP client can use it. These four are set up in one click from the app.

Claude CodeClaude DesktopCodexCursor

Built so your credentials never leave your browser

Weft records cookie names and storage keys to understand how a site authenticates — never their values. When your AI makes a call, the request is replayed inside your own browser tab, using the session that's already there.

What Weft does — and doesn't do

Runs entirely on 127.0.0.1 — no cloud, no account, no telemetry
Only captures sites you explicitly convert
Cookie and token values never leave your browser — not even to the Weft app
Read requests run freely; anything that changes data needs confirm: true
Every call is visible in the app's audit log
Open source (MIT) — read the threat model

FAQ

Is this allowed by the sites I use?

Weft uses your own account, from your own machine, at human scale — the same requests your browser makes when you click around. Still, every site has its own terms. Use it for your own data and your own workflows, and don't use it to scrape or bulk-download.

Which sites work?

Any site that loads its data from a JSON or GraphQL API in the browser — which is most modern web apps (Medium, Linear, Notion-style tools, dashboards, admin panels). Sites that sign every request or only stream over WebSockets are flagged as "not possible".

Does my AI see my password or cookies?

No. Your AI sees endpoint descriptions and the JSON responses. Cookie and token values stay in Chrome; Weft only ever sees their names.

What do I need installed?

Chrome (or another Chromium browser), Node.js 20+, and an MCP client such as Claude Code. Weft runs on macOS, Windows and Linux.

Is it free?

Yes — free and open source under the MIT license. No account, no paid tier.

Turn any website you're logged into into an MCP server