WEIR

Warp MCP Servers: Add a Remote URL, Sign In and Approve

Add a remote server to Warp MCP servers: the url and headers keys, ~/.warp/.mcp.json, browser sign-in, allowlists for tool calls and a real search's cost.


Published · Updated · 6 min read

Cover image: X research in Warp's agent

Warp MCP setup for a remote server is one url entry, pasted on the MCP servers page or saved in ~/.warp/.mcp.json.

This guide adds Weir, so Warp's agent can search X (Twitter) and read posts, threads and profiles from your terminal. Weir only reads, so it never posts as you. We run Weir.

{
  "mcpServers": {
    "weir": {
      "url": "https://api.weirapp.io/mcp"
    }
  }
}

Warp MCP servers: add Weir in four steps

You need Warp and a free Weir account.

We read Warp's docs, its changelog up to the 15 October 2026 release, and its open source code as of 22 October.

  1. Open MCP serversGo to Settings, then Agents, then MCP servers. Or search the Command Palette for Open MCP Servers.
  2. Paste the entryClick + Add, paste the JSON above and save.
  3. Sign inStart weir if it isn't running. Warp opens your browser, so sign in to Weir and approve.
  4. Ask the free questionAsk the agent "What's my Weir usage?" It calls get_usage, which costs nothing.

Rather keep it in a file? Save the same JSON as ~/.warp/.mcp.json. Warp starts global servers from it by itself, while a project's .warp/.mcp.json needs a manual start each session.

Set up in Claude Code or Codex already? Warp reads their MCP configs too. Turn on "Auto-spawn servers from third-party agents" on the MCP servers page to start them.

Warp's changelog from March 2026 says Settings, then AI. Its docs now put MCP servers under Agents.

Which keys does a Warp MCP server entry take?

Warp's docs list two keys for a URL server, and Weir needs only url:

Key Weir's value What it does
url https://api.weirapp.io/mcp The endpoint; Streamable HTTP
headers Authorization with a key Sends a key instead of signing in
command not used Starts a local server instead

Warp's code also reads serverUrl as url, and takes a servers wrapper as well as mcpServers.

Rather use a key? It suits a machine where nobody can click through a browser. Create one under API keys in your Weir dashboard:

{
  "mcpServers": {
    "weir": {
      "url": "https://api.weirapp.io/mcp",
      "headers": { "Authorization": "Bearer weir_live_your_key" }
    }
  }
}

The key sits in the file as plain text. Keep it in ~/.warp/.mcp.json, never in a project's .warp/.mcp.json that you commit. Weir's MCP docs cover both routes.

Does Warp support OAuth for MCP servers?

Yes. Warp's docs say starting a server without saved credentials opens a browser sign-in. Warp then stores the credentials on your device.

Here is what Warp's open source code does with Weir:

  • There's no client ID to paste. Warp registers itself through dynamic client registration, under the name "Warp".
  • The callback goes to the app. The desktop app returns to warp://mcp/oauth2callback, an app link that Weir accepts.
  • Cloud agents can't sign in. Warp refuses browser sign-in in headless runs, so those need a key in a header.
  • A new machine signs in again, Warp's docs say. You can revoke credentials from the MCP servers page.

The link shows as "Warp (MCP)" under API keys in your Weir dashboard. Revoke it there to cut Warp off.

How does Warp's agent approve MCP tool calls?

Warp sets this per profile, under Settings, then Agents, then Profiles. Its docs offer an MCP allowlist, an MCP denylist and "Agent decides".

Here is how Warp's code handled an MCP call as of 22 October 2026:

Setting Weir on no list On the allowlist On the denylist
Agent decides (default) Asks Runs Asks
Always ask Asks Runs Asks
Always allow Runs Runs Asks

The lists work per server, not per tool. Put Weir on the allowlist and its paid searches run without asking too.

The approval card names the tool and its server, so check limit before you allow it. Account tools like get_usage are free.

Can Warp's agent read X (Twitter)? A worked task

Yes. Say you want Warp's latest news before you update. Ask the agent:

Use weir: what's the latest @warpdotdev post on X? Skip replies and reposts.

The agent should pick search_x. We ran that call through Weir's MCP server on 24 October 2026:

→ search_x {"fromUsers": ["warpdotdev"], "query": "-filter:nativeretweets",
            "onlyOriginal": true, "since": "2026-10-01T00:00:00Z", "limit": 1}
← 1 post · 2 credits (1 + 1 × 1) · nextCursor set
  Oct 23  17 likes  2,843 views  "If an agent's PR doesn't have a screenshot verification..."

The post quotes another account's post, which we leave out. X search returns reposts by default, so -filter:nativeretweets drops them, and onlyOriginal drops replies.

2credits for our 1-post search
11credits for a 10-post search
0credits for get_usage
5,000free Weir credits every month

Weir bills 1 credit per call plus 1 per X post, and failed calls are free. Packs start at $5 for 25,000 credits and never expire, as of October 2026. See every rate on our pricing page.

What we haven't tested

We can't run Warp here. This guide comes from Warp's docs, changelog and source, plus a real call through Weir's MCP server.

  • Warp's sign-in against Weir. Weir accepts the registration and callback Warp's code uses, but we haven't clicked through it.
  • Cloud agents. Warp sets up MCP for them separately, and we haven't run Weir there.

If it doesn't work

  • Weir won't start. Click View Logs on the MCP servers page, and check the URL is exactly https://api.weirapp.io/mcp.
  • Sign-in keeps failing. Warp's docs suggest deleting ~/.mcp-auth, which clears every MCP sign-in. Then start Weir again.
  • A key isn't accepted. Send it as Authorization: Bearer <key>, and check it with Weir's free GET /v1/whoami.
  • A tool returns 402. Your Weir credits ran out, and retrying won't help.

When not to use Weir

  • Warp's agent has to post, reply or DM. Weir is read-only.
  • You want private data. Weir reads public posts, not your bookmarks, DMs or home timeline.
  • Price per post matters most. TwitterAPI.io lists $0.15 per 1,000 tweets as of October 2026, less than our $5 pack.
  • You need a guarantee. Weir isn't licensed by X or affiliated with it, so access can change.

FAQ

Where are Warp MCP servers configured?

In Settings, then Agents, then MCP servers, or under Personal, then MCP Servers in Warp Drive. File-based servers live in ~/.warp/.mcp.json, or in .warp/.mcp.json at a project's root.

Is Warp an MCP client?

Yes. Warp's local agents connect to MCP servers over Streamable HTTP, SSE or a local command. Its cloud agents have their own MCP setup, Warp's docs say.

Does Warp MCP need a paid plan?

Warp's MCP docs and pricing page name no plan for MCP. The agent's model use costs money, though. As of October 2026, Build costs $20 a month and includes that much usage, while Free pays as you go or brings its own model.

Can Warp post to X through Weir?

No. Weir only reads public X data, so nothing can post, like or follow through it. Its tools search posts, read threads and replies, and look up profiles, lists and Spaces.

Sources

All checked on 24 October 2026: