Choose a connection

The public API serves read-only reference data without an API key. It is useful for websites, directories and other programs that need Brownsmith’s published business information. The Business Advisor MCP is a separate, authenticated assistant integration for interactive scoping and contact handoff.

Public read-only API

These routes are public and support GET and HEAD. No key or sign-in is required.

/openapi.json describes the API in OpenAPI 3.1. /server.json publishes MCP server metadata using the official MCP Registry server.json format and the 2025-12-11 schema. Publishing this file on this site does not mean the server is listed in the MCP Registry. /.well-known/mcp.json is a site-specific alias for /server.json, not an MCP-mandated discovery endpoint.

Try the live read-only API

These links open the real API responses. There is no separate sandbox, write action, credential form or sample key.

For a terminal request, try curl -i 'https://mcp.brownsmithdynamics.com/api/v1/business'. Requests need no authorization header.

Errors and request rules

Public API error responses use application/problem+json (RFC 9457), with type, title, status, detail and instance, plus a stable code and actionable resolution where available. Unknown API query parameters return 400; unsupported methods return 405 with an Allow header. Public API routes are read-only: use GET or HEAD.

Business Advisor MCP

The MCP endpoint is https://brownsmith-business-advisor.anandrawat.chatgpt.site/mcp. It is a Streamable HTTP MCP server protected by the Site sign-in. Connect using the MCP support built into your AI client and follow that client’s Site connection/sign-in flow. The custom-domain /mcp route is not the hosted OAuth resource. Sites owns the authorization experience; there is no generic API key and this page does not promise that arbitrary OAuth clients can sign in.

A compatible client negotiates a connection, initializes the MCP session, then lists available tools with tools/list. For Streamable HTTP, send Accept: application/json, text/event-stream; clients must accept either JSON or server-sent events for protocol responses. The MCP endpoint is not the public data API.

Read the official MCP TypeScript client guide for the client-side initialize and tool-list flow. For connection steps for supported hosts, see the Business Advisor connection guide.

The advisor works with information you provide. Contact handoff tools require explicit approval of the reviewed message before anything is sent.

Machine-readable formats

Content pages support Markdown negotiation: request Accept: text/markdown; responses selected by the Accept header vary accordingly and should include Vary: Accept. Structured API data remains JSON. See OpenAPI and MCP server metadata.