Urbit MCP — Documentation

Urbit MCP is a Model Context Protocol server that brings Urbit's geographic intelligence into AI assistants. It answers questions about a specific address or coordinate in São Paulo: zoning and building potential, fiscal cadastre, property transfers, new development launches and absorption, census demographics, mobility, amenities, and environmental or legal constraints on the land.

1. What Urbit MCP does

The server exposes Urbit's data services as tools that an AI assistant can call while answering you. You describe a site in plain language; the assistant resolves it to a coordinate, calls the relevant tools, and reasons over what comes back. The connector supplies data — the analysis is produced by the assistant from that data.

Every tool is read-only. The connector does not create, modify or delete anything, in Urbit's systems or anywhere else. It writes nothing back to your account beyond the usage record needed for billing.

2. Who it is for

Developers, investors, consultancies, architecture and urban planning practices, and financial institutions that need site-level urban and market diagnostics. Typical work: land acquisition screening, feasibility studies, due diligence, competitive supply analysis and appraisal support.

Urbit does not provide legal, engineering, appraisal or investment advice. Output is informational and should be verified against the official record before it is relied on for a decision.

3. Requirements

• An active Urbit account with API/MCP access. Request one at urbit.com.br or write to contato@urbit.com.br.
• Claude — web, desktop or mobile — on a plan that supports connectors, or any other MCP-compatible client.
• A credit balance. Every new account receives free welcome credits so the server can be evaluated end to end before any purchase.

4. Connecting to Claude

1. In Claude, open Settings → Connectors.
2. Find Urbit MCP and click Connect.
3. You are redirected to Urbit's sign-in page. Authorize access.
4. The tools become available in your conversations. No further configuration is needed.

To disconnect, go to Settings → Connectors → Urbit MCP → Disconnect. This revokes the access token immediately; no further requests can be made until you reconnect.

5. Tool catalogue

Municipal services (marked M) require the cidade parameter and currently cover the city of São Paulo. National services (N) cover Brazil. Prices are per request, in Brazilian reais; the authoritative list is always the one returned by get-precos-servicos-api-mcp.

Utilities

Zoning and urban legislation

Fiscal cadastre and transactions

Risks, constraints and physical setting

Infrastructure, mobility and services

Demographics and socioeconomics (2022 Census)

Real estate market

6. Common parameters

A few services take additional parameters — finalidade (sale or rental) and optional filters on get-listing; unit characteristics on get-avm; a free-text endereco on get-geocoder. Your assistant reads these from each tool's schema; you do not need to supply them by hand.

7. Response format

Every tool returns a JSON object with a value array, ordered by distance where that applies:

{ "value": [ { "nome": "TRIANON-MASP", "modal": "METRÔ",
              "linha": "LINHA 2 - VERDE", "situacao": "OPERANDO",
              "distancia": 405 } ] }

When nothing is found within the radius, the response is an empty array with a message. This is a valid answer, not an error:

{ "value": [], "message": "nada consta" }

Geometries are suppressed in MCP responses — the geom field is returned as null — except for urban operations, where the perimeter polygon is included. Distances are in metres, areas in square metres, and monetary values in Brazilian reais.

8. Credits and pricing

Usage is metered in credits. Each request to a data service deducts its unit cost from your balance at the moment it is processed; requests that fail because of an error on Urbit's side are not charged. New accounts receive free welcome credits.

Administrative calls are free — checking the price list, your balance or your usage costs nothing. The price list itself is available at any time through get-precos-servicos-api-mcp, and it is the authoritative reference for what each request costs. Prices may change; credits already purchased keep their face value.

When your balance reaches zero, data services are suspended until it is topped up. Administrative calls continue to work. Full commercial terms are in the Terms of Service.

9. Example prompts

Start from an address. The assistant resolves the coordinate and chains the tools it needs.

10. Coverage and data sources

Municipal services — zoning, fiscal cadastre, ITBI, heritage, urban operations, contaminated land, road improvements, expropriations, parks and street markets — currently cover the city of São Paulo. National services — demographics, vulnerability, mobility, amenities, listings, launches and valuation — cover Brazil, with density varying by region.

Content is compiled from three kinds of source: open government data (the City of São Paulo, IBGE's 2022 Census, CONDEPHAAT and CONPRESP, among others), licensed third-party data (including property portals), and Urbit's own processing, indexes and models. Public sources may contain errors, omissions or lags that Urbit does not control, and model outputs — valuations, indexes, statistical estimates — are estimates rather than appraisals or official records.

11. Data and privacy

The connector sends Urbit only the parameters of the query: coordinates, radius and filters. It does not read your conversation history, your files, your memory or other connectors, and it does not collect conversation data.

Two services return publicly available personal data of third parties: the advertiser name and published telephone number in property listings (get-listing), and the taxpayer and registry fields published in municipal cadastral records (get-lote-fiscal). These may be used for professional real estate analysis and due diligence, and must not be used for unsolicited marketing, list building, or profiling of identifiable individuals. Your obligations as an independent controller under the LGPD are set out in Section 7.5 of the Terms of Service.

The Service returns no confidential taxpayer information — no tax debts, payment status or financial details of any taxpayer. Usage records are kept for billing and audit. See the Privacy Policy for categories, legal bases, retention and data subject rights.

12. Errors and troubleshooting

13. Limits and fair use

• get-listing and get-transacoes-itbi return at most 50 records per call. In dense areas, narrow the radius or filter by property type so the sample is not silently truncated.
• get-launches-typologies-mcp returns one record per unit typology and can produce a large payload at a wide radius — enough to exceed an assistant's context window. A radius of 500 m or a tighter filter keeps it readable.
• get-lote-fiscal returns exactly one lot: the one containing the coordinate.
• Default search radii differ by service, from roughly 100 m to 2,000 m. Passing distance explicitly makes results reproducible.
• Rate limits and fair-use thresholds apply to protect the Service, as described in Section 6 of the Terms of Service.

14. Support

Write to contato@urbit.com.br for questions about the connector, coverage, credits or billing. We reply within one business day. Privacy and data subject requests go to privacidade@urbit.com.br.

When reporting a problem, include the coordinate or address, the tool name and roughly when the call was made — that is enough for us to find the request in our logs.

See also: Terms of Service · Privacy Policy · Customer Support

15. Changelog