Geocode AI

Qué puedes hacer con él

Todavía no escribimos un resumen sencillo para este. Abajo están los datos que leímos del registro.

• Conexión: Computadora o nube
• Transporte: stdio, Streamable HTTP
• Categoría: Búsqueda y memoria de IA
• Debes completar: GEOCODE_API_KEY

Instalación

Elige la app de IA que usas y copia la configuración.

Necesitas

• Se ejecuta en la nubeNo hay nada que instalar; se conecta por internet
• npmNode.js instalado (para el comando npx)

¿Qué app usas?

https://geocodeai.dev/mcp

{
  "mcpServers": {
    "geocode": {
      "command": "npx",
      "args": [
        "-y",
        "@meterapp/geocode",
        "mcp"
      ],
      "env": {
        "GEOCODE_API_KEY": "your-value"
      }
    }
  }
}

claude mcp add --transport http geocode https://geocodeai.dev/mcp

claude mcp add geocode --env GEOCODE_API_KEY=your-value -- npx -y @meterapp/geocode mcp

{
  "mcpServers": {
    "geocode": {
      "url": "https://geocodeai.dev/mcp"
    }
  }
}

{
  "mcpServers": {
    "geocode": {
      "command": "npx",
      "args": [
        "-y",
        "@meterapp/geocode",
        "mcp"
      ],
      "env": {
        "GEOCODE_API_KEY": "your-value"
      }
    }
  }
}

{
  "servers": {
    "geocode": {
      "type": "http",
      "url": "https://geocodeai.dev/mcp"
    }
  }
}

{
  "servers": {
    "geocode": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@meterapp/geocode",
        "mcp"
      ],
      "env": {
        "GEOCODE_API_KEY": "your-value"
      }
    }
  }
}

https://geocodeai.dev/mcp

Tu elección se guarda en una cookie en este dispositivo; no necesitas cuenta.

Valores que debes completar

• GEOCODE_API_KEY secreto env
  Geocode AI API key (geo_...). Optional: public tools work without one.

Esta configuración se genera a partir de la ficha del creador en el registro. Si el README dice otra cosa, sigue el README.

Qué puede hacer

Nombres y descripciones de las herramientas tal como los informó el servidor el 6 nov 2026. Los escribió el creador, no nosotros; los mostramos como texto sin formato.

• search_boundaries

  Finds administrative boundaries (countries, states, counties, cities, districts) and postcode areas by name, in any language. Filter by country, kind or admin_level; bias toward a point with near. Free and public. Returns candidates with id, kind, admin_level, country, parents, b

• get_boundary

  Returns one boundary as a GeoJSON Feature: its polygon at a chosen detail plus properties (name, kind, admin_level, parents, bbox, area_km2, population, wikidata). Fetched from OpenStreetMap the first time anyone asks, then served from cache. Costs 1 unit; detail=low is also publ

• export_boundary

  Builds a boundary's polygon as a file (geojson, kml, wkt, svg or gml) at a detail level and returns a permanent public URL on our CDN; the REST route redirects straight to it. Use it for large polygons, GIS tools and bulk downloads. Costs 1 unit; each file is built once and then

• reverse_boundaries

  Every administrative boundary containing a point, country first down to the smallest district, plus postcode areas. Use it to tag an address, a store or a delivery with its country, state, county and city in one call. Costs 1 unit. Returns ids you can pass to get_boundary. Needs

• list_children

  The direct subdivisions of a boundary: a country's states, a state's counties, a city's districts. Without admin_level it picks the next level that exists. Free and public. Use it to build drill-down pickers or to cover a region with its parts.

• contains_points

  Tests up to 10,000 points ([lon, lat] pairs) against one boundary and returns a boolean per point plus the inside count. Use it for geofencing, service-area checks and filtering customer lists. Costs 1 unit per 1,000 points. Needs an API key or a connected account.

• union_boundaries

  Merges boundaries into one polygon: the union of include minus the union of exclude (e.g. three counties minus one city). Use it for sales territories, delivery zones and service areas. Up to 50 boundaries; costs 1 unit per boundary. Returns a GeoJSON Feature with area_km2. To de

• create_area

  Turns a plain-language description of an area ("Alameda and Contra Costa counties excluding San Jose, plus SFO") or wording from a contract or policy into one validated land-only polygon. An AI agent plans includes/excludes from real administrative boundaries; you get GeoJSON plu

• get_account

  The signed-in account and the organization the call acts in: email and profile, the organization (id, slug, name, personal or shared) and the caller's role in it (viewer, member, admin or owner), how the call is authenticated (api_key, oauth or session), the organization's plan i

• update_profile

  Sets the account's name, company, use case (what you are building) and language (the language for emails and the dashboard). Send only the fields to change; an empty string clears a text field. Free. Returns the updated profile. Needs an API key or a connected account.

• get_usage

  The organization's daily usage for the last N days (default 30), by op, with cache hit counts, across every member and key. Use it to explain a bill or spot a runaway client. Needs an API key or a connected account.

• list_api_keys

  The organization's API keys (prefix, name, who created it, last use; never the secret). Members see the keys they created; admins and owners see every key, including those of people who left. Needs an API key or a connected account.

• create_api_key

  Creates an API key for the organization and returns the secret once. Store it in an environment variable (GEOCODE_API_KEY); it cannot be shown again. The key acts in this organization only, with its creator's role (at most admin), and keeps working if the creator leaves until an

• revoke_api_key

  Revokes an API key by id. Requests with it fail with 401 immediately. Members revoke the keys they created; admins and owners revoke any key in the organization. Needs an API key or a connected account.

• get_email_preferences

  Which automated emails the account receives: the global subscription and one switch per kind (getting-started notes, first boundary, usage milestones, quota warnings, check-ins, monthly digest). Free. Sign-in codes are always sent. Needs an API key or a connected account.

• update_email_preferences

  Turns automated emails on or off: `subscribed: false` stops all of them (the same as the unsubscribe link), `subscribed: true` resubscribes, and `kinds` switches individual kinds. Kinds not named keep their setting. Free. Returns the preferences after the change. Needs an API key

• list_orgs

  The organizations you belong to, with your role in each and which one this call acts in (current). Personal is the one made for you at signup. An API key acts in its own organization only, so with a key this lists that one. Free. Needs an API key or a connected account.

• list_members

  The people in the organization: email, name, role (viewer, member, admin, owner), when they joined and their teams. Free. Use it to find who to share a file with. Inviting, removing and changing roles is done by a person on the dashboard. Needs an API key or a connected account.

• list_teams

  The organization's teams: slug, name, description and members with their team role (maintainer or member). Free. Pass a team's slug to share_file to share a library file with everyone in it. Needs an API key or a connected account.

• list_invites

  Invitations to the organization: email, role, teams, status (pending, accepted, expired, revoked) and when they expire. Admins and owners only. Free. Sending, resending and revoking invites is done on the dashboard. Needs an API key or a connected account.

• list_audit_log

  The organization's audit log, newest first: who (a person, an API key, an OAuth client or the system) changed membership, roles, teams, invites, API keys, billing or file sharing, and when. Admins and owners only. Free. Needs an API key or a connected account.

• save_file

  Exports a boundary (like export_boundary) and saves it in the organization's file library, so teammates find it on the dashboard and through list_files. visibility org (default) shares it with every member at their role; restricted keeps it to you, admins and whoever you share it

• list_files

  The boundary files in the organization's library that you can see, newest first: org-visible ones plus restricted ones shared with you or a team you are in. Each has your access (read, write or admin). Free. Needs an API key or a connected account.

• get_file

  One library file: its boundary, format, detail, visibility, your access, the permanent download url and, when you can manage it, who it is shared with. Free. Needs an API key or a connected account.

• update_file

  Renames a library file (write access) or sets its visibility (admin access on the file): org shares it with every member at their role, restricted keeps it to its creator, admins and explicit shares. Free. Needs an API key or a connected account.

• delete_file

  Removes a file from the organization's library and its shares (admin access on the file). The exported file itself stays in the public cache; export_boundary rebuilds the url any time. Free. Needs an API key or a connected account.

• share_file

  Shares a library file with a team (by slug or id) or a person in the organization (by email or user id) at read, write or admin access; sharing again changes the access. Needs admin access on the file (its creator, an org admin, or an admin share). Viewers are capped at read what

• unshare_file

  Removes one share of a library file by its grant id (from get_file). Needs admin access on the file. Org-visible files stay visible to every member; make it restricted with update_file to limit it to its shares. Free. Needs an API key or a connected account.

• get_subscription

  The organization's plan and subscription: plan, status, when the period renews or ends, whether it is set to cancel, the price, this month's use of every limit (units, described areas, API keys, rate) and what the next plan adds, with its checkout_url. Free. The same as get_accou

• create_checkout_link

  A link a human opens to buy a plan (pro or business) on a Stripe page branded Geocode AI. Free, and charges nothing: the person enters or confirms the card (never pass card details to a tool). With a key, the link is a Checkout page for that account (or, on a paid plan already, a

• get_billing_link

  A link for the account's owner to open Stripe's Customer Portal: download invoices, change the card or billing details, switch plans, or cancel (at the end of the period already paid for). Free. The link does not expire; it asks the person to sign in to Geocode AI, then opens the

• list_feedback

  The feedback board: feature requests and published issues with their status and upvotes, most upvoted first (with a key, also your own private issues, and whether you voted). Free and needs no key. Call it before request_feature or report_issue to find an existing item to upvote

• get_feedback

  One feedback item with its status, upvotes, comments (official team responses marked) and timeline of status changes. Free and needs no key for public items; a private issue is visible to its reporter and the team.

• list_my_feedback

  What you filed (including private issues), what you follow because you voted or commented, and your review, each with its current status. Free; needs a key. Use it to check on an issue you reported or a feature you asked for. Needs an API key or a connected account.

• request_feature

  Files a feature request on the public board and upvotes it for you. Use it when the human wishes the API did something it cannot (a boundary type, export format, op or option). It first looks for similar requests: if any match it files nothing and returns them in `similar`, so yo

• report_issue

  Reports a problem with Geocode AI: a failing or wrong API call, a wrong or missing boundary, a docs error. Call it after a call fails in a way that looks like our bug (5xx, a wrong polygon, a boundary that should exist), with the failing call's request_id (X-Request-Id header or

• upvote_feedback

  Adds your upvote to a feature request or issue (a "me too"); votes decide what gets built and fixed first, and you get an email when its status changes. Idempotent: one vote per account. A vote on a duplicate goes to the original. Free; needs a key. Returns the item with its new

• remove_feedback_vote

  Takes back your upvote on a feature request or issue, and stops its emails unless you filed or commented on it. Free; needs a key. Returns the item with its new vote count. Needs an API key or a connected account.

• comment_on_feedback

  Adds context to an existing feature request or issue: your use case, another failing request id, a workaround. Prefer it (with upvote_feedback) over filing a near-duplicate. You then get its status emails; its author gets a daily digest of comments. Free; needs a key; 50 comments

• list_reviews

  Published reviews of Geocode AI with the average rating and the distribution, and the team's response under each. Free and needs no key. Use it when the human asks what other users think.

• get_my_review

  Your review of the product, if you posted one, with its status (published, pending a check, or hidden with the reason) and the team's response. Free; needs a key. Needs an API key or a connected account.

• submit_review

  Posts the human's public review of Geocode AI (1–5 stars, what they like and dislike, what they use it for), or replaces their existing one; each account has one review and earlier versions are kept. Only call it with the human's own rating and words, never invented ones. Publish

• get_pricing

  Every plan with its monthly price, included units, limits (units, described areas, requests a minute, API keys), features and checkout_url, plus what each call costs in units and what works without a key. Free and needs no key. Call it before a large batch, when the human asks wh

Revisiones básicasi

Revisamos información que cualquiera puede ver; no hemos leído el código. Las revisiones que no aplican no se cuentan. · Revisado el 6 nov 2026

• ! Precaución

  El creador coincide con el repo

  El registro no indica ningún repo de código fuente, así que no podemos relacionar a quien lo publicó (geocodeai.dev) con el código

• … Aún sin revisar

  Sigue en mantenimiento

  Todavía no hemos leído este repo en GitHub

• … Aún sin revisar

  Tiene licencia

  Todavía no hemos leído este repo en GitHub

• ✓ Superada

  El endpoint responde

  Respondió en 1512 ms (HTTP 200)

• – No aplica

  Inicio de sesión con OAuth

  No hace falta iniciar sesión

• ✓ Superada

  Sin instrucciones ocultas en las descripciones de herramientas

  Leímos 43 descripciones de herramientas y no encontramos instrucciones ocultas para la IA

Comparado con otros en Búsqueda y memoria de IAi

• Más estrellas que el 0% de los otros 7241 servidores de esta categoría
• Publicado en el registro más recientemente que el 98% de los otros 7241 servidores de esta categoría
• Revisiones básicas iguales o mejores que el 40% de los otros 7241 servidores de esta categoría

Comparado con todos los servidores activos de esta categoría en el registro. Las estrellas solo cuentan cuando quien lo publica es dueño del repo.

Alternativas

Servidores de la misma categoría hechos por otros creadores, ordenados por estrellas.

Cómo leer una tarjeta:★ Estrellas de GitHubiTres pilares: reseñas · revisiones · usoiActualizado = fecha en que se publicó la última versión en el registroi

README del creador

No se encontró un README en el repo