Connect workspaceAlberta

Wouldn't it be great if the next contract was easier to find? Search CanadaBuys and Alberta Purchasing Connection from your compatible AI client.

  1. Add a remote HTTP MCP server with the URL https://elbowsupknivesout.warreandvavasour.com/mcp.
  2. Try: “Find open Alberta construction opportunities closing in the next 30 days.” Public search does not require an account.
  3. For saved watchlists, bid scorecards or document analysis, follow your client's Connect prompt. Continue with your Gmail or Google Workspace account, then approve access for the client shown.
  4. Pro tools require an active workspaceAlberta Pro subscription with the same email. Signing in is free and does not charge you. Subscription payments use our separate Stripe checkout.

Claude: add the URL in Customize → Connectors. Claude Code: add it as an HTTP MCP server, then use /mcp to authenticate. Other clients need remote MCP and OAuth with PKCE support.

Google accounts using an external email address without Gmail or Google Workspace are not currently supported, because we must verify ownership of the subscription email. If an email is already attached to another sign-in, contact support to link accounts.

Which tools need sign-in?

The connector is authless with partial authentication: connect and use public tools first; a protected tool returns HTTP 401 so your client can start OAuth sign-in.

APC search and matching may send your search terms or business capabilities to Cohere for commodity-filter selection. Document analysis sends data to the providers described in our privacy notice. Bid-room processing has a 145-second overall limit and may ask you to retry a large package with fewer attachments. A timeout means no completed analysis is available.

Always verify deadlines, eligibility and requirements in the original tender documents. Summaries and scores assist your review; they do not submit a bid.

For sign-in help, account-data requests or subscription questions: christian@warreandvavasour.com. Include the client name and a description of the issue; never send passwords, API keys or access tokens.

News and notes · Privacy · Source and documentation