DEV Community

Docat
Docat

Posted on

5 Claude Code Workflows That Replaced My Browser Tabs (2026)

#webdev #programming #ai #productivity

I used to have 15 browser tabs open at all times. CoinGecko for prices. Stripe Dashboard for revenue. Swagger UI for API docs. Weather.com before client calls. Google for currency conversions.

Then I discovered MCP servers — and closed most of them.

Quick context: MCP (Model Context Protocol) lets Claude connect to external tools and APIs directly. Instead of alt-tabbing to a browser, you just ask Claude. It calls the API, gets the data, and formats the answer — all inside your terminal or editor.

Here are 5 workflows that replaced my most-used browser tabs.

1. "What's Bitcoin at right now?" — Replaced my CoinGecko tab

The old way: Open CoinGecko. Wait for it to load. Scroll past the ads. Find the coin. Check the 24h change. Repeat every hour because you have no self-control.

The new way:

You: "What's BTC and ETH doing today? Compare their 7-day performance."
Claude: pulls live prices, 24h volume, market cap, and 7-day sparkline data
Enter fullscreen mode Exit fullscreen mode

I set up an MCP server that wraps the CoinGecko API and gives Claude access to 41 crypto tools — prices, trending coins, market data, historical charts, exchange info. The data is real-time, not cached from training.

What surprised me: I stopped checking crypto. I started asking about it only when I needed to. The compulsive tab-refreshing just... stopped.

Setup:

{
  "mcpServers": {
    "crypto": {
      "command": "npx",
      "args": ["-y", "mcp-openapi"],
      "env": {
        "API_BASE_URL": "https://api.coingecko.com",
        "OPENAPI_SPEC_URL": "https://docs.coingecko.com/openapi/3.0/coingecko-free-api.yaml"
      }
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

This uses mcp-openapi (free, open source) to auto-generate tools from CoinGecko's OpenAPI spec. I also built a pre-configured version ($7) that includes optimized tool descriptions and response formatting if you want it working in under a minute.

2. "How much did we make this month?" — Replaced my Stripe Dashboard tab

The old way: Log into Stripe. Click Payments. Set the date filter. Click Customers. Click Subscriptions. Open another tab for Stripe Docs because you forgot the webhook event name.

The new way:

You: "Show me this month's revenue, number of new subscribers, and top 5 customers by lifetime value."
Claude: queries Stripe's API across multiple endpoints, compiles the report
Enter fullscreen mode Exit fullscreen mode

This one changed my mornings. Instead of clicking through the Stripe dashboard for 10 minutes, I ask Claude one question and get a formatted summary. Revenue, churn, failed payments, upcoming renewals — all in one response.

The MCP server maps 11 endpoint groups from the Stripe API: charges, customers, subscriptions, invoices, payment intents, refunds, balance, products, prices, disputes, and events. Read-only by design — it uses a restricted Stripe key so Claude can query but never modify your payment data.

Setup:

{
  "mcpServers": {
    "stripe": {
      "command": "npx",
      "args": ["-y", "mcp-openapi"],
      "env": {
        "API_BASE_URL": "https://api.stripe.com",
        "OPENAPI_SPEC_URL": "https://raw.githubusercontent.com/stripe/openapi/master/openapi/spec3.json",
        "API_HEADERS": "Authorization: Bearer rk_live_your_restricted_key"
      }
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

Again, this uses mcp-openapi to generate tools from Stripe's official OpenAPI spec. There is also a pre-configured version ($12) with curated endpoints and response formatting that filters out the noise from Stripe's massive API surface.

3. "How does this API endpoint work?" — Replaced my Swagger UI tab

The old way: Find the API docs. Navigate to the right endpoint. Read the parameter descriptions. Copy the example. Paste into Postman. Fix the auth header. Send the request. Read the response. Go back to the docs for the next endpoint.

The new way:

You: "List all endpoints in the Petstore API that deal with inventory."
Claude: shows you the endpoints with parameters, types, and descriptions

You: "Call the getInventory endpoint."
Claude: makes the actual API call and returns the result
Enter fullscreen mode Exit fullscreen mode

This is the workflow I use the most. mcp-openapi takes any OpenAPI or Swagger spec URL and auto-generates one MCP tool per endpoint. Claude can then both explore and call the API in a single conversation.

It supports OpenAPI 3.x and Swagger 2.0, handles Bearer tokens, API keys, and OAuth2, and flattens nested parameter schemas so Claude actually understands what to send (this matters more than you think — I wrote about why).

Setup:

{
  "mcpServers": {
    "petstore": {
      "command": "npx",
      "args": ["-y", "mcp-openapi"],
      "env": {
        "API_BASE_URL": "https://petstore3.swagger.io",
        "OPENAPI_SPEC_URL": "https://petstore3.swagger.io/api/v3/openapi.json"
      }
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

Swap the URLs for any API that publishes a spec (most do). That is it. Zero config, zero code.

Install: npm install -g mcp-openapi or just use npx as shown above.

4. "Will it rain during my 2pm call?" — Replaced my Weather.com tab

The old way: Open weather.com. Close the cookie banner. Dismiss the push notification prompt. Scroll past the "feels like" widget, the air quality index, the 10-day forecast you did not ask for, and the sponsored content. Finally see the hourly forecast.

The new way:

You: "What's the weather in Taipei right now? Will it rain this afternoon?"
Claude: gives you temperature, humidity, conditions, and hourly forecast
Enter fullscreen mode Exit fullscreen mode

This one is free. I set up a weather MCP server using the Open-Meteo API (no API key required) and shared it as a free download. It is a good starter MCP server if you have never set one up before — zero cost, zero API keys, works out of the box.

Setup:

{
  "mcpServers": {
    "weather": {
      "command": "npx",
      "args": ["-y", "mcp-openapi"],
      "env": {
        "API_BASE_URL": "https://api.open-meteo.com",
        "OPENAPI_SPEC_URL": "https://raw.githubusercontent.com/open-meteo/open-meteo/main/openapi.yml"
      }
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

Three lines of config. No API key. Claude now knows the weather.

5. "How much is 4,500 EUR in TWD?" — Replaced my Google Currency tab

The old way: Open a new tab. Type "4500 EUR to TWD". Squint at the Google widget. Open another tab because you also need USD to JPY for a different invoice. Forget which number was which.

The new way:

You: "Convert 4,500 EUR to TWD, and while you're at it, 2,000 USD to JPY. Use today's rates."
Claude: fetches live exchange rates, does both conversions, shows the rates used
Enter fullscreen mode Exit fullscreen mode

Another free one. The Frankfurter API provides exchange rates from the European Central Bank — no API key, no rate limits, no nonsense. I packaged it as a free MCP config that gives Claude access to 30+ currency pairs.

Setup:

{
  "mcpServers": {
    "currency": {
      "command": "npx",
      "args": ["-y", "mcp-openapi"],
      "env": {
        "API_BASE_URL": "https://api.frankfurter.app",
        "OPENAPI_SPEC_URL": "https://api.frankfurter.app/openapi.json"
      }
    }
  }
}
Enter fullscreen mode Exit fullscreen mode

Especially useful if you do freelance work across currencies. No more mental math, no more stale Google rates from 3 hours ago.

How to Set All of This Up

Every workflow above uses the same core tool: mcp-openapi. It reads an OpenAPI spec and generates MCP tools automatically. The pattern is always the same:

  1. Find an API with a published OpenAPI/Swagger spec
  2. Add a mcpServers entry with the spec URL
  3. Ask Claude to do things with that API

You can combine multiple servers in your Claude config. Here is what my setup looks like:

{
  "mcpServers": {
    "crypto": { "command": "npx", "args": ["-y", "mcp-openapi"], "env": { "..." } },
    "stripe": { "command": "npx", "args": ["-y", "mcp-openapi"], "env": { "..." } },
    "weather": { "command": "npx", "args": ["-y", "mcp-openapi"], "env": { "..." } },
    "currency": { "command": "npx", "args": ["-y", "mcp-openapi"], "env": { "..." } }
  }
}
Enter fullscreen mode Exit fullscreen mode

Four lines per API. Four fewer browser tabs.

What Tab Would You Replace Next?

I still have a few tabs I have not killed yet (looking at you, Jira). But I went from 15 daily tabs to about 4, and most of those are just docs I am reading, not dashboards I am checking.

What browser tab would you most want to replace with a Claude workflow? Drop it in the comments — if there is a public API for it, there is probably a way to wire it up.

If this helped, follow @docat0209 — I write weekly about AI-assisted development and developer tools.

Top comments (0)