Skip to content
integration

Botoi MCP server: 49 developer tools inside your AI coding assistant

| 7 min read
AI assistant interface with tool integrations
Photo by Possessed Photography on Unsplash

You're debugging a DNS issue in Claude Code. You need A records for a domain. The options: open a browser, find an online tool, copy the result back. Or open a terminal, remember the dig syntax, parse the output yourself.

Both break your flow. The information you need is two hops away from where you're working.

Botoi now runs an MCP server at api.botoi.com/mcp with 49 developer tools. Connect it to Claude Desktop, Claude Code, Cursor, or VS Code, and your AI assistant can call tools like DNS lookup, JWT decode, Base64 encode, and PII detection directly. No browser tabs, no terminal switching.

Setup takes 30 seconds

The MCP server uses Streamable HTTP transport. It's stateless; there's no session to initialize or SSE connection to keep alive. Add the URL to your client config and you're done.

Claude Desktop

Open claude_desktop_config.json and add:

{
  "mcpServers": {
    "botoi": {
      "type": "streamable-http",
      "url": "https://api.botoi.com/mcp"
    }
  }
}

Claude Code

Run this in your terminal:

claude mcp add botoi --transport streamable-http https://api.botoi.com/mcp

Cursor

Open Cursor Settings, go to MCP, and add:

{
  "mcpServers": {
    "botoi": {
      "url": "https://api.botoi.com/mcp",
      "type": "streamable-http"
    }
  }
}

VS Code (GitHub Copilot)

Add this to your settings.json:

{
  "mcp": {
    "servers": {
      "botoi": {
        "type": "streamable-http",
        "url": "https://api.botoi.com/mcp"
      }
    }
  }
}

All four clients discover the 49 tools on first connection. No npm install, no Docker container, no local process to manage.

Code editor with AI assistant integration
MCP tools appear directly in your AI assistant's tool palette Photo by Fotis Fotopoulos on Unsplash

What you get: 49 tools across 5 categories

The MCP server exposes a curated subset of Botoi's 150+ API endpoints. These are the tools developers reach for most often during coding sessions.

Lookup (12 tools)

Network and domain intelligence without leaving your editor.

  • IP Lookup - geolocation, ISP, and AS number for any IP
  • DNS Lookup - A, AAAA, MX, TXT, CNAME, NS records
  • WHOIS - domain registration, registrar, expiry date
  • SSL Check - certificate details and security headers
  • Email Validate - syntax, MX records, disposable check
  • HTTP Headers - response headers for any URL
  • URL Metadata - title, OG tags, favicon extraction
  • Domain Availability - check if a domain is registered
  • Tech Detect - identify frameworks, CMS, and analytics on a site
  • VPN Detect - check if an IP is a VPN, proxy, or Tor node
  • Phone Lookup - parse and validate phone numbers
  • Company Lookup - company info from a domain name

Text and data (10 tools)

Encoding, conversion, and format transformations.

  • Base64 Encode/Decode - UTF-8 to Base64 and back
  • JSON Format - pretty-print with configurable indentation
  • JSON Validate - syntax check with error positions
  • Markdown to HTML - GFM-compatible conversion
  • HTML to Markdown - reverse conversion
  • CSV to JSON - parse CSV into JSON arrays
  • YAML to JSON / JSON to YAML - bidirectional conversion
  • XML to JSON - XML document conversion

Developer utilities (12 tools)

The tools you'd otherwise open a separate tab for.

  • Hash - MD5, SHA-1, SHA-256, SHA-512
  • UUID Generate - v4 and v7
  • JWT Sign/Verify - create and decode tokens
  • Cron Describe - plain-English cron explanations
  • Password Generate - configurable length and complexity
  • URL Encode/Decode - percent-encoding
  • Regex Test - test patterns against strings
  • Text Diff - unified diff output
  • Semver Parse - major, minor, patch extraction
  • Timestamp Convert - Unix to ISO 8601 and back

Security (5 tools)

  • Encrypt/Decrypt - AES-256-GCM with a passphrase
  • TOTP Generate - time-based one-time passwords
  • Credit Card Validate - Luhn check and network detection
  • PII Detect - find emails, phones, and SSNs in text

Transform (5 tools)

  • Minify JS/CSS - reduce file sizes
  • SQL Format - beautify SQL queries
  • Code Format - format JS, TS, Python, Go, Rust, and more
  • JSON to TypeScript - generate interfaces from JSON

Real example: DNS lookup from Claude Code

You're setting up Cloudflare DNS for a client's domain and want to verify the A records propagated. Ask your assistant:

> "Look up the DNS records for github.com"

Tool call: lookup_dns
Input: { "domain": "github.com", "type": "A" }

Result:
{
  "domain": "github.com",
  "type": "A",
  "records": [
    { "value": "140.82.121.4", "ttl": 60 }
  ],
  "resolver": "1.1.1.1",
  "query_time_ms": 12
}

The assistant calls lookup_dns, passes the domain and record type, and returns structured JSON. No terminal, no browser, no copy-paste. The result is in your conversation and you can act on it immediately.

More examples in practice

Decode a JWT during debugging

You're inspecting an auth token from a failing request. Paste it into your conversation:

> "Decode this JWT: eyJhbGciOiJIUzI1NiJ9.eyJ1c2VyIjoiYWxpY2UifQ.Ck2..."

Tool call: dev_jwt_verify
Input: { "token": "eyJhbGciOiJIUzI1NiJ9..." }

Result:
{
  "header": { "alg": "HS256" },
  "payload": { "user": "alice" },
  "expired": false
}

The header, payload, and expiry status come back in structured JSON. You can see the algorithm, claims, and whether the token is expired without visiting jwt.io.

Scan text for PII before logging

You're building a logging pipeline and want to verify no personal data leaks into your logs:

> "Check this text for personal data: Call me at 555-0123 or email john@example.com"

Tool call: security_pii_detect
Input: { "text": "Call me at 555-0123 or email john@example.com" }

Result:
{
  "found": true,
  "entities": [
    { "type": "phone", "value": "555-0123", "start": 14, "end": 22 },
    { "type": "email", "value": "john@example.com", "start": 32, "end": 48 }
  ],
  "count": 2
}

The response identifies each entity with its type, value, and position in the string. You can use this to mask sensitive data before it reaches your log store.

Anonymous access and authenticated access

The MCP server works without an API key. Anonymous access gives you 5 requests per minute and 100 requests per day, rate-limited by IP. That's enough for casual use during a coding session.

For heavier use, add an API key to your config:

{
  "mcpServers": {
    "botoi": {
      "type": "streamable-http",
      "url": "https://api.botoi.com/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

Get an API key at botoi.com/api. The free tier requires no payment method.

Technical details

Property Value
Endpoint POST https://api.botoi.com/mcp
Protocol MCP Streamable HTTP (JSON-RPC 2.0)
State Stateless; no session init required
Auth Authorization: Bearer KEY or X-API-Key: KEY header
Infrastructure Cloudflare Workers (edge, global)
Tool count 49 curated tools
Anonymous rate limit 5 req/min + 100 req/day

The server runs on Cloudflare Workers, which means requests route to the nearest edge node. Response times are typically under 50ms for computation-only tools like hashing, Base64 encoding, and JSON formatting. Lookup tools that call external services (DNS, WHOIS, SSL) add the upstream latency.

MCP vs. the REST API

The MCP server wraps the same endpoints as the Botoi REST API. If you're building an application, the REST API is the right choice. If you're working inside an AI assistant, MCP is faster because the assistant discovers tools on connection and calls them by name without you constructing HTTP requests.

Both share the same rate limits and API keys. An API key that works with the REST API works with the MCP server.

Get started

  • Add the config. Copy the snippet for your client from the setup section above.
  • Restart your client. Claude Desktop, Cursor, and VS Code pick up MCP server changes on restart.
  • Ask for something. Try "look up the DNS records for example.com" or "generate a UUID" and watch the tool call happen.

The full tool list and parameter schemas are available at api.botoi.com/v1/mcp/tools.json. The API docs cover every endpoint in detail.

Frequently asked questions

Do I need an API key to use the Botoi MCP server?
No. Anonymous access works at 5 requests per minute and 100 requests per day, rate-limited by IP. Add an API key to raise limits on any paid plan.
Which MCP transport does the Botoi server use?
Streamable HTTP (JSON-RPC 2.0) at https://api.botoi.com/mcp. The server is stateless, so there is no session initialization or SSE connection to maintain.
Can I use the MCP server with Cursor and VS Code?
Yes. Both Cursor and VS Code support MCP servers via their settings files. Add the server URL as a streamable-http type and the tools appear in your assistant.
How many tools are available through the MCP server?
49 curated tools across 5 categories: Lookup (12), Text and Data (10), Developer Utilities (12), Security (5), and Transform (5).
Is the MCP server different from the REST API?
The MCP server wraps the same REST API endpoints in the MCP protocol. AI assistants call tools by name and receive structured results. You can still call the REST API directly for non-MCP use cases.

Try this API

DNS Lookup API — interactive playground and code examples

More integration posts

Start building with botoi

150+ API endpoints for lookup, text processing, image generation, and developer utilities. Free tier, no credit card.