Moxie Docs MCP vs US Places, Then
A side-by-side look at the Moxie Docs MCP and US Places, Then MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
U
US Places, ThenLocation Services · Local subprocess (stdio)US places then: county on a date, PLSS land, GNIS names, old topo maps, post offices.53GoodAuth: no auth requiredVerdict: choose Moxie Docs MCP for knowledge & memory work as a local process; choose US Places, Then for location services as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Moxie Docs MCP when
- You need dedicated capabilities in the Knowledge & Memory domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You want tools like
moxie.get_ai_context, moxie.get_doc_impact, moxie.get_api_context.
UChoose US Places, Then when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
county_at, county_history, parse_legal_description.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | U US Places, Then | |
|---|---|---|
| Category | Knowledge & Memory | Location Services |
| Quality signal | 80/100 · Excellent | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | Freemium | Free |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 2 | 0 |
| Directory activity | 36 views 25 installs 4 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 12 | 12 |
| Full listing | View Moxie Docs MCP | View US Places, Then |
Tools & capabilities
Moxie Docs MCP tools 12
moxie.get_ai_contextCompact pre-edit briefing: repo status, verified commands, top conventions, open gaps, team notes. Read this first.moxie.get_doc_impactGiven the paths you're about to change (and any you're deleting), returns the conventions, gaps, and existing docs whose evidence overlaps them - and flags net-new/undocumented surfaces.moxie.get_api_contextGiven paths you're about to touch, returns structured context for any API endpoints they map to: method, path, schema, and known consumers/features.moxie.review_changeSelf-review a change before opening the PR; returns a severity-ranked verdict (clean / warnings / must-fix) covering convention breaches, stale docs, undocumented surface, and broken references.moxie.get_conventionsDiscovered coding conventions, grouped by category, with confidence scores, agent guidance, and source-file citations.moxie.search_docsSemantic + keyword search over generated docs, conventions, gaps, and AI context.moxie.get_doc_gapsUnresolved documentation gaps with severity and the paths they concern.moxie.get_documentation_opportunitiesRecommended doc work: missing docs, drift repairs, and PR templates.moxie.get_documentation_patternsHow the repository organizes and maintains its docs (where new docs belong).moxie.list_docsPaginated, section-grouped table of contents of every generated doc.moxie.propose_doc_updateAdd or update a doc as part of your current change; returns the target path + Markdown to write into your branch.moxie.propose_doc_removalRemove a Moxie-tracked doc your change makes obsolete; returns the path to delete in your branch.
US Places, Then tools 12
county_atThe county (or counties) that held a point on a date: a day, a month or a year. Returns the holder, its dates, the event and statute that made it, the whole chain of counties for that spot, changes within a year (check those by hand), and whether two governments contested it.county_historyEvery version of one county: created when, from what, and each later change, with statutes.parse_legal_descriptionRead a land description, however it is written (`E½NE`, `E2NE`, `E 1/2 NE 1/4`, "the east half of the northeast quarter", GLO's padded `0840N`, lots, several tracts), into its parts, with quarter-quarters and warnings for anything guessed. Offline.plss_locatePlace a description on the map: centroid, bounding box, acreage and BLM's ids, to the township, section, quarter-quarter or lot.plss_from_pointName the survey tract at a point: township, range, section and quarter-quarter.public_land_stateWas this state federal land? If not, who granted first title and where those records are; if so, its meridians and special cases. Offline.find_place_nameA named place in GNIS: its point, class, state and county. Searches the live GNIS and, given a state, the archive of August 2021 that keeps the cemeteries, churches, schools, post offices and buildings GNIS dropped that year; says which answered.post_officesWhich US post offices existed, 1639-2000: by name, by state and today's county, or around a point, and in a given year. Each with its years, whether it ran continuously, and its point if it was geocoded.historical_topo_mapsEvery USGS topographic map covering a point, oldest first: date, scale and quadrangle, with GeoPDF, GeoTIFF and JPEG preview links, and a TopoView link for JPEG and KMZ.find_land_entry_fileFrom a patent's Authority: the kind of entry, what its file holds, which National Archives series has it, ready-made arguments for nara-catalog-mcp's `search_records_advanced`, and how to order the file if it is not online. Offline.glo_linksA link to a search, or to one record, on BLM's General Land Office Records site, for you to open. Offline.cache_statusThis session's live calls and cache hits, and the datasets downloaded so far. Offline.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Moxie Docs MCP
{
"mcpServers": {
"moxie-docs-mcp": {
"command": "npx",
"args": [
"-y",
"moxie-docs"
]
}
}
}
US Places, Then
{
"mcpServers": {
"us-places-then": {
"command": "uvx",
"args": [
"us-places-mcp"
]
}
}
}
Frequently asked questions
Moxie Docs MCP is categorized under Knowledge & Memory and uses a local stdio subprocess. US Places, Then belongs to Location Services and uses a local stdio subprocess. Pick Moxie Docs MCP for knowledge & memory work and US Places, Then for location services.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Moxie Docs MCP is listed as freemium — a free tier with paid plans. Auth: api key required. US Places, Then is listed as free. Auth: no auth required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add moxie-docs-mcp and us-places-then as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Moxie Docs MCP has a quality signal of 80/100 (Excellent) with 36 views, 25 installs and 2 GitHub stars. US Places, Then has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.