Remote MCP server — connect with no install

The remote MCP server lets you connect Turtini to AI clients without installing anything locally — no Node, no npx, no config-file edits. Point your client at one URL with one Bearer key and you're done.

URL: https://api.turtini.com/mcp
Auth: Authorization: Bearer turtini_<your-key>
Transport: Streamable HTTP (MCP spec 2024-11-05)

How to connect:
1. Go to Settings → Developer → Connect to AI (or /connect) and pick "Remote MCP (no install)"
2. We mint a fresh API key with the AI-assistant scope bundle
3. Copy the URL + key into your client's "Custom Connector" / "Remote MCP" panel
4. The client will run an initialize handshake and discover the tools automatically

Clients that support remote MCP today:
• Claude Desktop (Custom Connectors)
• MCP Inspector (Anthropic's reference debugger)
• Cursor (with remote-MCP enabled)
• Any client that supports MCP Streamable HTTP transport

What's exposed:
14 tools, exactly mirroring the @turtini/mcp local stdio server: auth_whoami, contact_list, contact_create, article_list, article_create, event_list, event_create, account_list, opportunity_list, quote_list, product_list, grant_list, search, note_create.

Per-tool scope checks happen inside the server — a key with only contacts:read can call contact_list but gets a clean error on note_create. Each call hits Firestore directly via the same logic as the public REST API, so behavior is guaranteed identical.

Why prefer remote over the local @turtini/mcp package:
• Zero install (no Node, no npx)
• Zero config-file edits — just paste a URL
• Updates ship server-side — you never need to npm update
• Works in clients that don't support spawning subprocesses (browser-based MCP clients, restricted environments)