INDIVIDUAL MCP TOOL

circle_along_the_way

Trips people in the connected person's Circle already plan today or tomorrow that fit an errand: a store run someone's item could ride along on, a return or post office stop, a trip they both make.

citysignalai.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://citysignalai.com/mcp

No auth detected

Connect to this endpoint to inspect the live schema for circle_along_the_way and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

A tool name or description contains a write-action term.

Parent server

citysignalai.com

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.citysignal]
url = "https://citysignalai.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "citysignal": {
      "type": "http",
      "url": "https://citysignalai.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: citysignal
Remote MCP URL: https://citysignalai.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "citysignal": {
      "url": "https://citysignalai.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "citysignal": {
      "type": "http",
      "url": "https://citysignalai.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "citysignal",
  "transport": "streamable-http",
  "url": "https://citysignalai.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

list_cities — The cities CitySignal covers, with their slug, timezone, center point, the official sources it reads, and status: live, or preview (still being checked, open to sign-ups, trackers not yet public).
city_now — Live alerts in a city, deduplicated from official feeds (roads, transit, weather, power, water, construction) and placed by the app's own rule into four buckets: now (live and current), ongoing (live for more than two days, or unconfirmed), ahead (starts later, within 7 days, grouped by day) and recap (ended in the last 12 hours).
city_near — Alerts within a radius of a latitude and longitude in a city, nearest first, each with its distance in miles: live ones (bucket now, ongoing or ahead) and ones that ended in the last 12 hours (bucket recap, so 'was there anything here this afternoon' can be answered).
city_week — Week-over-week memory for a city: counts by category for the last 7 days and the 7 before, a plain-language read of the week, measured insights, where it concentrated (areas and corridors), why an unusual week was unusual, and what a newsroom published about it.
city_incidents — Four weeks of what happened in a city, sorted by kind, for one category.
cities_report — Report mode: how every live CitySignal city is doing, in one call.
city_events — Events, concerts and home games coming up in a city within the next N days (default 7, max 14), with venue area, ticket price range and a ticket link when listed, and expected local traffic impact when known.
get_signal — Full detail for one signal by its signal_id (from any other tool): summary, place, area, corridor, timing, source link, confidence and whether a live camera check confirmed or contradicted it.