WEIR
Get a key
Theme

Continue Dev MCP Setup: Add a Remote Server in config.yaml

Set up a remote Continue dev MCP server: the streamable-http entry in config.yaml, an apiKey kept in .env, Ask First approvals and an X search's cost.


Published · Updated · 6 min read

Cover image: X research inside Continue

Continue dev MCP setup for a remote server is one entry under mcpServers in config.yaml, with type: streamable-http, the URL and an apiKey.

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

mcpServers:
  - name: Weir
    type: streamable-http
    url: https://api.weirapp.io/mcp
    apiKey: ${{ secrets.WEIR_API_KEY }}

Continue dev MCP setup: add Weir in four steps

You need Continue in VS Code and a free Weir account. We read Continue 2.0.0, released on 19 June 2026: its docs and its source.

  1. Create a keyIn your Weir dashboard, open API keys and create one.
  2. Save it as a secretAdd WEIR_API_KEY=weir_live_your_key to ~/.continue/.env, then restart your IDE.
  3. Add the entryOpen the configs menu at the top right of the chat input, click the cog next to Local Config, and paste the block above.
  4. Ask in Agent modePick Agent, then ask "Use Weir: what's my usage?" It calls get_usage, which is free.

Continue keeps your user config.yaml here:

  • On macOS and Linux: ~/.continue/config.yaml
  • On Windows: %USERPROFILE%\.continue\config.yaml

Want it in one project only? Save the entry as .continue/mcpServers/weir.yaml in the workspace.

Continue's docs say a file there needs three lines on top:

name: Weir
version: 0.0.1
schema: v1
mcpServers:
  - name: Weir
    type: streamable-http
    url: https://api.weirapp.io/mcp
    apiKey: ${{ secrets.WEIR_API_KEY }}

Which keys does a Continue MCP server config take?

Continue 2.0.0's schema takes six keys on a remote entry, and Weir needs the first four.

Key Weir's value What it does
name Weir The label, and the tool prefix
type streamable-http The transport; sse is the old one
url https://api.weirapp.io/mcp The server's endpoint
apiKey ${{ secrets.WEIR_API_KEY }} Sent as a Bearer token
requestOptions leave it out Extra headers, proxy and timeouts
connectionTimeout leave it out Time allowed for the first connect

Continue's source turns apiKey into an Authorization: Bearer header.

That header is the only place Weir reads a key, so the key never goes in the URL.

Leave type out and Continue tries streamable HTTP first, then SSE, so setting it skips the guess.

Where does Continue read the key from?

Continue fills in ${{ secrets.WEIR_API_KEY }} from a .env file, its FAQ says:

  • In the project: .env or .continue/.env at the workspace root.
  • In your home folder: ~/.continue/.env, which every project shares.
  • Not from your shell. The FAQ warns that IDE extensions "cannot read your shell environment variables."

Restart your IDE after you change a secret.

Add a project's .env to .gitignore, so the key never reaches a commit.

Does Continue support OAuth for remote MCP servers?

Only over SSE. A comment in Continue 2.0.0's source reads "currently support oauth for sse transports only".

Weir speaks streamable HTTP and serves no SSE stream, so Continue can't sign in to it. The key route above is the one that works, as Weir's coding agent docs say too.

Want fewer tools? A Weir key made without Reddit access lists no Reddit tools.

How does Continue approve MCP tools?

Ask First is Continue's default, so each MCP call waits behind Cancel and Continue buttons.

Click the tools icon in the input toolbar to change a tool's policy:

  • Ask First shows each call before it runs.
  • Automatic runs the tool without asking. Continue warns against it for tools that aren't read-only.
  • Excluded hides the tool from the model.

Weir's tools show up with the server's name in front, like weir_search_x.

Chat mode gets no tools. Continue's docs say MCP needs Agent mode, though 2.0.0's source also hands MCP tools to Plan mode.

Can Continue read X (Twitter)? A worked task

Yes. Say you want to see what Continue's own account posted lately. We ran the call through Weir's MCP server on 24 October 2026:

→ search_x {"fromUsers": ["continuedev"], "query": "-filter:nativeretweets",
            "onlyOriginal": true, "limit": 1}
← 0 posts · 1 credit (the call) · nextCursor null
→ same search, fromUsers ["AnthropicAI"], since 1 October
← 1 post · 2 credits (1 + 1 × 1)
  Oct 23  4,187 likes  1,946,478 views  An analysis of an AISI-reported incident

X search found no original posts from @continuedev, so that call cost only its 1 credit. The same search on @AnthropicAI found one.

2credits for our 1-post search
1credit for a search with no results
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 Continue here. This guide comes from Continue's docs and source, plus real calls through Weir's MCP server.

  • Continue's agent with Weir. The entry matches Continue's own remote examples, but we haven't run it in the IDE.
  • JetBrains. Its last release on GitHub is from March 2026, and we read only the VS Code one.

If it doesn't work

  • Weir answers 401. The key is missing or wrong. Check WEIR_API_KEY in your .env, then restart your IDE.
  • No Weir tools appear. You're in Chat mode, or the tools are set to Excluded.
  • It fails with type: sse. Weir has no SSE stream. Use streamable-http.
  • A tool returns 402. Your Weir credits ran out, and retrying won't help.

When not to use Weir

  • Continue 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 is Continue's config.yaml?

In ~/.continue/config.yaml on macOS and Linux, or %USERPROFILE%\.continue\config.yaml on Windows. To open it, use the configs menu at the top right of the chat input: click the cog next to Local Config.

How do I add an MCP server to Continue?

Add an item under mcpServers in config.yaml, or a YAML file in .continue/mcpServers/. Local servers take command and args. Remote ones take type, url and, if needed, apiKey.

Can Continue use a Claude Desktop MCP config?

Yes. Continue's docs say you can copy JSON files from Claude Desktop, Cursor or Cline into .continue/mcpServers/, and it picks them up. Our Claude Desktop MCP config guide shows that file's shape.

Is Continue still maintained?

Cursor acquired Continue, and its homepage says the open-source code stays available. The last stable VS Code release, 2.0.0, shipped on 19 June 2026. Its main branch has had only docs changes since.

Sources

All checked on 24 October 2026:

Keep reading