mcpField
1
1acre Land Intelligence

1acre Land Intelligence

Remote
1acre.inBusiness & Marketing0Updated 8w ago

About 1acre Land Intelligence

1acre Land Intelligence provides MCP access to land lookups and intelligence reports in India for land buyers, sellers, and agents using a 1acre account. It identifies parcels by survey number or coordinates and offers boundary data, map-layer details, and verified listing searches.

Key features

  1. 01Generate parcel reports from survey numbers or coordinates
  2. 02Browse location hierarchies and survey numbers
  3. 03Retrieve GeoJSON boundaries for existing reports
  4. 04Look up map-layer attributes and regional listings
  5. 05Check token balance and submit a sell intent

Use cases

  1. 01Identify a cadastral parcel from coordinates
  2. 02Find survey numbers available in a village
  3. 03Review parcel boundaries and map-layer attributes
  4. 04Search verified land listings by location

MCP support

The hosted MCP server connects to 1acre accounts using OAuth 2.1 with PKCE and exposes land lookup, reporting, and listing tools. Some tools use 1acre credits; balance and tool costs can be checked through the service.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://mcp.1acre.in/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

1acre MCP

The official MCP (Model Context Protocol) server for 1acre.in — India's verified land marketplace. Connect Claude Code, Cursor, Claude Desktop, or any MCP-compatible client to look up survey numbers, browse cadastral data, and generate land-intelligence reports on behalf of your 1acre account.

This repository contains the client-side configuration and documentation — how to connect. The server itself runs at https://mcp.1acre.in.


What you can do

Once connected, any MCP client can call these tools as the signed-in 1acre user:

ToolCostDescription
get_token_balanceFreeCheck your token balance, tier allowance, and what each paid tool costs
browse_locationsFreeWalk the location hierarchy (state → district → mandal → village)
list_survey_numbersFreeList survey numbers that exist in a given village
list_available_layersFreeDiscover which map layers (Master Plan, air-funnels, expressways, metro, etc.) cover a lat/lng — metadata only
get_survey_number_reportFreeRe-open a previously generated report by ID — no tokens spent
get_report_coordinatesFreeGet GeoJSON boundary coordinates for a previously generated report
create_sell_listing_intentFreeCapture a "sell my land" intake — returns a pre-filled WhatsApp link to the 1acre listings team
get_layer_info5 tokens per layerFetch feature attributes at a lat/lng inside a paid map layer (zone, permissible height, corridor distance). Misses are free.
list_lands_in_region1 token per pageUp to 10 verified 1acre land listings within a radius of a lat/lng (per page). Empty pages are free.
create_survey_number_report10 tokensGenerate a full land-intelligence report for a specific survey number
identify_parcel_at_point10 tokensIdentify the cadastral parcel at a lat/lng coordinate and generate its report

Paid tools spend from your "1a" token balance. Free tools cost nothing — once a report exists, you can re-open it and pull its boundary coordinates as often as you like without spending another token.

Call get_token_balance first (it's free) to see your live balance and the current per-tool price. A run that would overdraw fails with insufficient_tokens and is recoverable — top up from the My Tokens page on 1acre and retry.

"Tokens" here means 1acre land-intelligence credits — unrelated to the OAuth access tokens your MCP client manages for sign-in.


Quick start — Claude Code

claude mcp add --scope user --transport http 1acre https://mcp.1acre.in/mcp \
  --callback-port 8118 \
  --client-id eKg8BebDnd09zxwy

Then in Claude Code:

  1. Type /mcp — you'll see 1acre with Needs authentication
  2. Click Sign In
  3. Browser opens 1acre's sign-in page (phone number)
  4. Enter your phone number → receive OTP via SMS → enter code
  5. Consent screen → Allow
  6. 1acre flips to ✓ Connected

Now ask Claude anything land-related: "How many 1acre tokens do I have left?", "What districts does Telangana have?", etc.


Quick start — Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or the equivalent path on your OS:

{
  "mcpServers": {
    "1acre": {
      "url": "https://mcp.1acre.in/mcp",
      "transport": "http",
      "oauth": {
        "clientId": "eKg8BebDnd09zxwy",
        "callbackPort": 8118
      }
    }
  }
}

Restart Claude Desktop. Sign in via the MCP servers dialog.


Quick start — Cursor

Cursor's MCP config lives at ~/.cursor/mcp.json. Add:

{
  "mcpServers": {
    "1acre": {
      "url": "https://mcp.1acre.in/mcp"
    }
  }
}

Cursor prompts you to authenticate on first tool call.

More detailed examples in examples/.


Authentication

1acre MCP uses OAuth 2.1 with PKCE. Sign-in is phone-number-based via one-time SMS verification (secure, DLT-compliant for Indian phone numbers).

  • Your phone number becomes your identity.
  • You must have a 1acre.in account first — sign up at 1acre.in with the phone number you plan to use. MCP resolves your Clerk identity to that Account by matching the phone.
  • Sessions are managed by the auth server; your MCP client refreshes tokens automatically.

Registering an OAuth client

Most clients register automatically. 1acre's OAuth provider supports RFC 7591 Dynamic Client Registration at https://clerk.1acre.in/oauth/register — MCP clients that speak DCR (Claude Code, Smithery, and others) discover this from .well-known/oauth-authorization-server and register themselves on first connect. You don't need to do anything, and the --client-id flag in the Quick Start above is only needed if your client can't do DCR.

Manual registration (only if your client doesn't support DCR)

Contact [email protected] with:

  1. Your MCP client name (e.g. "Internal agent X")
  2. The exact callback URL your client will use

You'll receive a client_id (public — safe to commit; PKCE-only, no client secret).


Available at

  • MCP endpoint: https://mcp.1acre.in/mcp
  • Discovery: https://mcp.1acre.in/.well-known/oauth-protected-resource
  • Health: https://mcp.1acre.in/healthz

Costs & limits

  • Free tools (balance check, discovery, hierarchy browse, list survey numbers, sell-listing intent, re-read reports, get coordinates): unlimited
  • Paid tools:
    • get_layer_info — 5 tokens per layer that returns a feature (misses are free)
    • list_lands_in_region — 1 token per non-empty page (10 listings per page; empty pages are free)
    • create_survey_number_report — 10 tokens per report
    • identify_parcel_at_point — 10 tokens per run
  • Rate limits: 60 requests/minute per OAuth access token

Token allowance by account tier:

TierAllowance
Non-premium (regular, free trial, expired premium)100 tokens
Premium — quarterly plan500 tokens
Premium — yearly plan2,000 tokens

Tokens expire 365 days after they are credited — this is a balance, not a lifetime allowance. Purchased top-up packs stack on top of your tier allowance, so a balance above the figures above is normal. get_token_balance is always the source of truth for what's actually spendable.

For higher limits, contact [email protected].


Support


License

MIT — see LICENSE.

Server code is not open source; this repo covers client-side configuration and documentation only.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.