Using Bridge Town on Smithery

Bridge Town is listed on Smithery at smithery.ai/servers/bridge-town/finance. Use that page when you want Smithery to launch the Bridge Town MCP server configuration for a supported agent or workspace.

Bridge Town remains hosted by Bridge Town. Smithery is the discovery and connection surface; the MCP endpoint, authentication, tenant isolation, and tool execution stay on Bridge Town infrastructure.

Connection profile

Field	Value
Smithery listing	https://smithery.ai/servers/bridge-town/finance
MCP endpoint	`https://api.bridgetown.builders/mcp`
Transport	MCP Streamable HTTP
Authentication	OAuth through Bridge Town
Session parameters	None required

Do not paste Bridge Town API tokens into Smithery. The Smithery listing should send users through the same Bridge Town OAuth flow used by other hosted MCP clients.

Connect from Smithery

Open the Bridge Town Smithery listing: https://smithery.ai/servers/bridge-town/finance.
Choose the Smithery client or install flow you want to use.
Approve the Bridge Town OAuth prompt.
Confirm the server URL is https://api.bridgetown.builders/mcp.
Start a session and ask the client to list Bridge Town tools or models.

Once connected, the agent can call the same 75 Bridge Town MCP tools available through Claude.ai, Claude Code, Claude Desktop, Codex, OpenCode, and other MCP clients.

First smoke prompts

Use these prompts to confirm the Smithery connection is live:

List my Bridge Town models and show the model names only.

Search Bridge Town tools for Google Sheets formatting and tell me which product
tool I should use.

Explain the Bridge Town Google Sheets formatting workflow using the available
tool schemas, then summarize it before taking any action.

The submitted directory profile does not expose behavioral skill retrieval. Claude skills/plugins are packaged separately; connector discovery uses only the static product tool catalog.

Google Sheets workflows

Bridge Town’s Google Sheets tools work through the same OAuth-backed Bridge Town account, but Google Sheet access still follows Bridge Town’s Drive security model:

Bridge Town uses Google drive.file scope.
A sheet must be selected through the Bridge Town web app or created by Bridge Town before an agent can read or write it.
Use list_data_sources to confirm the connected source_name.
Use publish_run_output_to_google_sheet and append_google_sheet_rows for Sheet output.

For the full workflow, see the Google Sheets Integration guide.

Operator checklist

If you maintain the Smithery listing, keep these settings aligned with Bridge Town production:

Server URL: https://api.bridgetown.builders/mcp
OAuth callback URL allowed in Auth0: https://smithery.run/oauth/callback
Namespace: bridge-town
Server id: finance
Session config parameters: none

Smithery domain verification may require a TXT record on www.bridgetown.builders. Keep any existing TXT values in place when adding a Smithery verification value.

Troubleshooting

Callback URL mismatch

If OAuth fails with Callback URL mismatch, add https://smithery.run/oauth/callback to the Bridge Town Auth0 application’s allowed callback URLs, then retry the Smithery connection.

Smithery cannot verify the domain

Add the Smithery-provided TXT value to www.bridgetown.builders in Vercel DNS. Do not replace existing TXT records. DNS propagation can take a few minutes.

GET /mcp returns 405

This is expected. Bridge Town serves MCP over Streamable HTTP and expects MCP client requests to use POST. Use https://api.bridgetown.builders/mcp exactly; do not add /sse, /v1, or another transport-specific suffix.