Add Bridge Town MCP submission

[gregorycarter]

Tool Submission

Tool Information

• Tool ID: bridge-town
• Tool Name: Bridge Town
• Version: 1.0.1
• Author: Bridge Town
• Homepage: https://github.com/Bridge-Town/financial-modeling-mcp

Description

Bridge Town is a hosted MCP connector for building financial models as code: cloud execution, Google Sheets workflows, version control, collaboration, dashboards, scenarios, and portable project archives.

The production Bridge Town server is a commercial hosted service. The public repository contains registry metadata, user-facing documentation, and a minimal bridge-town-mcp stdio shim that forwards MCP JSON-RPC messages to the hosted Streamable HTTP endpoint at https://api.bridgetown.builders/mcp.

MCP Functions Exposed

The manifest lists all 75 Bridge Town MCP tools. Primary groups:

• Billing: get_subscription, get_usage
• Projects and files: list_projects, create_project, delete_project, list_files, read_file, create_file, update_file, patch_file, delete_file, commit_files, describe_model
• Execution and outputs: run, get_run, list_runs, cancel_run, get_run_output, export_run_output
• Data and Google Sheets: ingest_data_source, list_data_sources, query_data, get_spreadsheet_metadata, batch_read_gsheet_ranges, write_gsheet, format_gsheet, modify_gsheet_structure
• Branches, versions, and pull requests: create_branch, list_branches, merge_branch, delete_branch, compare_branches, compare_runs, list_versions, diff, rollback_version, create_pull_request, list_pull_requests, get_pull_request, review_pull_request, merge_pull_request
• Collaboration and sharing: collaborator tools, model share request tools, dashboards, commentary, scheduled runs, snapshots, imports, exports, templates, search_tools, get_tool, and get_skill

Permissions Justification

Permission	Value	Reason
filesystem	false	The public stdio shim does not read or write local files. Model files and data live in Bridge Town's hosted tenant-scoped service.
network	["https://api.bridgetown.builders"]	Required to forward MCP JSON-RPC messages to the hosted Bridge Town MCP API.
env_vars	["BRIDGE_TOWN_API_TOKEN", "BRIDGE_TOWN_MCP_URL"]	The token authenticates the caller. The URL override is for local development and defaults to the hosted endpoint.
allow_exec	false	The shim does not spawn child processes.
processes	false	No local process management is required.

Checklist

• toolbox.toml is in submissions/bridge-town/
• Binary entry name matches an actual binary: bridge-town-mcp in the public repository
• All permissions are justified above
• Tool description is accurate and does not contain hidden instructions
• I have tested this tool locally with the Bridge Town stdio shim and MCP framing path

Local Validation

python3 - <<'PY'
import tomllib
from pathlib import Path
with Path('submissions/bridge-town/toolbox.toml').open('rb') as f:
    data = tomllib.load(f)
assert data['tool']['name'] == 'bridge-town'
assert len(data['mcp']['tools']) == 75
print('toolbox.toml valid TOML with 75 tools')
PY

bash scripts/review-tool.sh submissions/bridge-town/

Result: manifest structure passed; fallback pattern scan reported no suspicious patterns. The toolbox scanner was not available locally, so maintainers should run the full scanner in the normal review environment.