Handled Locator

com.handledlocalPublished by handledlocal.comOfficial publisherv0.1.0Updated Oct 27, 2026

Manage a store locator by chatting: locations, tags, booking buttons, map styling, embed code.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server for Handled Locator that lets an assistant manage a store locator: locations, tags, booking buttons, map styling and embed code.

What you can do
  • Manage store locator locations and their tags
  • Configure booking buttons and map styling
  • Retrieve or adjust the embed code for the locator
  • All actions are performed through a hosted remote endpoint after OAuth sign-in
When to use it
Useful when you run a store locator on Handled Locator and want to update locations, tags, booking buttons or map appearance conversationally instead of through its dashboard.
Requirements
A remote MCP endpoint at app.handledlocal.com over streamable HTTP; OAuth authentication is required, so a Handled Locator account with access to the locator is needed. No environment variables or headers are declared.
Before you install
The server can change live locator content such as locations, tags, booking buttons and map styling, so review edits before applying them. Access is granted through OAuth to your Handled Locator account; the manifest lists no further credentials.

Installation

In SourceWeft

  1. Open Handled Locator in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.handledlocal%2Flocator/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "handled-locator": {
      "type": "http",
      "url": "https://app.handledlocal.com/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.