Short version: the connector gives Muse the same capabilities as the Zone Agents app, scoped to your own account. Reads (history, report contents, source inspection) are safe to allow automatically. Writes (starting a report, publishing a share link, deleting a report) should stay behind Muse's approval prompt. Connection steps follow Meta's published connector flow and will be refined once the directory listing is live.
1. What the connector does
Zone Agents is a municipal site-intelligence service for real-estate development teams. Type an address and get a defensible, sourced brief. Through Muse you can run the same four workflows by asking in plain language:
- Site due-diligence brief — parcel zoning, site-specific exceptions, flood and watercourse constraints, and public-record gaps for one address.
- Zoning and permitted-use brief — the governing bylaw, exceptions, holding provisions, and whether a use such as “supermarket” is permitted under the bylaw's own terminology.
- Flood and watercourse brief — conservation-authority and provincial regulated-area, floodplain, and wetland sources.
- Council-records search — public council and committee decisions affecting a street or site within a date window.
Every brief links to the government endpoint or record it relied on. When a source is unavailable, incomplete, or bot-blocked, the brief says so and drafts the municipal records request instead of guessing.
2. How to connect
You need a Zone Agents account (sign up). Zone Agents is a standard remote MCP server, so it connects the way Muse connects any OAuth-protected service (see Meta's connector help):
- Ask Muse to connect Zone Agents. Until we are listed in the connector directory, tell Muse to connect to the MCP server at
https://app.zoneagents.ca/mcpas a custom connector; the OAuth authorization server is advertised at/.well-known/oauth-protected-resource/mcp. - Sign in to Zone Agents when prompted and approve the requested access. This is a standard OAuth consent; Zone Agents never sees your Muse credentials and Muse never sees your Zone Agents password.
- Use Muse's approval settings to decide which actions it may take without asking. Our write tools are annotated so Muse can tell them apart from reads (see below).
Disconnecting the connector in Muse stops further requests. Your reports remain in your Zone Agents account. We will update these steps with exact Muse screens once the directory listing is live.
3. Actions and permissions
Each capability is exposed as a separately annotated tool, so Muse can distinguish reads from writes.
| Action | Effect | Recommended Muse approval |
|---|---|---|
list_capabilities | Read | Allow |
list_reports | Read | Allow |
get_report | Read | Allow |
inspect_site_sources | Read (queries live government endpoints) | Allow |
search / fetch | Read (your report history) | Allow |
create_report | Write — starts a report and uses one report credit | Ask |
create_share_link | Publish — makes one completed report readable by anyone with the link | Ask |
delete_report | Destructive — permanently deletes one report | Ask |
Zone Agents never initiates actions on its own and does not push data to Muse proactively. Every action is scoped to the signed-in user's workspace by database row-level security; a connector cannot read another user's reports. Note that an authorized token can call every tool; read-only behaviour depends on the Muse client honouring the tool annotations and your approval settings, not on a server-side scope.
4. Example requests
- “Run a zoning brief for 1500 Jane St, Toronto and tell me whether a grocery store is a permitted use.”
- “Check flood and watercourse constraints for 550 Bayview Ave, Toronto.”
- “Search Toronto council records for noise-control measures on Jane Street between September 2023 and September 2025.”
- “Which government endpoints did my last Mississauga report actually query?”
- “Share my Vaughan zoning brief with a public link.” (Muse will ask you to confirm.)
Reports run in the background and usually complete within a few minutes. Muse can poll for progress or you can open the report in the app.
5. Data handling
- Public data only. The research path uses public municipal, provincial, and conservation-authority sources. Do not submit personal information about third parties.
- What Muse sends us. The address or street, the workflow, optional date range and use terms, and your OAuth token. Nothing else from your Muse conversation is transmitted.
- What we send Muse. The report contents, source links, progress state, and the results of the actions you asked for.
- Storage. Reports are stored in your Zone Agents account under the same retention rules as the app. Connector traffic is covered by our Privacy Policy and Terms of Service.
- No sale or advertising use. We do not sell personal information or use it for behavioural advertising.
6. Coverage and limits
Parcel-level zoning is currently wired for 15 Canadian municipalities including Toronto, Mississauga, Vaughan, Markham, Richmond Hill, Hamilton, Ottawa, Oakville, Milton, Calgary, Edmonton, Winnipeg, and Vancouver, with partial coverage for Brampton and Montréal. Ask list_capabilities for the live list. Outside covered municipalities the brief explains the gap and drafts a records request.
A brief is research support, not a zoning certificate, legal opinion, or municipal approval. Confirm material findings against the cited source before relying on them.
7. For developers
- Remote MCP server (Streamable HTTP):
https://app.zoneagents.ca/mcp - OAuth metadata:
/.well-known/oauth-protected-resource/mcpand/.well-known/oauth-authorization-server(Dynamic Client Registration enabled) - REST discovery: /api/v1/openapi.json and /api/v1/capabilities
- Health: /api/health
8. Support
Zone Agents
privacy@zoneagents.ca
Ontario, Canada