Skip to content
noBSredir

Using agents

noBS redir has a built-in MCP server. Hook up Claude Code, Cursor, Windsurf, or whatever agent you use, and manage your links by talking to it. No SDKs to install, no wrapper code to write, no setup headaches. Connect, authenticate, done.

Connect in 30 seconds

  1. Go to Settings > API Keys and create a key
  2. Pick your client and follow the setup below
  3. Restart your editor. Done.

Run this in your terminal:

claude mcp add --transport http nobsredir \
--header "X-API-Key: nobs_your_api_key_here" \
https://nobsredir.com/mcp

Or add it to .mcp.json in your project root (or ~/.claude/.mcp.json for global):

{
  "mcpServers": {
    "nobsredir": {
      "type": "streamable-http",
      "url": "https://nobsredir.com/mcp",
      "headers": {
        "X-API-Key": "nobs_your_api_key_here"
      }
    }
  }
}

Go to Settings → Connectors → Add connector. Enter the URL and auth header:

URL:     https://nobsredir.com/mcp
Header:  X-API-Key: nobs_your_api_key_here

Claude Desktop uses the Connectors UI for remote MCP servers. Restart Claude Desktop after adding.

Open Settings → MCP → Add new MCP server. Set type to streamable-http and use:

{
  "mcpServers": {
    "nobsredir": {
      "type": "streamable-http",
      "url": "https://nobsredir.com/mcp",
      "headers": {
        "X-API-Key": "nobs_your_api_key_here"
      }
    }
  }
}

Or add it directly to .cursor/mcp.json in your project root. Restart Cursor to activate.

Open Settings → MCP and add a new server. Use the streamable HTTP transport:

{
  "mcpServers": {
    "nobsredir": {
      "type": "streamable-http",
      "url": "https://nobsredir.com/mcp",
      "headers": {
        "X-API-Key": "nobs_your_api_key_here"
      }
    }
  }
}

Or add it to ~/.codeium/windsurf/mcp_config.json. Restart Windsurf.

Add this to your VS Code settings.json (or .vscode/mcp.json in your project):

{
  "servers": {
    "nobsredir": {
      "type": "http",
      "url": "https://nobsredir.com/mcp",
      "headers": {
        "X-API-Key": "nobs_your_api_key_here"
      }
    }
  }
}

Make sure GitHub Copilot agent mode is enabled. The MCP server will appear in the Copilot chat tools.

Go to Settings → Tools → AI Assistant → MCP → Add. Select Streamable HTTP and paste:

{
  "mcpServers": {
    "nobsredir": {
      "url": "https://nobsredir.com/mcp",
      "headers": {
        "X-API-Key": "nobs_your_api_key_here"
      }
    }
  }
}

Works in IntelliJ, WebStorm, PyCharm, GoLand, and all JetBrains IDEs with AI Assistant.

Any MCP client that supports the streamable-http transport will work. Point it to:

URL:        https://nobsredir.com/mcp
Transport:  streamable-http
Header:     X-API-Key: nobs_your_api_key_here

Check your client’s docs for where to configure MCP servers. The connection is stateless - each request is authenticated via your API key.

Your agent now has access to all your workspace’s links, analytics, and domains. It’s scoped to whichever workspace the API key belongs to.

What you can ask it to do

These are real prompts that work. Copy them, tweak them, whatever.

Shorten https://example.com/spring-collection on go.mystore.com and tag it “spring-2025”

Create links for these three pages and tag them all “onboarding”:

Shorten https://example.com/pricing with UTM params: source=newsletter, medium=email, campaign=march-promo

The agent picks the right tool, fills in the params, and gives you the short URL back.

Check analytics

How are my links doing this week?

Which links got the most clicks in the last 7 days?

Show me the stats for go.mystore.com/spring - where’s the traffic coming from?

Compare clicks this week vs last week. Any big changes?

The agent pulls from your workspace analytics. It’ll break things down by country, referrer, device, browser - whatever you ask.

Run campaigns

Set up a “product-launch” campaign for these URLs: https://example.com/landing, https://example.com/demo, https://example.com/pricing

Multi-step workflow, single prompt. The agent reads your workspace config, creates a tag, builds links with consistent UTM params, and hands you a summary table.

A/B testing

Set up an A/B test between https://example.com/page-v1 and https://example.com/page-v2

The agent creates a split test with proper weights and tells you how to read the results later.

Delete the link go.mystore.com/old-promo

Change the target of go.mystore.com/demo to https://example.com/new-demo

Add the tag “archived” to all links tagged “q4-2024”

Tips

  • Be specific about domains. If you have multiple custom domains, tell the agent which one to use.
  • Tag everything. Tags make it easy to ask “how’s the spring campaign doing?” later.
  • Ask follow-up questions. “What about mobile vs desktop?” or “Break that down by country” works after any stats query.
  • The agent reads your workspace config automatically. It knows your domains, tags, and plan limits before it acts.

What it can’t do

A few things still need the dashboard:

  • Adding or verifying custom domains (needs DNS changes)
  • Managing workspace members and roles
  • Creating API keys
  • Billing and plan changes

For the full technical reference (every tool, resource, and prompt), see the MCP developer docs.