Model Context Protocol

Connect an AI assistant to MapWise

Ask Claude or another assistant about any Florida parcel, in plain language. The MapWise MCP server gives your assistant the same parcel data as the API. That covers owners, sales, valuation, land use and flood zones in all 67 counties. It works with a MapWise sign-in or an API key, and bills your account at API rates.

Server URL https://www.mapwise.com/mcp

Sign in with your MapWise account

Assistants that support MCP sign-in connect with your MapWise account. You don’t need an API key. MCP sign-in uses OAuth, with dynamic client registration (DCR) or a client ID metadata document (CIMD). Your assistant’s connector settings show whether it supports sign-in.

Add MapWise as a remote MCP server, with the server URL.
When your assistant asks, sign in with your MapWise account.
Confirm the account, then allow access.

You can connect if you can create an API key. Get an API key covers who can. Every call bills your account at API rates, the same as a call with a key.

Any assistant with sign-in

Server URL  https://www.mapwise.com/mcp
Sign-in     Your MapWise account

Manage it in My Account. The app then appears under Connected apps, where you can disconnect it. See Manage connected apps.

For example, in Claude (web, desktop and mobile)

Add MapWise as a custom connector. You need a Claude plan that allows custom connectors. Claude’s guide to custom connectors lists the plans and shows where to find the setting.

Server URL: https://www.mapwise.com/mcp
Sign-in: Leave it on

In Claude, open Customize > Connectors.
Add a custom connector.
Enter the name MapWise and the server URL.
Leave sign-in on. Don’t add a header or a key.
When Claude asks, sign in with your MapWise account.
MapWise asks “Connect an AI app to your MapWise account?” Confirm it.
Approve the consent screen that follows. WorkOS runs it for MapWise.
In a new chat, turn on MapWise.
Run the free check.

If Claude’s menus have changed, follow its guide. If MapWise stops working in Claude, see MapWise stopped working.

Connector settings

Name        MapWise
Server URL  https://www.mapwise.com/mcp
Sign-in     On (your MapWise account)

For example, in Claude Code

Add the server with no header or key, then sign in.

Add MapWise with the command shown, or add it to your project’s .mcp.json.
In Claude Code, run /mcp and choose mapwise.
Sign in with your MapWise account when your browser opens, then allow access.
Run the free check.

When Claude Code runs headless or from a script, use an API key instead.

For more options, such as scopes and approval prompts, see Claude Code’s MCP documentation.

Terminal

claude mcp add --transport http mapwise \
  https://www.mapwise.com/mcp

.mcp.json

{
  "mcpServers": {
    "mapwise": {
      "type": "http",
      "url": "https://www.mapwise.com/mcp"
    }
  }
}

Use an API key

Use a key with assistants that don’t support MCP sign-in, and with scripts and headless agents. The assistant sends the key with every call.

Get an API key

Create a secret key in My Account > MapWise API. Give it its own name, such as Claude Code laptop, so you can revoke it later without breaking anything else. You can hold up to 10 secret keys.

Keys start with mw_sk_ and are shown once. Paste the key straight into your assistant.
Every call bills your account at the same rates as the API.
Keep the key secret. Anyone who has it can run billed searches.

One key per assistant. If a key leaks, revoke that one key in My Account. Nothing else stops working.

Or use an API key in Claude Code

Verified

Use a key when Claude Code runs headless or from a script. Add the server to your project’s .mcp.json, and read the key from an environment variable as shown. That keeps the key out of any file you commit and out of your shell history.

Before you start Claude Code, set MAPWISE_API_KEY in your shell.

If you are only trying it on your own machine, the one-line command works too.

Verified with Claude Code on 7 October 2026.

.mcp.json

{
  "mcpServers": {
    "mapwise": {
      "type": "http",
      "url": "https://www.mapwise.com/mcp",
      "headers": {
        "Authorization": "Bearer ${MAPWISE_API_KEY}"
      }
    }
  }
}

Terminal

claude mcp add --transport http mapwise \
  https://www.mapwise.com/mcp \
  --header "Authorization: Bearer mw_sk_…"

Any other MCP client

Most assistants can connect to a remote MCP server. Add MapWise the way your client’s instructions describe. Use https://www.mapwise.com/mcp as the server URL. If your client supports MCP sign-in, sign in with your MapWise account. Otherwise send your key in the Authorization header.

For questions or trouble connecting, email support@mapwise.com.

Connect only servers you trust alongside MapWise. Text from another connector or a web page can try to steer your assistant into searches you did not ask for.

Typical config

{
  "mapwise": {
    "url": "https://www.mapwise.com/mcp",
    "headers": {
      "Authorization": "Bearer mw_sk_…"
    }
  }
}

Verify with a free call

Start with get_help. It costs nothing and proves your assistant can reach MapWise. Then try one parcel, which bills one record.

A tool list alone does not prove the key works. An assistant can connect and list the MapWise tools with a wrong key. A bad key shows up on the first real call.

Approve tool calls. Turn on your assistant’s tool-approval setting so you see each search and its arguments before it runs. Searches bill per record.

Free

Use MapWise get_help to list what
parcel searches you can do.

One record · $0.06

Using MapWise, find the parcel at
2410 NW 43rd St, Gainesville in
Alachua County. One result only.

Tools and pricing

Your assistant chooses the tool. Searches bill per record returned and reports bill per report, at the rates on the API pricing page. get_help and get_usage_history are free. MapWise rejects an unknown or misspelled argument before it bills anything.

Your spend cap applies. Every call counts toward the monthly cap you set in My Account, the same as direct API use. Ask your assistant to run get_usage_history to see what a key has spent.

Tool	Use it to	Price
`get_parcel`	Summarize one parcel by PIN or point	$0.06 / record
`get_parcel_detail`	Full detail, sale history, flood zones, boundary	$0.06 / record
`search_parcels`	Look up by address, PIN, city or ZIP	$0.06 / record
`find_parcels_in_area`	Screen an area by acreage, land use, value	$0.06 / record
`find_owner_holdings`	Everything an owner holds statewide	$0.06 / record
`list_aggregation_parcels`	Expand an owner or tract row into parcels	$0.06 / record
`find_recent_sales`	Recent sales and comparables near a point	$0.06 / record
`generate_parcel_report`	A PDF property or flood report, delivered as a link	$1.00 / report
`get_usage_history`	Check what your key has spent	Free
`get_help`	Tool arguments and land-use codes	Free

Parcel boundaries are capped at 100 KB per response. Rows past the cap keep their center point. The server tells your assistant how to fetch the full boundary for one parcel.

To keep searches cheap, name the county when you know it. Ask how many parcels match before you ask for the list.

Rotate or revoke a key

Create a new key in My Account > MapWise API.
Replace the Authorization header in your assistant’s connector settings.
Make one call to confirm it works.
Revoke the old key. MapWise emails you whenever a key is created or revoked.

Manage connected apps

Each app you sign in to MapWise appears under Connected apps on the MapWise API tab of My Account, separate from your API keys. Disconnect an app there. Removing the connector inside Claude does not disconnect it at MapWise.

You can have up to 10 connected apps. Connecting an 11th disconnects the oldest.
A connection unused for 12 months stops working. To reconnect, add MapWise again from inside the app.

Troubleshooting

“Missing or empty …”401

The Authorization header is missing or misspelled, or carries no key. It must be exactly Authorization: Bearer mw_sk_….

MapWise stopped working

The app may have been disconnected. That happens when you disconnect it in My Account, connect too many apps, or leave it unused for a year. See Manage connected apps, then add MapWise again from inside the app.

“Unknown argument … Did you mean …?”

Your assistant misspelled a filter. MapWise rejected the call before billing it. Ask your assistant to retry with the suggested name.

Feedback

Email support@mapwise.com with feedback, a client you want supported, or a tool you wish existed.