Guides

Adding up your AI invoices gets the number wrong in both directions. A three-bucket model for real AI spend, and the four traps that corrupt it.

Let an AI client schedule real meetings on your calendar — previewing times before creating, checking invitee availability, and sending invites.

Connect ChatGPT to your own business data through a custom connector authenticated with OAuth 2.1 and PKCE, so it searches before it answers.

Connect GitHub so any AI client can search your repos, with issues, PRs, and commits synced into a workspace scoped to that specific repository.

Connect GreatArrow.ai to Claude as an MCP connector, then link Gmail through OAuth so Claude can search and reference your inbox in conversations.

Connect Slack to your AI assistant through OAuth so any connected client can search messages, follow threads, and reply — scoped to the channels you allow.

Give Cursor project-aware, persistent memory with a one-click deeplink install and a REPO workspace that auto-provisions from your repository URL.

Every AI client you use keeps its own memory. Here is how MCP gives Claude, ChatGPT, Cursor, and your other AI tools one shared, persistent memory instead.

Give Claude Desktop persistent memory it can search across sessions, using the one-click .mcpb installer, the universal installer, or a manual config file.

Step-by-step setup to connect both Claude and ChatGPT to the same memory server, so a fact stored in one is instantly searchable from the other.

An evaluator-level explanation of the Model Context Protocol — what it does, remote vs. local servers, OAuth vs. tokens, and what to check in a server.