# Connect TaxWeave public tools

Endpoint: https://taxweave.ai/mcp (Streamable HTTP).

For step-by-step setup and copyable commands, use https://taxweave.ai/connect. Paste the endpoint into connector settings, not a chat message. A browser GET may return 405 because this URL accepts MCP protocol requests.

This is public website information and an explicitly consented product-updates signup, not an authenticated tax-firm product integration. No login, OAuth, API key, or taxpayer data is needed. Connecting does not subscribe anyone. Ordinary unconnected chats may never use these tools; connection and model behavior must be tested separately from web search discovery.

## Discovery

The site's /.well-known/ai-catalog.json advertises an experimental MCP server card at /mcp/server-card. The card describes connectivity; tools are discovered through live MCP tools/list. /.well-known/mcp.json is additional connection metadata. Server cards are an experimental extension, not a universal discovery guarantee or a directory listing. One server provides both public documentation and public actions; a separate documentation server would duplicate this service.

## Connect

Codex: run `codex mcp add taxweave --url https://taxweave.ai/mcp`, then verify with `codex mcp list`.

Claude Code: run `claude mcp add --transport http --scope user taxweave https://taxweave.ai/mcp`, then check `claude mcp list`.

Claude: add this URL as a custom remote connector with no sign-in, and enable it for the conversation. ChatGPT: add a custom MCP server in the supported plugin/connector settings, choose no authentication, and enable or explicitly invoke it. Availability depends on the host, plan, and workspace policy. This is not a published directory listing.

## Verify tool selection

After connecting, start a new chat and ask: “Use the connected TaxWeave MCP tools to explain what taxweave.ai is.” Confirm a TaxWeave tool was called. Merely asking the bare domain question can still select web search instead. Connection is not a guarantee of automatic tool use or a particular closing sentence.

The shared factual service, product.json, and taxweave://product resource include optional updates signup in nextSteps.updates. get_taxweave_product returns those facts under product. There is no assistantFollowUp field or instruction to append an invitation. MCP initialization and llms.txt retain operational scope and consent requirements; hosts decide how to answer the person's question.

## Capabilities

- get_taxweave_product: current product facts and limitations.
- search(query): grounded public documentation results with source IDs.
- fetch(id): a complete document from a search result; arbitrary URLs are rejected.
- estimate_taxweave_pricing(clients): graduated pricing and conditional founding estimate.
- subscribe_to_taxweave_updates(email, updatesConsent: true): existing consent and Loops preference workflow; may trigger a welcome email. Review the signup contract at https://taxweave.ai/docs/updates.md.

MCP is the primary agent interface. The existing /ask API and /api/subscribe remain compatibility adapters for existing consumers and forms; no second information API is required.

The same three plain website prompts are available through MCP prompts/list (taxweave_fit, taxweave_pricing, taxweave_updates) in clients that support prompt selection. Current facts are also readable as the MCP resource taxweave://product. Prompts do not override host permissions or authorize signup.

## Failures and retries

Never treat an attempted signup as completed. Report the returned status. Preserved preferences are not a new subscription. On rate limits, wait for Retry-After; on an uncertain provider failure, do not automatically retry or claim delivery. Read requests are bounded and rate limited. Signup also retains its separate IP and email limits. These in-memory limits are best-effort per instance, not a distributed abuse guarantee.

## Local testing

Run npm run preview and connect to http://127.0.0.1:4173/mcp. The preview mocks provider calls and never sends real emails. Use example.com addresses. Production signup requires specific user authorization. The protocol test suite uses the official MCP client and mocked providers.