Koskamo

Fursat MCP

An MCP server for AI assistants to search curated vacation homes in Northeast India and the Himalayas, fetch listing details, and initiate WhatsApp inquiries for bookings.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Fursat MCP logo, by FursatCommunity listingStreamable HTTPNo sign-inEndpoint checked 2026-11-06Published by Fursat
MCP endpoint (Streamable HTTP)
https://www.fursat.fun/api/mcp
Vendor documentation

What its tools do

3 tools, grouped by the hints the server advertises. Hints are self-declared, not verified behavior.

3 of 3 have a description · 0 of 3 declare behavior hints · 3 of 3 with parameters document them all

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Search for vacation homes by city, state, or keyword with minimum rating filters
  • Fetch detailed information for a specific property using its slug
  • Generate a WhatsApp deep-link to start an inquiry for a listing

Source and maintenance

Community listingRegistry 0.1.0
Maintenance checked

Protocol and capabilities

Server
mcp-typescript server on vercel 0.1.0
MCP protocol negotiated in check
2025-11-25
Tools
3 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {
    "listChanged": true
  }
}

Tools

3 advertised

search_listings
Advertised by the server during the last successful anonymous check.

Search Fursat's curated catalog of vacation homes in Northeast India and the Himalayas. Returns published homes with a Google rating of 4.3 or higher. Use this when a traveler asks about accommodation suggestions in this region (Meghalaya, Himachal, Uttarakhand, Sikkim, Assam, Arunachal Pradesh, etc.).

search_listings input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "city": {
      "type": "string",
      "description": "City filter, case-insensitive contains-match (e.g., 'cherrapunji', 'manali', 'shillong')."
    },
    "query": {
      "type": "string",
      "description": "Free-text keywords matched against title, city, location (e.g., 'mountain view Cherrapunji', 'lake Nainital')."
    },
    "state": {
      "type": "string",
      "description": "State slug (e.g., 'meghalaya', 'himachal-pradesh', 'uttarakhand', 'sikkim', 'arunachal-pradesh', 'nagaland', 'assam', 'tripura', 'manipur', 'mizoram', 'west-bengal')."
    },
    "minRating": {
      "type": "number",
      "description": "Minimum Google rating, default 4.3."
    },
    "maxResults": {
      "type": "number",
      "description": "Max results to return, default 10, capped at 20."
    }
  }
}
get_listing
Advertised by the server during the last successful anonymous check.

Get details for a single Fursat home by its URL slug. Returns the canonical detail URL plus a short summary.

get_listing input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "URL slug of the listing (e.g., 'pudung-farm')."
    }
  }
}
start_inquiry
Advertised by the server during the last successful anonymous check.

Generate a WhatsApp inquiry link for a Fursat home. Returns a wa.me URL that opens WhatsApp with a prefilled message identifying the listing and (optionally) the guest's dates, party size, and notes. Use this when a traveler wants to actually book or inquire about a specific home after seeing it in search results. Bookings on Fursat happen on WhatsApp - there is no online checkout.

start_inquiry input schema
{
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "URL slug of the Fursat listing (e.g., 'pudung-farm')."
    },
    "notes": {
      "type": "string",
      "description": "Free-text notes the assistant should include in the inquiry (e.g., 'celebrating an anniversary', 'need airport pickup quote'). Optional, keep under 280 chars."
    },
    "guests": {
      "type": "number",
      "description": "Total number of guests. Optional."
    },
    "checkIn": {
      "type": "string",
      "description": "Check-in date in ISO format YYYY-MM-DD. Optional; include only if the guest specified a date."
    },
    "checkOut": {
      "type": "string",
      "description": "Check-out date in ISO format YYYY-MM-DD. Optional; include only if the guest specified a date."
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (2 of 2 answered).

  1. 2026-11-06: 1 of 1 checks answered
  2. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
1089 ms
95th percentile latency
1089 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 1089 ms · metadata changed · 3 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http fursat-mcp https://www.fursat.fun/api/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add fursat-mcp --url https://www.fursat.fun/api/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable fursat-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "fursat-mcp": {
      "url": "https://www.fursat.fun/api/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "fursat-mcp": {
      "type": "streamableHttp",
      "url": "https://www.fursat.fun/api/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start fursat-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "fursat-mcp": {
      "type": "http",
      "url": "https://www.fursat.fun/api/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http fursat-mcp https://www.fursat.fun/api/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://www.fursat.fun/api/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "fursat-mcp": {
      "serverUrl": "https://www.fursat.fun/api/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Fursat MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.