6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Badger Maps (Standard)
Read and change a field-sales territory from an AI agent: accounts, routes, check-ins.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
What the Badger Maps (Standard) connector does
The Badger Maps MCP server connects a field-sales territory — customer accounts, driving routes, site check-ins and follow-ups — to Claude, ChatGPT and any MCP-compatible agent. Anthropic's directory lists 21 tools: 13 read, 7 write and one that deletes a customer account. Sign-in is OAuth with your Badger username and password.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Badger Maps (Standard) tools (21)
- create_account
- create_checkin
- create_route
- delete_account
- find_user
- get_account
- get_account_brief
- get_account_by_external_id
- get_accounts_in_area
- get_checkins
- get_route
- get_user_profile
- list_accounts
- list_future_followups
- list_overdue_followups
- list_routes
- search_accounts
- update_account
- update_account_address
- update_checkin
- update_route
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- The single OAuth scope draws no boundary.
badgernames no object and no verb. Nothing at the consent screen separates the 13 reads from the seven writes or the one delete. The only place that separation exists is the client's per-tool permission setting. - Eleven of the 21 tool names have no vendor corroboration in any medium — no text, no recording. That set includes
delete_accountand six of the seven writes. The ten names Badger's recordings do corroborate are nine reads pluscreate_route, and they match as prettified labels rather than as literal strings, so a rename would not have shown. delete_accountis undocumented. Badger publishes no description, no statement on whether the deletion is recoverable, and no mention of a confirmation gate. We did not test it.- We could not read tool schemas or safety annotations. The endpoint returns 401 to an anonymous request, so no parameter-level detail appears on this page and every read/write label is our classification of a name.
- The connector inherits the connecting user's clearances, and Badger names no MCP-specific limit. An admin login gives the agent admin breadth across the team's accounts, routes and check-ins.
- The AI leg is your responsibility, and Badger says so. Its documentation states the user assumes full responsibility for compliance when connecting the server to any external LLM or AI platform, and that it makes no representations about third-party platforms' data practices. Where reps are tracked, employee-notification and works-council duties are the operator's.
- Data may reach model training via the AI platform, not via Badger. Badger's documentation warns that data returned from the MCP server may be processed by the connected platform and, depending on account settings, used to improve or train its models, and directs users to that platform's opt-out. Badger notes this is governed by the third party's policy, not its own.
- A second Badger MCP server exists at a different endpoint and is not in the current directory. See below — it is not what this page describes.
- No metering signal either way. No tool name carries a credit, balance, usage, quota or billing term, and Badger publishes no per-call cost for MCP. We found no evidence that a call spends anything, and no tool that could observe it if one did.
- Badger publishes no rate limits for the MCP server. Its security page describes login rate-limiting and account lockouts, which is a different control.
Frequently asked questions
Can the Badger Maps connector see where an individual salesperson has been?
It reaches their visit history, not their live position. get_checkins returns the check-in records a rep filed at customer sites, each carrying a place and a time, and list_routes plus get_route return the planned stops for a day. Ordered by time that is a movement log for a named worker. Badger's privacy policy says device location is captured non-continuously.
Does the Badger Maps MCP server expose customer records?
Yes, and they are the connector's main subject. Accounts in Badger are the businesses a rep visits, and list_accounts, search_accounts, get_account and get_accounts_in_area return them. Badger's demo transcripts show account names, street addresses, recipient email addresses, last check-in dates and free-text notes coming back. Those are third-party contact records, not your own data.
Can the Badger Maps connector delete anything?
One tool can: delete_account. It is the only destructive name among the 21, and it removes a customer account record along with whatever history hangs off it. Badger publishes no documentation for the tool and we could not read its schema, so whether deletion is soft or permanent, and whether it cascades to check-ins, is unknown.
What OAuth scopes does the Badger Maps MCP server request?
Exactly one, named badger. The server's RFC 9728 descriptor and its authorization server metadata both advertised that single scope on 2026-08-23. It names no object and no verb, so it cannot separate reading an account from deleting one. Granting it grants whatever the server implements, now and in future.
How do I stop the AI from writing to Badger Maps?
Use per-tool permissions in the client, because OAuth will not do it. Badger's guides state that in Claude you go to Customize, then Connectors, then Badger Maps, then Tool permissions, and set each tool to Always allow, Needs approval, or Blocked. That per-tool control is the only place the write and delete tools can be separated from the read ones.
Can the Badger Maps connector send an email to a customer?
Not by itself — no tool among the 21 sends mail. Badger's own use cases pair the connector with a separate Gmail or Outlook connector, and its example prompts all end with a saved draft rather than a send. In Badger's demo recordings Claude states the drafts are saved and the Send button is never clicked, so a human still presses send.
What permissions does the Badger Maps MCP server have in my account?
Exactly the ones the connecting user already has. Badger states the MCP server is a wrapper around its API and carries the same permissions as the setup user, and gives the example that connecting through an admin who can already see everything gives that same admin access over MCP. Connect a rep-level account, not an admin one, to narrow the reach.
Does Badger Maps store my AI conversations?
Badger says the MCP server itself does not, but its wider product does log AI usage. Its documentation states the MCP server does not independently store, process, or share user or customer data with third parties. Separately its privacy policy names PostHog as storing AI Assistant chat transcripts and related metadata, which describes Badger's in-app assistant rather than this connector.
Sources
- Badger Maps, "How to Connect Badger Maps to an AI Assistant" (retrieved 2026-08-23). The endpoint, the Claude setup steps, the five example prompts, the technical FAQ and the data-privacy statement all come from this page. · retrieved 2026-08-23
- Badger Maps, "…for Route Creation" (retrieved 2026-08-23) · retrieved 2026-08-23
- Badger Maps, "…for Follow-Up Emails" (retrieved 2026-08-23) · retrieved 2026-08-23
- Badger Maps, "…for Pre-Meeting Briefs" (retrieved 2026-08-23) · retrieved 2026-08-23
- Badger Maps, "…for Email Scheduling" (retrieved 2026-08-23). The per-tool permission instruction appears in all four task guides. · retrieved 2026-08-23
- Badger Maps screen recordings embedded in the four task guides above, hosted at
badger-website-staging.s3.amazonaws.com(retrieved 2026-08-23). The tool-label table is transcribed from the frames of these recordings; the demo data in them is synthetic. · retrieved 2026-08-23 - Badger Maps, "Badger Maps & Your Security" (retrieved 2026-08-23) · retrieved 2026-08-23
- Badger Maps privacy policy (retrieved 2026-08-23). Source for the non-continuous location statement and the collected-data list. · retrieved 2026-08-23
- Live auth posture check, 2026-08-23: an anonymous
initializetohttps://mcp.badgermapping.com/mcpreturned 401 withwww-authenticate: Bearer resource_metadata=…; RFC 9728 metadata at and authorization server metadata at , both advertising the single scope. A nonsense control path under the same prefix returned a 404 body identical to the host's other 404s, so the 200s are genuine and not a catch-all. · retrieved 2026-08-23 https://www.badgermapping.com/robots.txtreturned 404 on 2026-08-23, so no crawl directive and noContent-Signalapplies.llms.txt,llms-full.txtand the.mdsuffix route all returned 404; the nominated documentation URL was the only route that resolved. · retrieved 2026-08-23- Anthropic Connectors Directory entry — , read from our directory snapshot dated 2026-08-23 · retrieved 2026-08-23
- Badger Maps support
More Productivity connectors
Adobe Experience Manager
Create, edit, publish and delete AEM pages, content fragments and assets from an agent.
Adobe Workfront
Find, create, update and delete Workfront work items from an AI agent.
Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.
Use it in an agent
Put Badger Maps (Standard) to work.
Connect Badger Maps (Standard) once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.